Corcava MCP Setup for Continue: Remote MCP Over SSE

Connect Continue to Corcava via MCP using Server-Sent Events (SSE) transport. This guide provides config snippets, verification steps, and a sample workflow that turns a spec into tasks then logs progress as comments.

Prerequisites

Continue installed in your editor (VS Code, Cursor, etc.)
A Corcava account with API key access
Basic familiarity with editing JSON files

About SSE Transport

Continue uses Server-Sent Events (SSE) for remote MCP servers, which provides:

Real-time streaming: Responses stream as they're generated
Persistent connection: Maintains connection for multiple requests
Remote server support: Works with cloud-hosted MCP servers like Corcava
Efficient: Lower overhead than polling-based approaches

Step 1: Get Your Corcava API Key

Log in to Corcava
Navigate to Settings → Integrations
Find the Public API section
Click Add API Key
Copy the key immediately (it's only shown once)
Store it securely - you'll need it in the next step

Step 2: Locate Your Continue Configuration File

Continue stores configuration in a config.json file. The location depends on your editor:

VS Code / Cursor

Path:

~/.continue/config.json

Other Editors

Check Continue's documentation for your specific editor. Typically in:

Your home directory under .continue/
Or in the Continue extension's settings folder

Accessing Continue Settings

You can also access the config through Continue's UI:

Click the gear icon in the Continue sidebar
Select "Edit Config" or "Open Config File"
This opens the config.json file

Step 3: Add Corcava MCP Server Configuration

Open your config.json file and add Corcava to the mcpServers array. Continue uses an array format with SSE transport:

If This Is Your First MCP Server

If the file doesn't have an mcpServers section, add it:

{
  "mcpServers": [
    {
      "name": "corcava",
      "transport": {
        "type": "sse",
        "url": "https://app.corcava.com/mcp",
        "headers": {
          "Authorization": "Bearer YOUR_API_KEY"
        }
      }
    }
  ]
}

If You Already Have Other MCP Servers

If you already have MCP servers, add Corcava to the existing array:

{
  "mcpServers": [
    {
      "name": "existing-server",
      ...
    },
    {
      "name": "corcava",
      "transport": {
        "type": "sse",
        "url": "https://app.corcava.com/mcp",
        "headers": {
          "Authorization": "Bearer YOUR_API_KEY"
        }
      }
    }
  ]
}

⚠️ Important

Replace YOUR_API_KEY with the actual API key you copied
The type must be "sse" for remote servers
There must be a space between "Bearer" and your API key
Ensure the JSON is valid (no trailing commas, proper quotes)

Step 4: Save and Restart Continue

Save the config.json file
Reload Continue or restart your editor
Wait for Continue to initialize

Reloading Continue

You can reload Continue without restarting your editor:

Click the Continue icon in the sidebar
Look for a "Reload" or "Restart" option
Or use the command palette: "Continue: Reload"

Note: If reload doesn't work, fully restart your editor.

Step 5: Verify Connection

After reloading, verify that Continue can connect to Corcava:

Verification Prompt

In Continue's chat, ask:

"What MCP tools are available from Corcava?"

Expected Response:

Continue should list tools like:

list_tasks
get_task
create_task
update_task
list_projects
start_time_tracking
And more...

Step 6: Sample Workflow - Spec to Tasks

Try this workflow that converts a feature spec into tasks and logs progress:

Workflow: Turn Spec into Tasks

Step 1: Provide the Spec

"I have this feature spec: [paste your spec]. Convert it into tasks in Corcava. Show me what tasks you'll create before creating them."

What happens:

Continue analyzes the spec
Proposes a list of tasks with titles and descriptions
Shows you the proposed tasks
Waits for confirmation

Step 2: Create Tasks (After Confirmation)

"Yes, create those tasks."

What happens:

Continue calls create_task for each task
Tasks are created in Corcava
Continue confirms what was created

Step 3: Log Progress as Comments

"I've completed the API integration task. Add a comment to that task summarizing what was done."

What happens:

Continue finds the task
Calls add_task_comment with your summary
Comment is added to the task

Troubleshooting SSE Issues

❌ SSE Connection Drops

Symptom: Connection works initially but then disconnects

Possible Causes:

Network instability
Proxy or firewall interrupting long-lived connections
Server-side timeout

Fix:

Check network stability
Verify proxy/firewall allows SSE connections
Try reloading Continue
Check Continue logs for error messages

Read SSE troubleshooting guide →

❌ SSE Connection Timeout

Symptom: Connection fails to establish or times out

Possible Causes:

Network connectivity issues
Firewall blocking SSE connections
Corporate proxy interfering
Incorrect URL or auth header

Fix:

Verify endpoint URL is correct: https://app.corcava.com/mcp
Check auth header format
Test if https://app.corcava.com is accessible
Check network/firewall settings

Read connection troubleshooting guide →

❌ Config Validation Errors

Possible Causes:

Invalid JSON syntax
Missing required fields (name, transport, type, url)
Wrong transport type (should be "sse" for remote)

Fix:

Validate JSON syntax
Ensure "type": "sse" is set
Verify all required fields are present

Read JSON troubleshooting guide →

Best Practices for SSE

SSE-Specific Tips

Keep context minimal: SSE works best with focused requests
Reduce tool calls: Batch operations when possible
Handle disconnects gracefully: Continue should retry automatically
Monitor connection status: Check Continue logs if issues persist

Next Steps

Continue Workflows

Weekly planning and task management prompts

SSE Transport Guide

Learn more about remote MCP servers and SSE

Connect Continue to Corcava

Use SSE transport for remote MCP access

Start Free Trial → Continue Workflows

No credit card required