Using Aegis MCP Servers in Claude Desktop

Aegis uses the Model Context Protocol (MCP) to expose internal tools directly to Claude Desktop.

Because Aegis is a microservices architecture, the Aegis Admin MCP Server acts as the primary Edge Router. It hosts its own tools (like routing and compliance audits) and automatically proxies requests to internal microservices (like Nudger) via Cloudflare Service Bindings.

The Aegis Admin MCP Edge Router

You only need to connect Claude Desktop to this single endpoint to access tools across the entire Aegis ecosystem.

  • URL: https://aegis.purdyandfigg.dev/api/mcp
  • Tools Included:
    • list_routes
    • lock_route
    • unlock_route
    • page_audit
    • nudger_card_state (Proxied to Nudger)
    • nudger_todo_list_status (Proxied to Nudger)
    • nudger_overall_summary (Proxied to Nudger)
    • nudger_qa_test (Proxied to Nudger)

How to Add Aegis to Claude

Because Aegis is already configured in the Claude Organization Settings, you do not need to manually edit any JSON configuration files!

To add it:

  1. Open Claude Desktop.
  2. Go to Customise.
  3. You will see Aegis Admin MCP Edge Router available in the organization's tools list.
  4. Simply click to add/enable it.

How to Refresh Tools in Claude Desktop

If a new tool (like nudger_qa_test) is added to the codebase but you don't see it in Claude yet:

  1. Wait for Deployment: Ensure the latest code has been pushed to production (npm run deploy:admin).
  2. Refresh Claude: Completely quit Claude Desktop (Cmd + Q on Mac, or right-click the dock icon and hit Quit) and reopen it. Claude fetches the freshest tool list every time it starts up.