Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.coinversa.ai/llms.txt

Use this file to discover all available pages before exploring further.

The Coinversa MCP server exposes all 55 Pulse tools to AI agents over the Model Context Protocol. You install it once in your client, and the agent gets first-class access to Hyperliquid trader analytics, HIP-4 outcomes, live risk, and the cross-market asset registry. Hosted MCP endpoint: https://mcp.coinversa.ai/mcp Source: github.com/Coinversaa/mcp-server Pick your client below. All four use the same hosted endpoint and your same API key.

​
Claude.ai (web)

Use the Custom Connectors UI — no local install.
1

Open the connector modal

Visit claude.ai/customize/connectors?modal=add-custom-connector.
2

Fill in the form

  • Name: Coinversa
  • URL: https://mcp.coinversa.ai/mcp
  • Auth header: X-API-Key: YOUR_API_KEY
3

Verify

Open a new chat and ask: “What’s the global trading stats from Coinversa Pulse?” — Claude should call pulse_global_stats.

​
Claude Desktop

Claude Desktop reads MCP servers from a local JSON config.
1

Locate your config file

OSPath
macOS~/Library/Application Support/Claude/claude_desktop_config.json
Windows%APPDATA%\Claude\claude_desktop_config.json
Linux~/.config/Claude/claude_desktop_config.json
2

Add the Coinversa entry

{
  "mcpServers": {
    "coinversa": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.coinversa.ai/mcp",
        "--header",
        "X-API-Key: YOUR_API_KEY"
      ]
    }
  }
}
If the file already has other mcpServers, just add coinversa alongside them — don’t replace the whole block.
3

Restart Claude Desktop

Fully quit (Cmd+Q / right-click → quit), then reopen. Look for the Coinversa tool icon in the chat input.
Why mcp-remote? Claude Desktop only speaks stdio MCP today; mcp-remote is a small shim that bridges stdio ↔ HTTP so you can use the hosted endpoint instead of running anything locally.

​
Cursor

Cursor supports HTTP MCP servers natively via a one-click deeplink. The fastest path: go to developers.coinversa.ai/connect while signed in, paste your key into the snippet area, and click Install in Cursor. The deeplink encodes the config — no manual editing. For manual install, add to your ~/.cursor/mcp.json: 
{
  "mcpServers": {
    "coinversa": {
      "url": "https://mcp.coinversa.ai/mcp",
      "headers": { "X-API-Key": "YOUR_API_KEY" }
    }
  }
}
Restart Cursor and the Coinversa tools appear in the agent’s tool palette.

​
Perplexity

Use Perplexity’s Custom Connectors.
1

Open connectors

Visit perplexity.ai/computer/connectors.
2

Add custom connector

  • URL: https://mcp.coinversa.ai/mcp
  • Header: X-API-Key: YOUR_API_KEY

​
Other clients (stdio / npx)

For any stdio-based MCP client, run the published server directly: 
COINVERSAA_API_KEY=cvsa_... npx -y @coinversaa/mcp-server
This runs the same code as the hosted endpoint, but locally over stdio.

​
Verify it works

Regardless of client, ask the agent:
Use Coinversa Pulse to show me the top 5 traders on Hyperliquid by total PnL this week.
You should see the agent call pulse_leaderboard and return ranked addresses with PnL stats. If it says “no tool available,” the install didn’t take — restart the client.

​
Troubleshooting

Your key is missing or wrong. Check that you copied the full key (starts with cvsa_) and that you used X-API-Key as the header name (not Authorization).
The MCP connection didn’t initialize. For Claude Desktop, check Console.app on macOS for mcp errors. For Cursor, check the MCP panel in settings. Most often: missing -y on the npx command, or a JSON syntax error in the config.
You may have an aggressive prompt or you share a key with a bot. The MCP and direct-API calls share one quota — see authentication. Bump to Starter or Pro if you genuinely need more.
Clone Coinversaa/mcp-server and run npm run start:http. Set COINVERSAA_API_URL if you also host the backend.