Skip to content

Easy setup

Step-by-step instructions for adding this connector to the assistant you already use. No API key needed — see Install if you want a named key instead of the shared public one.

The connector URL you'll need throughout:

https://mcp.chancerylaneproject.org/mcp

Claude (claude.ai, Claude Desktop, Cowork)

Claude Desktop, claude.ai and Cowork share one account, so a connector added once is available everywhere you're signed in.

Individual (Pro/Max) accounts:

  1. Go to Settings → Connectors.
  2. Click +, then Add custom connector.
  3. Paste the connector URL above.
  4. Leave Advanced settings (OAuth) blank — this connector doesn't need it.
  5. Click Add.

Team/Enterprise accounts:

  1. An owner goes to Organization settings → Connectors, clicks Add, then Custom → Web, and pastes the connector URL.
  2. Members then go to Settings → Connectors, find the connector, and click Connect.

Once added, enable it per conversation: click + in the chat box, choose Connectors, and toggle it on.

Microsoft 365 Copilot (Copilot Studio)

Microsoft 365 Copilot reaches MCP servers through an agent built in Copilot Studio. You need maker access to a Power Platform environment; your tenant admin may also have to approve the connector under your data policies. Copilot Studio supports the Streamable HTTP transport this connector uses.

Add the connector as a tool:

  1. Open your agent in Copilot Studio (or create one), go to Tools, and select Add a tool → New tool → Model Context Protocol.
  2. Fill in Server name (e.g. "TCLP Knowledge Graph"), Server description (what it does — the orchestrator uses this to decide when to call it), and Server URL: the connector URL above.
  3. Choose the authentication type:
    • None — connects with the shared public key. Fine for trying it out.
    • API key — for a named key. Set Type to Header and the header name to X-Api-Key. (Query with the parameter name api_key also works, but the key may then appear in logs.)
  4. Select Create, then on Add tool select Create a new connection — supply your named key here if you configured API key authentication — and Add to agent.

Make it available in Microsoft 365 Copilot: publish the agent, then add it under Channels → Microsoft 365 Copilot. Users pick the agent in the Copilot sidebar or chat. Tenant policy may require admin approval before the agent appears.

Consumer Copilot

The free Microsoft Copilot app at copilot.microsoft.com doesn't take custom MCP connectors. This route needs Microsoft 365 Copilot with Copilot Studio.

ChatGPT

  1. Open Settings → Connectors, click Advanced, and turn on Developer mode (Plus, Pro, Team, Enterprise, or Edu — free ChatGPT doesn't support custom connectors).
  2. Back in Settings → Connectors, click Create.
  3. Enter a Name (e.g. "TCLP Knowledge Graph") and the connector URL above.
  4. Leave authentication unset and confirm you trust the provider.
  5. Click Create, then enable Developer Mode and the connector in the chat you want to use it in.

Notes

A note on keys in URLs

Some clients only offer a plain URL field with no way to set a custom header. If you're using a named key rather than the shared public one, you can still pass it as ?api_key=YOUR_API_KEY on the connector URL — see Authentication for the trade-off against the X-Api-Key header.

Having trouble? Check Install for the full connection reference, or contact TCLP.