MCP server

Last updated

Argus exposes team memory and review results over the Model Context Protocol. Any MCP client that supports remote servers with OAuth — Claude Code, Cursor, Claude Desktop — can read what Argus learned about your codebase and query past reviews without leaving the agent.

Connect

Point your client at https://api.argus.reviews/mcp. The client discovers the authorization server from /.well-known/oauth-protected-resource, runs a browser login once, and asks you to pick one organization— the connection sees only that org's repos and memory. Switching orgs means authorizing again. Tokens refresh automatically; there are no API keys.

Tools

Call list_repos first — it resolves the local repo_id and installation_id every other tool takes.

  • search_memory, get_memory_briefing — semantic search over team memory, and the briefing Argus gives its own reviewers.
  • create_memory, delete_memory, retire_memory — write and manage memory. Need the argus:memory:write scope.
  • list_reviews, get_review_status, get_review — review history, cheap status polls, and the full review page in one call.

Scopes and guard rails

argus:read covers every read tool; argus:memory:write covers the three memory mutations. A read-only grant cannot mutate memory, whatever flags a call sets.

  • Deleting or retiring a memory the review pipeline learned requires confirm_pipeline_learned=true; writing an org-wide memory requires confirm_shared=true. Neither can be undone.
  • To stop a memory influencing reviews, use retire_memory — delete_memory removes one contributing record and the memory may remain searchable.

Self-hosting

Off by default. Set MCP_ENABLED=true, CLERK_ISSUER_URL (your Clerk Frontend API origin), and MCP_RESOURCE_URL (the public https://…/mcp URL); CLERK_JWKS_URL must already be set. The route 404s while disabled. Full setup, including the Clerk dashboard configuration, is in the README.