Vybe Solana API MCP

What is MCP?

Model Context Protocol (MCP) is an open standard that allows AI applications to securely access external data sources and tools. The Vybe Solana API MCP server gives AI agents:

• API schema discovery — browse all 35+ endpoints, inspect parameters, and understand response shapes
• Documentation search — find relevant guides and integration details
• Live API execution — make real API calls and get back live Solana data
• Code generation — generate accurate integration code grounded in the actual API spec, not hallucinated fields

Available MCP Tools

Compatibility

The Vybe Solana MCP server uses the standard Model Context Protocol and is compatible with any client that supports remote MCP servers. This includes AI code editors like Cursor and Windsurf, general-purpose AI tools like Claude.ai and Claude Desktop, and any other MCP-enabled application — such as VS Code with Copilot, Cline, Continue, or OpenCode. If your tool supports MCP, you can connect it to Vybe.

The MCP server URL is the same for all clients:

https://docs.vybenetwork.com/mcp

See the setup guides below for client-specific configuration.

Note on execute-request: This tool requires your API key to be forwarded in the MCP connection headers. Most clients that support native url + headers configuration handle this automatically. Claude Desktop via mcp-remote currently surfaces the 3 schema discovery tools but does not expose execute-request. If you need live API execution from Claude, use the Claude.ai connector method below.

Setup

Claude.ai / Claude Desktop (Recommended for full experience)

The simplest way to connect — gives you all 4 tools including live API execution.

Settings → Connectors → Add Custom Connector:

Name: vybe-solana-api
URL:  https://docs.vybenetwork.com/mcp

Once added, toggle the connector on in any conversation via the + icon → Connectors → vybe-solana-api. Provide Claude with your API key when chatting.

Cursor

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "vybe-solana-api": {
      "url": "https://docs.vybenetwork.com/mcp",
      "headers": {
        "X-API-KEY": "your-vybe-api-key"
      }
    }
  }
}

Windsurf

Add to your Windsurf MCP config:

{
  "mcpServers": {
    "vybe-solana-api": {
      "url": "https://docs.vybenetwork.com/mcp",
      "headers": {
        "X-API-KEY": "your-vybe-api-key"
      }
    }
  }
}

Claude Desktop (if using claude_desktop_config.json instead of Connector)

Claude Desktop doesn't support remote MCP servers with native url config yet. Use mcp-remote as a bridge:

{
  "mcpServers": {
    "vybe-solana-api": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://docs.vybenetwork.com/mcp",
        "--header",
        "X-API-KEY:${VYBE_API_KEY}"
      ],
      "env": {
        "VYBE_API_KEY": "your-vybe-api-key"
      }
    }
  }
}

Important: mcp-remote requires Node.js 18+ (recommended: Node 22). Claude Desktop does not use your shell profile or nvm, so it may resolve to an older Node version. To fix this:

• Set command to the full path of npx from your desired Node version (e.g. the path shown by which npx or nvm which 22)
• Set PATH in the env block to include that Node version's bin directory first, so child processes also resolve to the correct version
• If you see SyntaxError: The requested module 'node:fs/promises' does not provide an export named 'constants', your Node version is too old
• If the error persists after updating, clear the npx cache: rm -rf ~/.npm/_npx and restart Claude Desktop (Cmd+Q, then relaunch)

Note: Claude Desktop via mcp-remote currently provides schema discovery tools only (3/4 tools). For live API execution, use Claude.ai with the custom connector method above.

Authentication

All endpoints require an API key passed via the X-API-KEY header. Get your key from vybe.fyi, you can refer to this guide page.

For MCP clients that support headers natively (Cursor, Windsurf, Claude.ai), your API key is automatically forwarded to execute-request calls. For mcp-remote, the key authenticates the MCP transport connection.

Testing Your Setup

Once configured, try these prompts to verify the connection:

• Schema discovery: "List all available Vybe API endpoints" — should return 35+ endpoints across tokens, wallets, trades, and more
• Endpoint inspection: "Show me the parameters for the Wallet PnL endpoint" — should return full parameter schema including resolution, sorting, and pagination options
• Search: "Find all endpoints related to token holders" — should return holder count history and top holders endpoints
• Live execution (where execute-request is available): "Get the top 3 traders by realized PnL today" or "What's the current price of SOL?"

What You Can Build

With the Vybe MCP server connected, your AI assistant can:

• Generate working API integration code grounded in the actual OpenAPI spec
• Query live Solana token prices, wallet balances, and trade history
• Explore 47+ supported DEXs and their swap and trades data, along with their markets
• Build portfolio trackers, trading bots, and analytics dashboards with accurate endpoint knowledge
• Debug API responses by comparing live data against documented schemas