CDP Index

Install

4 min read

Install

AI Quick Start

OpenAI Codex Claude Code Cursor

Use the public Cloudflare MCP endpoint when you want an agent to use this knowledge base without Git credentials or a local clone.

https://cdp-index.pages.dev/mcp

The custom domain is protected by Cloudflare Access, so use https://cdp-index.pages.dev/mcp for no-creds agent setup.

Cloudflare Managed Portal

Cloudflare MCP server portals are managed under Zero Trust > Access controls > AI controls. They require a dedicated hostname that points at Cloudflare’s MCP portal gateway, then expose MCP at /mcp.

Target portal:

https://cdp-index-mcp.bakerstreet.tech/mcp

Upstream MCP server:

https://cdp-index.pages.dev/mcp

Cloudflare setup:

  1. Add an MCP server with server ID cdp-index, authentication Unauthenticated, and HTTP URL https://cdp-index.pages.dev/mcp.
  2. Create an MCP server portal with portal ID cdp-index-portal, hostname cdp-index-mcp.bakerstreet.tech, and include the cdp-index server.
  3. Create a proxied CNAME for cdp-index-mcp.bakerstreet.tech pointing to gateway.agents.cloudflare.com if the portal was created through the API or Terraform.
  4. Add Access policies for the portal and for the cdp-index MCP server entry so allowed users can see the server in the portal.

Equivalent Cloudflare API endpoints:

POST /accounts/{account_id}/access/ai-controls/mcp/servers
POST /accounts/{account_id}/access/ai-controls/mcp/portals

The currently configured deployment tokens can deploy the Pages MCP endpoint and read normal Access apps, but Cloudflare returns Authentication error for the AI Controls MCP API. Use a Cloudflare token with Zero Trust Access/AI Controls write access before provisioning the managed portal.

For Claude or other MCP clients that need browser-based portal auth, Cloudflare recommends mcp-remote:

{
  "mcpServers": {
    "cdp-index": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://cdp-index-mcp.bakerstreet.tech/mcp"
      ]
    }
  }
}

Codex

Add the hosted MCP server:

codex mcp add cdp-index --url https://cdp-index.pages.dev/mcp

Restart Codex Desktop or open a new thread, then run /mcp to confirm cdp-index is connected.

Claude Code

Add the hosted MCP server:

claude mcp add --transport http cdp-index https://cdp-index.pages.dev/mcp

Restart Claude Code or open a new session. The tools should appear as:

mcp__cdp-index__search_index
mcp__cdp-index__search_index_docs
mcp__cdp-index__list_index_docs
mcp__cdp-index__get_index_doc
mcp__cdp-index__list_index_tools
mcp__cdp-index__describe_index_tool
mcp__cdp-index__list_agent_tools
mcp__cdp-index__describe_agent_tool
mcp__cdp-index__index_status
mcp__cdp-index__save_conversation_snapshot

Microsoft Teams and Copilot

Use the same public MCP endpoint for Microsoft 365 Copilot and Teams agent experiments:

https://cdp-index.pages.dev/mcp

Fastest Copilot Studio path:

  1. Open the target agent in Copilot Studio.
  2. Go to Tools.
  3. Select Add a tool > New tool > Model Context Protocol.
  4. Enter:
    • Server name: CDP Index
    • Server description: Search CDP Index project memory, partner notes, connectors, workflows, and operating documentation.
    • Server URL: https://cdp-index.pages.dev/mcp
    • Authentication: None
  5. Create the tool, add the MCP tools to the agent, then test with: Search CDP Index for MCP setup.

Teams / Microsoft 365 Copilot agent path:

  1. Use Microsoft 365 Agents Toolkit in VS Code.
  2. Create a new declarative agent.
  3. Add an action and choose Start with an MCP server.
  4. Enter https://cdp-index.pages.dev/mcp.
  5. Select the tools to expose, usually:
    • search_index
    • search_index_docs
    • list_index_docs
    • get_index_doc
    • list_index_tools
    • describe_index_tool
    • list_agent_tools
    • describe_agent_tool
    • index_status
    • save_conversation_snapshot
  6. Test locally through Microsoft 365 Copilot, then package and publish the agent to Teams/Microsoft 365 through the tenant approval flow.

Do not use https://cdp-index.bakerstreet.tech/mcp for Copilot or Teams unless the Microsoft connector is configured with Cloudflare Access service-token headers. Without that, Microsoft clients receive the Cloudflare Access login redirect instead of MCP JSON-RPC.

Local Repository Setup

Use these links only when you want to open the Git-backed repository in an agent and configure the local MCP server from mcp/.

  • Open in Codex: uses Codex originUrl matching to find a local workspace with the https://gitlab.com/baker-street/cdp-index remote.
  • Open in Claude Code: uses Claude Code cwd matching for this local clone. Claude Code’s repo= deeplink is GitHub owner/name based, so use cwd= for non-GitHub repositories.

If the clone is not present locally:

git clone https://gitlab.com/baker-street/cdp-index.git /Users/andrewmagu/src/cdp-index

Configure the local stdio MCP server:

claude mcp add --transport stdio cdp-index -- node /Users/andrewmagu/src/cdp-index/mcp/dist/server.js
codex mcp add cdp-index -- node /Users/andrewmagu/src/cdp-index/mcp/dist/server.js

Sources checked: Claude Code deep links, Claude Code MCP, Codex app deep links, Codex MCP, Copilot Studio MCP onboarding, Microsoft 365 agent connectors for MCP.

Graph View