Claude Desktop & claude.ai

Claude Desktop and claude.ai add remote MCP servers as custom connectors. The connector dialog takes a URL but no custom headers, so use the query-parameter form of authentication. You need an active API key from API Keys.

Add the connector

Go to Settings → Connectors → Add custom connector and enter:

https://mcp.defiorbit.xyz/mcp?api_key=<API_KEY>

Name it DeFi Orbit AI. Custom connectors require a paid Claude plan. The key sits in the connector URL, so treat that settings entry as a secret. To keep the key out of the URL on Claude Desktop, use the local config file with the mcp-remote bridge instead — Settings → Developer → Edit Config opens claude_desktop_config.json:

{
  "mcpServers": {
    "defiorbit": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.defiorbit.xyz/mcp",
        "--header",
        "Authorization: Bearer <API_KEY>"
      ]
    }
  }
}

Restart Claude Desktop after saving. This form needs Node.js installed.

Verify the first call

Start a chat, confirm the connector’s tools appear in the tools menu, and ask:

Call the defiorbit usage-credits tool.

A working setup returns the organization’s balance:

{ "data": { "credits_remaining": 123242, "grants": 119259, "purchased_credits": 3983 } }

That call costs 1 credit, the same as Get Remaining Credits over REST, and confirms the key, billing, and rate limit are all wired to your organization.

If it fails

The one to know: an invalid key still connects and lists all 54 tools — authentication is only checked when a tool runs. If the connector attaches but every call returns INVALID_API_KEY, the key in the URL or config is wrong or revoked, not the connection. All failure cases are on Troubleshooting.

Get started

Client setup

Reference

Claude Desktop & claude.ai

Add the connector

Verify the first call

If it fails

​Add the connector

​Verify the first call

​If it fails

Add the connector

Verify the first call

If it fails