Other MCP clients

DeFi Orbit AI speaks streamable HTTP (MCP protocol 2025-06-18) at https://mcp.defiorbit.xyz/mcp. The server is stateless — no session setup is required before tools/list or tools/call. Any MCP client can connect using one of three forms, in order of preference. You need an active API key from API Keys.

1. Streamable HTTP with a header

For clients that accept a URL plus custom headers (Windsurf, Cline, and most current clients):

{
  "mcpServers": {
    "defiorbit": {
      "url": "https://mcp.defiorbit.xyz/mcp",
      "headers": {
        "Authorization": "Bearer <API_KEY>"
      }
    }
  }
}

2. Streamable HTTP with a query parameter

For clients that accept a URL but no headers:

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

3. Stdio bridge

For clients that only launch local stdio servers (Codex CLI and older clients), bridge with mcp-remote (needs Node.js). Codex CLI example, in ~/.codex/config.toml:

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

Verify the first call

From the client, call the usage-credits tool with no arguments. 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. To test outside any client, the same call works with curl — note both Accept values are required:

curl -X POST https://mcp.defiorbit.xyz/mcp \
  --header 'Authorization: Bearer <API_KEY>' \
  --header 'Content-Type: application/json' \
  --header 'Accept: application/json, text/event-stream' \
  --data '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"usage-credits","arguments":{}}}'

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. All failure cases are on Troubleshooting.

Get started

Client setup

Reference

1. Streamable HTTP with a header

2. Streamable HTTP with a query parameter

3. Stdio bridge

Verify the first call

If it fails

​1. Streamable HTTP with a header

​2. Streamable HTTP with a query parameter

​3. Stdio bridge

​Verify the first call

​If it fails

1. Streamable HTTP with a header

2. Streamable HTTP with a query parameter

3. Stdio bridge

Verify the first call

If it fails