MCP

Two MCP servers: public calculators, private fund data

Both speak the Model Context Protocol over HTTP — install once, and any spec-compliant agent client can call them.

Public server — calculators only, no key

Connect An Agent
Claude Code

Add the Nyx Fund public MCP server with one `claude mcp add` command.

claude mcp add --transport http nyx-fund https://nyxchain.org/api/mcp/public
Claude Desktop

Paste a custom connector entry into your Claude Desktop config.

{
  "nyx-fund": {
    "type": "http",
    "url": "https://nyxchain.org/api/mcp/public"
  }
}
Cursor

Install via a one-click deeplink, or paste the config JSON yourself.

Add to CursorOr paste this config
{
  "mcpServers": {
    "nyx-fund": {
      "url": "https://nyxchain.org/api/mcp/public"
    }
  }
}
ChatGPT

Add as a custom connector where your ChatGPT plan and workspace support MCP.

ChatGPT's MCP connector support (Settings, Connectors, Add custom connector — on plans and workspaces where it's enabled) accepts an HTTP MCP server URL:

https://nyxchain.org/api/mcp/public

If a header is required, add it as a custom header: "Authorization: Bearer <your API key>". Availability depends on your ChatGPT plan and workspace configuration.
Any MCP client (JSON-RPC)

Speak raw MCP JSON-RPC over HTTP — works with any spec-compliant client.

# 1. Initialize the MCP session
curl -s -X POST "https://nyxchain.org/api/mcp/public" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2026-06-18","capabilities":{},"clientInfo":{"name":"example-client","version":"1.0.0"}}}'

# 2. Call a tool
curl -s -X POST "https://nyxchain.org/api/mcp/public" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"get_fund_overview","arguments":{}}}'

Fund server — your fund's real data

Connect An Agent
Claude Code

Add the Nyx Fund public MCP server with one `claude mcp add` command.

Needs a real fund API key — mint one from Settings → Developer.

claude mcp add --transport http nyx-fund https://nyxchain.org/api/mcp --header "Authorization: Bearer nyx_sk_YOUR_FUND_API_KEY"
Claude Desktop

Paste a custom connector entry into your Claude Desktop config.

Needs a real fund API key — mint one from Settings → Developer.

{
  "nyx-fund": {
    "type": "http",
    "url": "https://nyxchain.org/api/mcp",
    "headers": {
      "Authorization": "Bearer nyx_sk_YOUR_FUND_API_KEY"
    }
  }
}
Cursor

Install via a one-click deeplink, or paste the config JSON yourself.

Needs a real fund API key — mint one from Settings → Developer.

Add to CursorOr paste this config
{
  "mcpServers": {
    "nyx-fund": {
      "url": "https://nyxchain.org/api/mcp",
      "headers": {
        "Authorization": "Bearer nyx_sk_YOUR_FUND_API_KEY"
      }
    }
  }
}
ChatGPT

Add as a custom connector where your ChatGPT plan and workspace support MCP.

Needs a real fund API key — mint one from Settings → Developer.

ChatGPT's MCP connector support (Settings, Connectors, Add custom connector — on plans and workspaces where it's enabled) accepts an HTTP MCP server URL:

https://nyxchain.org/api/mcp

If a header is required, add it as a custom header: "Authorization: Bearer <your API key>". Availability depends on your ChatGPT plan and workspace configuration.
Any MCP client (JSON-RPC)

Speak raw MCP JSON-RPC over HTTP — works with any spec-compliant client.

Needs a real fund API key — mint one from Settings → Developer.

# 1. Initialize the MCP session
curl -s -X POST "https://nyxchain.org/api/mcp" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2026-06-18","capabilities":{},"clientInfo":{"name":"example-client","version":"1.0.0"}}}'

# 2. Call a tool
curl -s -X POST "https://nyxchain.org/api/mcp" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"get_fund_overview","arguments":{}}}'

Per-client setup pages

Questions, answered

Is there an MCP server for hedge funds?

Yes. Nyx Fund runs two Model Context Protocol servers: a public one at /api/mcp/public with no authentication required for illustrative fund calculators, and a private, fund-scoped one at /api/mcp authenticated with your own nyx_sk_ key for your real fund's live shadow-NAV data.

How do I connect Claude Code to the Nyx Fund MCP server?

Run a single `claude mcp add` command with the public server URL (https://nyxchain.org/api/mcp/public) — no API key and no config file to edit. The exact command is on nyxchain.org/developers/mcp/claude-code.

Does the public MCP server require an API key?

No. The public server is free with no login and no key — it exposes seven calc_* calculator tools plus a search_docs tool, all stateless and illustrative.

Can I connect my own fund's real data over MCP?

Yes, on a separate server — /api/mcp — authenticated with your own nyx_sk_ key, minted from your Nyx Fund dashboard. It exposes the same read-only, shadow-NAV fund tools as the REST Fund Data API, never the public server's calculator tools.

Which AI clients can connect to the Nyx Fund MCP server?

Claude Code, Claude Desktop, Cursor, and ChatGPT (where your plan and workspace support MCP), plus any spec-compliant JSON-RPC MCP client — each has its own setup page at nyxchain.org/developers/mcp/<client>.

What protocol does the Nyx Fund MCP server speak?

Standard Model Context Protocol JSON-RPC 2.0 over streamable HTTP — send `initialize`, then `tools/list`, then `tools/call`. Both servers are stateless and single-response, and share the same JSON-RPC framing.