SquidX logo
Open SquidX

Any MCP client

SquidX speaks Streamable HTTP, stateless, with JSON responses. A client that understands OAuth 2.1 signs in on its own.

SquidX speaks Streamable HTTP, stateless, with JSON responses. A client that understands OAuth 2.1 signs in on its own.

  1. 1

    Point the client at the server

    Use the URL below as a remote server of type http. If the client supports OAuth 2.1, that is all: the 401 points to https://squidx.io/.well-known/oauth-protected-resource and the rest follows the spec.

    text
    https://squidx.io/api/mcp

Or send an API key

A client that cannot do OAuth sends the key as a bearer token.

json
{
  "type": "http",
  "url": "https://squidx.io/api/mcp",
  "headers": {
    "Authorization": "Bearer sqx_your_key"
  }
}

Check it worked

Ask the assistant to call squidx_get_workspace. It returns the workspace name, plan and timezone.

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