MCP Setup Guide

This guide helps you quickly configure ChainStream MCP Server.

Prerequisites

Before you begin, ensure you have:

Requirement	Details	How to Check
ChainStream Account	Registered account	Log in to console to confirm
Access Token	Valid access token	Console → Apps → Generate Token
AI Client	Claude Desktop / Cursor / Custom client	Installed

MCP Endpoint

ChainStream provides a hosted MCP Server. No local installation required - connect directly via:

https://mcp.chainstream.io/mcp

Configuration Steps

Get Access Token

Log in to ChainStream Console
Navigate to Apps page
Create an App to get Client ID and Client Secret
Use credentials to generate Access Token (see Authentication docs)

Access Token is valid for 24 hours. We recommend implementing an automatic refresh mechanism in your application.

Configure AI Client

Claude Desktop
Cursor IDE
Custom Client

Config file path:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

Configuration:

{
  "mcpServers": {
    "chainstream": {
      "url": "https://mcp.chainstream.io/mcp",
      "headers": {
        "Authorization": "Bearer your_access_token"
      }
    }
  }
}

If the file doesn’t exist, create it manually. If you have other MCP Server configurations, add the chainstream config to the existing mcpServers object.

Config file path: ~/.cursor/mcp.jsonConfiguration:

{
  "mcpServers": {
    "chainstream": {
      "url": "https://mcp.chainstream.io/mcp",
      "headers": {
        "Authorization": "Bearer your_access_token"
      }
    }
  }
}

If you’re using a custom MCP client, connect via HTTP+SSE protocol:Endpoint Information:

Endpoint	URL
MCP Endpoint	`https://mcp.chainstream.io/mcp`
SSE Endpoint	`https://mcp.chainstream.io/sse`
Message Endpoint	`https://mcp.chainstream.io/messages`

Authentication:Add Authorization header to requests:

Authorization: Bearer your_access_token

Example Code:

import { Client } from '@modelcontextprotocol/sdk/client/index.js';
import { SSEClientTransport } from '@modelcontextprotocol/sdk/client/sse.js';

const transport = new SSEClientTransport(
  new URL('https://mcp.chainstream.io/sse'),
  {
    requestInit: {
      headers: {
        'Authorization': `Bearer ${process.env.CHAINSTREAM_ACCESS_TOKEN}`
      }
    }
  }
);

const client = new Client({
  name: 'my-client',
  version: '1.0.0'
});

await client.connect(transport);

// List available tools
const { tools } = await client.listTools();
console.log('Available tools:', tools.map(t => t.name));

Restart Client

After configuration, completely quit and restart your AI client for changes to take effect.

Claude Desktop: Fully quit (not just minimize), then reopen
Cursor: Restart the IDE

Verify Configuration

Test Command

Enter the following test question in your AI client:

Query the token balance of 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 on Ethereum

Expected Result

If configured successfully, the AI should:

Recognize this as a balance query request
Call the get_token_balance tool
Return the address’s token balance list

Success example:

This address (Vitalik.eth) holds the following on Ethereum:

| Token | Balance | Value (USD) |
|-------|---------|-------------|
| ETH   | 1,234.56 | $2,469,120 |
| USDC  | 50,000 | $50,000 |
| ...   | ... | ... |

Total value: ~$2,500,000

If the AI doesn’t call the tool or returns an error, refer to Troubleshooting below.

Troubleshooting

Authentication failed

Possible causes:

Access Token entered incorrectly
- Check for extra spaces
- Confirm complete copy
Access Token expired
- Token is valid for 24 hours
- Need to regenerate
Token format incorrect
- Confirm it’s a complete JWT format
- Confirm Bearer prefix is included

Solutions:

Regenerate Access Token
Check if Token is expired
Confirm Authorization header format is correct

Connection failed

Possible causes:

Network issues
- Check network connection
- Confirm access to https://mcp.chainstream.io
Configuration format error
- Check JSON format is correct
- Confirm URL spelling is correct

Solution:

# Test endpoint connectivity
curl -I https://mcp.chainstream.io/mcp

Config file not taking effect

Possible causes:

Config file path incorrect
- macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
- Windows: %APPDATA%\Claude\claude_desktop_config.json
JSON format error
- Use a JSON validator to check
Client not restarted
- Fully quit and restart

Solution:

# macOS - validate config file
cat ~/Library/Application\ Support/Claude/claude_desktop_config.json | python -m json.tool

Tool call failed: Quota exceeded

Possible causes:

Plan quota exhausted
Request rate too high, triggering rate limit

Solutions:

Check quota usage in the console
Upgrade plan for more quota

Data return delayed or timeout

Possible causes:

Network latency
Query data volume too large
Server load high

Solutions:

Check network connection
Reduce data volume per query
Try again later

Next Steps

Tools Catalog

View all available tools and usage examples

AI Agent Tutorial

Build an AI trading assistant

Getting Started

Data Concepts

Security & Compliance

AI Infrastructure

Resources

Legal & Policies

Prerequisites

MCP Endpoint

Configuration Steps

Verify Configuration

Test Command

Expected Result

Troubleshooting

Next Steps

Tools Catalog

AI Agent Tutorial

Getting Started

Data Concepts

Security & Compliance

AI Infrastructure

Resources

Legal & Policies

​Prerequisites

​MCP Endpoint

​Configuration Steps

​Verify Configuration

​Test Command

​Expected Result

​Troubleshooting

​Next Steps

Tools Catalog

AI Agent Tutorial

Prerequisites

MCP Endpoint

Configuration Steps

Verify Configuration

Test Command

Expected Result

Troubleshooting

Next Steps