Zed + Velkin MCP

Configure the connection

Merge this configuration into Zed settings.json, preserving your existing servers. Choose one Velkin transport; enabling both is unnecessary. The stdio option requires Node.js and downloads the published package through npm.

{
  "context_servers": {
    "velkin": {
      "url": "https://mcp.velkinui.com/mcp"
    },
    "velkin-stdio": {
      "command": "npx",
      "args": [
        "-y",
        "@velkin/mcp"
      ]
    }
  }
}

Verify a tool response

1. Reload or refresh the editor’s MCP server list.
2. Check that the Velkin tools are available. Approve only the tools your workflow needs.
3. Ask: “Read the Velkin Button API, list its documented props, and then show a primary save action.”
4. Confirm that a documentation tool actually ran; a plausible answer alone does not prove the connection works.

Troubleshooting

Check the endpoint spelling, JSON syntax, client version, and local proxy/firewall settings. Hosted requests use Streamable HTTP POST; a browser GET is a discovery response, not a complete MCP handshake. Keep secrets out of committed configuration.

Configuration is based on the published project templates. Check the editor’s own documentation for version-specific settings.