Connecting to Claude Code
Use your Reeva MCP servers with Anthropic's Claude Code CLI tool for AI-powered coding assistance.
For ready-to-use configuration, navigate to your server in the Reeva Dashboard and expand the "Connect to MCP Clients" section.
Prerequisites
- Claude Code installed and configured (see Claude Code documentation)
- A Reeva server with at least one tool configured
- An API key linked to your server
Step-by-Step Setup
1. Get Your Server Details
From the Reeva Dashboard:
- Go to Servers → Select your server
- Note your MCP Endpoint URL:
https://api.joinreeva.com/mcp/server_YOUR_SERVER_ID - Get an API Key from the Linked API Keys section
2. Add Your Reeva Server
Open your terminal and run:
# Add using SSE transport (recommended for remote servers)
claude mcp add --transport sse reeva https://api.joinreeva.com/mcp/server_YOUR_SERVER_ID \
--header "Authorization: Bearer YOUR_API_KEY"
Or using HTTP transport:
# Add using HTTP transport
claude mcp add --transport http reeva https://api.joinreeva.com/mcp/server_YOUR_SERVER_ID \
--header "Authorization: Bearer YOUR_API_KEY"
Replace:
YOUR_SERVER_IDwith your actual server ID (e.g.,server_abc123)YOUR_API_KEYwith your API key from the dashboard
3. Verify Setup
List your configured servers:
claude mcp list
You should see your Reeva server listed with its tools.
4. Authenticate (If Required)
Some remote servers require OAuth authentication. If prompted:
# Start the authentication flow
/mcp
Follow the prompts to complete authentication.
Usage
In Claude Code Chat
Once configured, your tools are available in Claude Code conversations:
# Start a chat session
claude
# Then use your tools naturally
> Search the web for "latest React features"
> Scrape https://example.com for product information
List Available Tools
To see which tools are available from your server:
claude mcp list
Configuration Examples
Single Server
claude mcp add --transport sse reeva-main https://api.joinreeva.com/mcp/server_abc123 \
--header "Authorization: Bearer your_api_key"
Multiple Servers
# Research server
claude mcp add --transport sse reeva-research https://api.joinreeva.com/mcp/server_abc123 \
--header "Authorization: Bearer research_api_key"
# Productivity server
claude mcp add --transport sse reeva-productivity https://api.joinreeva.com/mcp/server_xyz789 \
--header "Authorization: Bearer productivity_api_key"
With Descriptive Names
Use names that describe the server's purpose:
claude mcp add --transport sse web-scraping https://api.joinreeva.com/mcp/server_abc123 \
--header "Authorization: Bearer your_api_key"
claude mcp add --transport sse notion-tools https://api.joinreeva.com/mcp/server_xyz789 \
--header "Authorization: Bearer your_api_key"
Managing Servers
List All Servers
claude mcp list
Remove a Server
claude mcp remove reeva
Update a Server
Remove and re-add with new settings:
claude mcp remove reeva
claude mcp add --transport sse reeva https://api.joinreeva.com/mcp/server_NEW_ID \
--header "Authorization: Bearer NEW_API_KEY"
Troubleshooting
"MCP server not found"
Problem: Server doesn't appear in the list.
Solutions:
# Verify server is added
claude mcp list
# Re-add if missing
claude mcp add --transport sse reeva https://api.joinreeva.com/mcp/server_YOUR_ID \
--header "Authorization: Bearer YOUR_API_KEY"
Authentication Errors
Problem: 401 Unauthorized or authentication failed.
Solutions:
- ✅ Verify your API key is correct
- ✅ Ensure the header format is:
Authorization: Bearer YOUR_KEY - ✅ Check key hasn't been revoked in dashboard
- ✅ Generate a new API key if needed
Connection Issues
Problem: Cannot connect to server.
Solutions:
- ✅ Check your internet connection
- ✅ Verify the server URL is correct
- ✅ Try switching transport from
ssetohttpor vice versa - ✅ Check server is active in the Reeva dashboard
Tools Not Available
Problem: Claude doesn't see your tools.
Solutions:
- ✅ Verify the server has tools configured in dashboard
- ✅ Test the server in Reeva Chat first
- ✅ Run
claude mcp listto confirm connection - ✅ Check your credit balance
Best Practices
- ✅ Use descriptive server names: "web-research" not "server1"
- ✅ Keep API keys secure: Don't commit to Git or share publicly
- ✅ Test in Reeva dashboard first: Verify tools work before CLI use
- ✅ Use SSE transport: Recommended for most remote server connections