API Preview - This API is under active development. Endpoints may change without notice.

Cursor & Cline

Both editors connect to a remote MCP server by URL. Add ~alter to the editor's MCP config and its identity tools appear in the agent. Anonymous tools work with no account; connect via OAuth to reach the authenticated tools.

Connection

Endpoint	`https://mcp.truealter.com/api/v1/mcp`
Transport	Streamable HTTP (JSON-RPC 2.0 over POST)
Auth header	Authorization: Bearer <capability_token> (omit for anonymous tools)
Config	Cursor: .cursor/mcp.json · Cline: cline_mcp_settings.json

Setup

1Cursor

Add ~alter to .cursor/mcp.json in the project, or ~/.cursor/mcp.json globally. Cursor infers Streamable HTTP from the url, so no transport field is needed.

json

{
  "mcpServers": {
    "alter": {
      "url": "https://mcp.truealter.com/api/v1/mcp",
      "headers": { "Authorization": "Bearer <capability_token>" }
    }
  }
}

2Cline

Add the same server to cline_mcp_settings.json. Cline accepts a remote server by url with headers.

json

{
  "mcpServers": {
    "alter": {
      "url": "https://mcp.truealter.com/api/v1/mcp",
      "headers": { "Authorization": "Bearer <capability_token>" },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Verify

Open the MCP panel in either editor. ~alter should show as connected with its tool list.

Notes

-Neither client needs a transport or type field; both infer Streamable HTTP from the url. Drop the headers block for anonymous access.
-Cursor supports ${env:VAR} interpolation in the header value if you would rather not hard-code the capability token.
-If Cline shows the server using the older SSE transport after adding, re-check that it negotiated Streamable HTTP.

MCP server reference Tools reference Connect via OAuth Cursor MCP docs ↗