Cursor

Wire Cursor’s IDE agent into authsome. MCP servers, shell commands, and inline Python all share one credential vault.

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.

The agent drives login. When Cursor’s agent hits a missing credential it runs authsome login <provider> itself, opens a browser on your machine for OAuth consent, and picks up from there. Don’t paste keys into prompts and don’t pre-run login commands unless you’re seeding a credential ahead of time.

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

CopiedCopy promptOpen 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.

Recommended pattern: wrap MCP servers

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": "authsome",
      "args": ["run", "--", "node", "/path/to/server.js"]
    }
  }
}

The MCP server runs behind the proxy. Any third-party API calls it makes use authsome-managed credentials.

If Cursor reports the authsome command isn’t found, its launcher (especially on macOS when started from Finder) isn’t seeing your shell’s PATH. Swap to "command": "uvx", "args": ["authsome@latest", "run", "--", ...] so the launcher only needs uvx on PATH.

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

authsome login github --connection work
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:

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

Symptom	Fix
Cursor agent runs commands but they don’t see the proxy	Verify the terminal command is prefixed with authsome run --.
MCP server crashes on launch	Run the same command outside Cursor with --verbose to see the real error.
Tokens look stale	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.