How to Connect Any MCP Client to a Remote MCP Server
This guide provides a universal checklist for connecting any MCP client to a remote MCP server. While the exact configuration steps vary by client, the core principles are the same. We'll use Corcava as the worked example throughout.
Universal Connection Checklist
Regardless of which MCP client you're using, you'll need to complete these steps:
Step-by-Step Checklist
- Get your API key from the MCP server (Corcava: Settings → Integrations → Public API)
- Locate your client's config file (varies by client and OS)
- Add the server endpoint URL (for Corcava:
https://app.corcava.com/mcp) - Add the Authorization header with your API key (
Bearer YOUR_API_KEY) - Save the configuration file
- Restart your AI client (required for changes to take effect)
- Verify tools appear by asking your AI to list available tools
- Test with a simple prompt to confirm everything works
Step 1: Get Your API Key
Before connecting, you need an API key from the MCP server. For Corcava:
- Log in to your Corcava workspace
- Navigate to Settings → Integrations
- Find the Public API section
- Click Add API Key
- Copy the generated key immediately (it's only shown once)
- Store it securely - you'll need it for the next steps
⚠️ Security Tip
Create separate API keys for different AI assistants. This allows you to revoke access per client if needed. Name your keys descriptively (e.g., "Claude Desktop - MacBook", "Cursor - Work Laptop").
Step 2: Locate Your Client's Config File
Each MCP client stores its configuration in a different location. Here are the common locations:
Claude Desktop
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json - Linux:
~/.config/Claude/claude_desktop_config.json
Cursor
- All platforms:
~/.cursor/mcp.json
Windsurf
- All platforms: Settings UI (no file editing required)
Continue
- All platforms:
~/.continue/config.json
For detailed, client-specific instructions, see our setup guides:
Step 3: Add the Server Endpoint URL
The endpoint URL is the address where your MCP client will connect to the server. For Corcava, this is:
This URL should be:
- HTTPS: Always use secure connections (never HTTP)
- Exact: Copy the URL exactly - no trailing slashes
- Accessible: Ensure your network can reach this endpoint (check firewalls/proxies if needed)
Step 4: Add the Authorization Header
Most MCP clients require you to specify authentication headers. For Corcava, you need to add an Authorization header with your API key.
Header Format
The header must be in this exact format:
Important: There must be a space between "Bearer" and your API key. Do not include quotes around the key.
Example Configuration Snippets
Claude Desktop / Cursor Format:
{
"mcpServers": {
"corcava": {
"url": "https://app.corcava.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}
Continue Format (SSE):
{
"mcpServers": [
{
"name": "corcava",
"transport": {
"type": "sse",
"url": "https://app.corcava.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
]
}
⚠️ Common Mistakes
- Missing space after "Bearer"
- Including quotes around the API key in the header value
- Using "Token" instead of "Bearer"
- Trailing whitespace when copying the key
- Using an expired or revoked API key
Step 5: Save and Restart
After adding the configuration:
- Save the configuration file (if editing a file)
- Validate JSON syntax (use a JSON validator if unsure)
- Completely restart your AI client - closing and reopening is required
- Wait for the client to initialize - this may take a few seconds
Why Restart is Required
MCP clients typically load their configuration only at startup. Simply saving the file isn't enough - you must fully quit and restart the application for changes to take effect. Some clients (like Cursor) may have a "Reload" command, but a full restart is most reliable.
Step 6: Verify Tools Appear
After restarting, verify that your AI client can see the MCP server's tools. Here's how to check:
Verification Prompts
Try asking your AI assistant one of these questions:
- "What MCP tools are available?"
- "List all available tools from Corcava"
- "What can you do with Corcava?"
The AI should respond with a list of tools like list_tasks, create_task, start_time_tracking, etc.
Expected Tool List
For Corcava, you should see these tools (and more):
list_tasks- Search and filter tasksget_task- Get task detailscreate_task- Create new tasksupdate_task- Update task detailslist_projects- List projectsstart_time_tracking- Start timer- And more... (see complete tools reference)
Step 7: First Test Prompt
Once tools are visible, test with a simple read-only operation:
Safe Test Prompts
Start with read-only operations that won't modify data:
- "What tasks do I have in Corcava?" - Tests
list_tasks - "Show me my projects" - Tests
list_projects - "What boards are available?" - Tests
list_boards
Note: If you don't have any tasks/projects yet, the AI will return an empty list, which is still a successful connection!
Example: Testing with Corcava
You: "What tasks are due this week in Corcava?"
AI (via MCP):
- Calls
list_taskswith filters for due dates - Receives task list from Corcava
- Formats and presents the results to you
If this works, your connection is successful!
Troubleshooting Connection Issues
If tools don't appear or you get errors, check these common issues:
❌ "Authorization failed" or 401 Error
- Double-check the API key is correct (no extra spaces)
- Verify the key is active in Corcava Settings → Integrations
- Ensure "Bearer" prefix is included with a space
- Check for trailing whitespace when copying the key
❌ "Connection refused" or Network Error
- Verify your internet connection
- Check if
https://app.corcava.comis accessible in your browser - Check corporate firewall/proxy settings
- Try regenerating your API key
❌ Tools Not Showing Up
- Did you fully restart the client? (not just save the file)
- Check JSON syntax is valid (no trailing commas, proper quotes)
- Verify the config file is in the correct location
- Check client logs for error messages
Client-Specific Guides
For detailed, step-by-step instructions for each client, see our dedicated setup guides:
Claude Desktop
Complete setup guide for macOS, Windows, and Linux
Cursor
IDE-focused setup with workflow examples
Windsurf
Settings UI configuration guide
Continue
SSE transport configuration
Ready to Connect?
Get your API key and connect your AI assistant in minutes
No credit card required