Connecting

torqee Connect exposes an MCP Streamable HTTP endpoint at:

https://connect.torqee.app/mcp

The endpoint is stateless on the server side. Each request authenticates with the same workspace-scoped Bearer credentials used by the REST API.

OAuth discovery

MCP clients that support protected resource discovery can start with the MCP URL and follow Connect metadata to the torqee authorization server.

claude mcp add --transport http torqee https://connect.torqee.app/mcp

API key header

Clients that do not run OAuth discovery can send a torqee_ API key as a Bearer token:

{
  "mcpServers": {
    "torqee": {
      "type": "http",
      "url": "https://connect.torqee.app/mcp",
      "headers": { "Authorization": "Bearer torqee_YOUR_API_KEY" }
    }
  }
}

API keys and OAuth tokens are both workspace scoped and use the same read scopes.