MCP authentication and setup

Astute starts with a hosted MCP and local bridge so users can refine guided flows inside the AI apps they already use.

Access status
The hosted endpoint uses Clerk OAuth before MCP clients can call Astute tools.
Hosted endpoint
https://mcp.astute.sh
Auth server
auth.astute.sh
Transport
Streamable HTTP
Authentication
Clerk OAuth
{
  "mcpServers": {
    "astute": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.astute.sh"]
    }
  }
}
Authenticate
Sign in through auth.astute.sh with the same Clerk account used on astute.sh.
Connect client
Choose Codex, Cursor, Claude, or another compatible client and download the right config.
Run guided flows
Use admin, BA, student, project officer, and AI onboarding flows from the host app.

Client setup targets

The website keeps each client path explicit because users need direct instructions, not abstract protocol language.

Codex
Use Astute flows while building and refining workflows.
Cursor
Bring guided requirements and admin flows into code work.
Claude
Connect through remote MCP or a local proxy command.
Auth boundary
Remote tools stay deterministic while Clerk OAuth and later entitlement checks protect hosted access.
Guardrail
Download MCP
Use the downloads page for hosted config, local bridge commands, and later desktop app files.
Open downloads