Skip to main content

Documentation Index

Fetch the complete documentation index at: https://authsome.agentr.dev/docs/llms.txt

Use this file to discover all available pages before exploring further.

Cursor is an AI-first code editor. Its agent surface includes inline AI calls, MCP servers, and shell-tool execution. Authsome plugs in at the MCP layer: register your MCP servers with authsome wrappers, and the proxy injects fresh credentials whenever a tool calls an external service.

Wrap your MCP servers with authsome. Open this prompt in Cursor to apply it.

CursorOpen in Cursor

​
What you get

  • MCP servers wrapped by authsome run get tokens injected into outbound HTTP requests automatically. The server process never sees the raw secret.
  • One credential vault shared with the regular CLI, with Claude Code, and with anything else on the machine.
  • Multi-account flows work the same as on the CLI.
Cursor reads MCP server definitions from ~/.cursor/mcp.json (global) or .cursor/mcp.json in a workspace. Wrap each server’s launch command with authsome run --: 
{
  "mcpServers": {
    "my-mcp": {
      "command": "uvx",
      "args": ["authsome", "run", "--", "node", "/path/to/server.js"]
    }
  }
}
The MCP server runs behind the proxy. Any third-party API calls it makes use authsome-managed credentials.

​
Embedding the library

If you’re driving Cursor from a Python orchestrator, or running inline Python tasks that need explicit credential control, drop below the proxy: 
from authsome.server.dependencies import create_auth_service

auth = create_auth_service()
token = auth.get_access_token("github", connection="default")
See Python library.

​
Multiple accounts per provider

uvx authsome login github --connection work
uvx authsome login github --connection personal
The proxy uses each provider’s default connection. To run Cursor against a specific connection, set it as the default with --force: 
uvx authsome login github --connection work --force
Per-request connection selection inside Cursor is not yet supported. See Multiple connections per provider.

​
TLS interception

Cursor’s built-in HTTP clients honor HTTP_PROXY. Third-party MCP servers sometimes use TLS pinning or their own CA bundle. If you see TLS errors from a specific MCP server, point its environment at the mitmproxy CA: 
export REQUESTS_CA_BUNDLE=~/.mitmproxy/mitmproxy-ca-cert.pem
export SSL_CERT_FILE=~/.mitmproxy/mitmproxy-ca-cert.pem
The general guidance is in Proxy networking.

​
Troubleshooting

SymptomFix
Cursor agent runs commands but they don’t see the proxyVerify the terminal command is prefixed with uvx authsome run --.
MCP server crashes on launchRun the same command outside Cursor with --verbose to see the real error.
Tokens look staleuvx authsome get <provider> --field status from a terminal Cursor wraps.

​
What’s next

Run agents with the proxy

The proxy injection model.

Multiple connections per provider

Per-account workflows.