Connect Your AI Agent via MCP

The Phenom Int-Docs MCP server at https://int-docs-mcp.thephenom.app/mcp exposes all internal documentation and runbooks as MCP tools. Any AI agent that supports the Model Context Protocol can query, search, and retrieve content directly.

Prerequisites

You need a Phenom Cognito account (the same login you use for int-docs.thephenom.app).

Step 1 — Get your token

Visit the token endpoint in your browser:

https://int-docs-mcp.thephenom.app/token

If you are not already logged in, Cloudflare Access will redirect you to the Cognito login page. Once authenticated, the page returns your personal Bearer token and ready-to-paste config blocks for common MCP clients.

Your token is valid for 90 days. To rotate it, visit the same URL again.

Step 2 — Add to your MCP client

Claude Code

Add to ~/.claude/settings.json:

{
  "mcpServers": {
    "phenom-int-docs": {
      "type": "http",
      "url": "https://int-docs-mcp.thephenom.app/mcp",
      "headers": {
        "Authorization": "Bearer <your-token>"
      }
    }
  }
}

Replace <your-token> with the itk_... value from Step 1. The token page shows this block pre-filled with your actual token.

Cursor / Windsurf / other MCP clients

Add to .cursor/mcp.json (or your client’s MCP config file):

{
  "mcpServers": {
    "phenom-int-docs": {
      "url": "https://int-docs-mcp.thephenom.app/mcp",
      "headers": {
        "Authorization": "Bearer <your-token>"
      }
    }
  }
}

Available tools

Once connected, your agent has access to:

Provenance

Every runbook carries a C2PA Content Credential signed by sign.trusteddit.com via the Trusteddit-Journalist-Issuer-CA. The get_runbook and list_audit_stamps tools surface the signer identity, issuer CA, TSA timestamp, and audit state so your agent can reason about document freshness and trust.

Troubleshooting

401 Unauthorized – your token may have expired (90-day TTL). Visit https://int-docs-mcp.thephenom.app/token to get a new one.

Redirected to Cognito login – you are not currently logged in. Complete the login and you will be redirected back to the token page automatically.

Token page says “KV namespace not bound” – contact the platform team; this is a server configuration issue.