Claude Code

Claude Code connects to DeFi Orbit AI over streamable HTTP with the claude mcp add command. You need an active API key from API Keys.

Add the server

claude mcp add --transport http defiorbit https://mcp.defiorbit.xyz/mcp \
  --header "Authorization: Bearer <API_KEY>"

This registers the server for the current project. Add --scope user to make it available in every project on the machine. To share the server with a team without sharing the key, commit a .mcp.json at the project root that reads the key from an environment variable:

{
  "mcpServers": {
    "defiorbit": {
      "type": "http",
      "url": "https://mcp.defiorbit.xyz/mcp",
      "headers": {
        "Authorization": "Bearer ${DEFIORBIT_API_KEY}"
      }
    }
  }
}

Each teammate then sets DEFIORBIT_API_KEY in their shell before starting Claude Code.

Verify the first call

Run /mcp inside a Claude Code session — defiorbit should show as connected with 54 tools. Then 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 /mcp shows the server as healthy but every call returns INVALID_API_KEY, the key is wrong or revoked, not the connection. All failure cases are on Troubleshooting.

Get started

Client setup

Reference

Add the server

Verify the first call

If it fails

​Add the server

​Verify the first call

​If it fails

Add the server

Verify the first call

If it fails