Quickstart

The first run has one goal: keep the agent disposable while its access and context remain on the server.

1. Add CoreSpeed to your MCP client

Point the client at the unified Streamable HTTP endpoint and authenticate with your CoreSpeed key:

{
  "mcpServers": {
    "corespeed": {
      "type": "http",
      "url": "https://api.corespeed.io/mcp",
      "headers": {
        "Authorization": "Bearer sk-cs-..."
      }
    }
  }
}

Replace sk-cs-... before pasting the configuration. Keep the key out of source control and shared configuration files.

2. Confirm the visible tool surface

Most MCP clients run tools/list automatically. To inspect the same authenticated surface directly:

curl https://api.corespeed.io/mcp \
  -H "Authorization: Bearer $CORESPEED_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

Tool names are namespaced as <capability>__<operation>. Before any connector is attached, the response already lists the built-in tools this caller can run (memory and image generation). Account-management (manage__*) tools also appear, but they execute only under a human WorkOS session — calling one with an API key through unified /mcp returns HTTP 200 with result.isError: true and a jwt_session_required payload. Only the standalone management route returns HTTP 403.

3. Connect software in the dashboard

Open Dashboard → Connectors, choose a connector, and authorize an account. The OAuth token stays with CoreSpeed; the agent receives callable tools, not the provider credential.

Run tools/list again. A connected provider now contributes its namespaced tools to the same /mcp endpoint. You do not add another MCP server.

4. Use a connector and memory

Ask the client to perform a task with the connected account, then preserve one piece of context for the next run. For example:

Read the launch thread from our connected X account, save the decision brief
to Notion, then remember that rollout requires a two-day review window.

To verify memory without relying on an agent planner, call the tool directly:

curl https://api.corespeed.io/mcp \
  -H "Authorization: Bearer $CORESPEED_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 2,
    "method": "tools/call",
    "params": {
      "name": "memory__remember",
      "arguments": {
        "memory": "Rollout changes require a two-day review window.",
        "scope": "shared"
      }
    }
  }'

Now open a different MCP client with the same CoreSpeed identity and ask it to search memory. The software connection and durable context remain available without repeating either setup.

What just happened

Next steps