Skip to main content

Connecting to Cursor

Integrate your Reeva MCP servers with Cursor IDE for AI-powered development.

Quick Tip

For ready-to-use configuration snippets, navigate to your server in the Reeva Dashboard and expand the "Connect to MCP Clients" section. You can copy the exact configuration for your server directly from there.

Step-by-Step Setup

1. Get Your Server Configuration

  1. Log into Reeva Dashboard
  2. Navigate to Servers
  3. Select the server you want to connect
  4. Expand the "Connect to MCP Clients" section
  5. Click "Cursor Configuration" and copy the configuration

Your configuration looks like:

{
"mcpServers": {
"my-server-name": {
"url": "https://api.joinreeva.com/mcp/server_xxxxx",
"headers": {
"Authorization": "Bearer YOUR_API_KEY_HERE"
}
}
}
}

Replace YOUR_API_KEY_HERE with an API key linked to your server (found in the Linked API Keys section).

2. Open Cursor MCP Settings

Option A: Via Settings UI

  1. Open Cursor
  2. Press Cmd+, (Mac) or Ctrl+, (Windows/Linux) to open Settings
  3. Search for "MCP" in the settings search bar
  4. Click on "Features""MCP"

Option B: Via Command Palette

  1. Press Cmd+Shift+P (Mac) or Ctrl+Shift+P (Windows/Linux)
  2. Type "MCP Settings"
  3. Select "Preferences: Open MCP Settings"

3. Add Your Server

In the MCP settings panel:

  1. Click "Edit Config" or "Add MCP Server"

  2. Paste your Reeva configuration

  3. Alternatively, manually add:

    • Server Name: Choose a descriptive name (e.g., "my-research-server")
    • Server URL: https://api.joinreeva.com/mcp/server_YOUR_SERVER_ID
    • Headers: Add Authorization header with value Bearer YOUR_API_KEY
  4. Click "Save"

4. Restart Cursor

For changes to take effect:

  1. Close Cursor completely
  2. Reopen Cursor

Alternatively:

  • Press Cmd+Shift+P (Mac) or Ctrl+Shift+P (Windows/Linux)
  • Type "Reload Window"
  • Press Enter

5. Verify Connection

Check MCP Panel:

  1. Open Cursor's MCP panel (usually in the sidebar)
  2. Look for your server name
  3. Status should show "Connected" or a green indicator

Test in Chat:

  1. Open a new chat with Cursor AI (Cmd+L or Ctrl+L)
  2. Ask a question that requires your tools:
    Search the web for "latest React 19 features"
  3. Watch the AI automatically use your tool
  4. Results will appear in the chat

6. Verify Tool Availability

Ask the AI directly:

What tools do you have access to?

Or try:

List all available MCP tools

Configuration Examples

Basic Configuration

{
"mcpServers": {
"reeva-research": {
"url": "https://api.joinreeva.com/mcp/server_abc123",
"headers": {
"Authorization": "Bearer your_api_key_here"
}
}
}
}

Multiple Servers

{
"mcpServers": {
"reeva-research": {
"url": "https://api.joinreeva.com/mcp/server_abc123",
"headers": {
"Authorization": "Bearer api_key_for_research"
}
},
"reeva-productivity": {
"url": "https://api.joinreeva.com/mcp/server_xyz789",
"headers": {
"Authorization": "Bearer api_key_for_productivity"
}
}
}
}

With Custom Names

Use descriptive names that indicate what the server does:

{
"mcpServers": {
"web-scraping": {
"url": "https://api.joinreeva.com/mcp/server_abc123",
"headers": {
"Authorization": "Bearer your_api_key"
}
},
"notion-jira": {
"url": "https://api.joinreeva.com/mcp/server_xyz789",
"headers": {
"Authorization": "Bearer your_api_key"
}
}
}
}

Usage Tips

When to Use Your Tools

The AI will automatically decide when to use your tools based on context. You can also explicitly request:

Use my web search tool to find...
Scrape https://example.com using Firecrawl
Search my Notion workspace for...

Tool Selection

If you have multiple similar tools, be specific:

Use the "My Company Notion" tool to search for project docs

Debugging Prompts

If tools aren't working, try:

List all available MCP tools
Show me the parameters for the google_search tool
Try calling my web search tool with query "test"

Troubleshooting

Server Not Appearing

Problem: Server doesn't show up in MCP panel after restart.

Solutions:

  1. ✅ Verify JSON syntax is valid (no trailing commas, proper quotes)
  2. ✅ Check API key has no extra spaces
  3. ✅ Ensure the Authorization header uses Bearer prefix (with a space after Bearer)
  4. ✅ Ensure Server ID is correct (check dashboard)
  5. ✅ Try removing and re-adding the configuration
  6. ✅ Check Cursor logs:
    • Help → Toggle Developer Tools → Console tab
    • Look for MCP-related errors

"Authentication Failed"

Problem: Error message about authentication when AI tries to use tools.

Solutions:

  1. ✅ Verify your API key is correct and formatted as Bearer YOUR_KEY
  2. ✅ Check key hasn't been revoked in dashboard
  3. ✅ Ensure API key is linked to the correct server
  4. ✅ Try generating a new API key in the dashboard

Tools Not Available

Problem: AI says it doesn't have access to your tools.

Solutions:

  1. ✅ Restart Cursor (full restart, not just reload)
  2. ✅ Check server status in dashboard (should be active)
  3. ✅ Verify custom tools are added to server
  4. ✅ Test server in Reeva Chat first to ensure it works
  5. ✅ Check for Cursor updates (update to latest version)

"Insufficient Credits"

Problem: Tool execution fails with credit error.

Solutions:

  1. ✅ Check credit balance in dashboard
  2. ✅ Purchase more credits if needed
  3. ✅ Verify tool execution succeeded (check Usage page)

Slow Tool Execution

Problem: Tools take a long time to respond.

Expected behavior:

  • Most tools respond in 1-5 seconds
  • Web scraping may take 5-15 seconds
  • External API delays are normal

If consistently slow:

  1. ✅ Check network connection
  2. ✅ Verify external service (Notion, Jira, etc.) is responding
  3. ✅ Test tool in Reeva Playground to isolate issue

Configuration File Location

If you need to manually edit the config file:

Mac:

~/Library/Application Support/Cursor/User/mcp-settings.json

Windows:

%APPDATA%\Cursor\User\mcp-settings.json

Linux:

~/.config/Cursor/User/mcp-settings.json

Best Practices

Security

  • Never commit API keys to version control
  • Use server-specific keys for production
  • Rotate keys periodically (every 90 days)
  • Revoke unused keys in dashboard

Organization

  • Name servers descriptively: "research-tools" not "server1"
  • Group related tools: One server per use case
  • Document usage: Add comments in config (outside JSON)

Performance

  • Limit tool count: Don't add 50 tools to one server
  • Test before deploying: Use Chat/Playground first
  • Monitor usage: Track which tools are actually used

Next Steps

Need Help?


You're all set! Your Reeva tools are now available in Cursor. Happy coding!