SquidX logo
Open SquidX

Cursor

Put the server in an mcp.json file. Cursor reads it from the project or from your home folder.

Put the server in an mcp.json file. Cursor reads it from the project or from your home folder.

  1. 1

    Add the server

    Save this as .cursor/mcp.json in the project, or as ~/.cursor/mcp.json to use SquidX in every project.

    json
    {
  "mcpServers": {
    "squidx": {
      "url": "https://squidx.io/api/mcp"
    }
  }
}
  2. 2

    Sign in when asked

    The server asks for a sign-in the first time the agent uses it. Sign in to SquidX in the browser and choose what Cursor may do.

Or use an API key

Add a header instead, and keep the key in an environment variable. Cursor fills ${env:NAME} in url and headers.

json
{
  "mcpServers": {
    "squidx": {
      "url": "https://squidx.io/api/mcp",
      "headers": {
        "Authorization": "Bearer ${env:SQUIDX_API_KEY}"
      }
    }
  }
}

Check it worked

Open the agent chat and ask: "What is in my SquidX queue this week?" If SquidX answers, the server is connected.

We have not tested these steps end to end yet. If something looks different on your screen, the vendor's own page is the reference.

Troubleshooting

The client says it could not register with the sign-in service
The discovery documents did not answer. Check that https://squidx.io/.well-known/oauth-authorization-server loads in a browser, then remove the server and add it again.
I get a 401 with an API key
The header is missing or the key is wrong. It is Authorization: Bearer sqx_..., with the space.
The assistant has no write tools
The access is read only. Disconnect the app in Settings, then sign in again with Read and write, or create a key with it, and reconnect so the client fetches the tool list again.
A tool answers inactive
The workspace has no active plan. Drafts still work. Queuing and publishing need a subscription or credits.
Full reference