ArgorantDocs

Cursor and other clients

Any MCP client that speaks streamable HTTP with OAuth can connect. Cursor, Windsurf, VS Code, Gemini CLI, and your own runtime.

The server is standard: streamable HTTP at https://mcp.argorant.com/mcp, OAuth 2.1 with PKCE and dynamic client registration. If your client asks for a URL and can open a browser for sign-in, it works.

Cursor

Cursor Settings → MCP → Add new global MCP server, or put this in ~/.cursor/mcp.json:

JSON
{ "mcpServers": { "argorant": { "url": "https://mcp.argorant.com/mcp" } } }

VS Code (Copilot agent mode)

.vscode/mcp.json:

JSON
{ "servers": { "argorant": { "type": "http", "url": "https://mcp.argorant.com/mcp" } } }

Windsurf

~/.codeium/windsurf/mcp_config.json:

JSON
{ "mcpServers": { "argorant": { "serverUrl": "https://mcp.argorant.com/mcp" } } }

Gemini CLI

Shell
gemini mcp add --transport http argorant https://mcp.argorant.com/mcp

Your own runtime

Use any MCP SDK. Discovery lives at https://mcp.argorant.com/.well-known/oauth-protected-resource; register a client at the authorization server's registration endpoint, run the authorization code flow with PKCE, then call argorant_account first. Every tool and its annotations are listed on Tools.

No MCP at all

The REST API and the CLI are the same engine. An agent that can run a shell gets everything with npx argorant … --json.

On this page