🔌Connect your AI assistant

MetaCopier is not listed in the connector directories of ChatGPT, Claude or any other host, so searching for it there finds nothing. You add the MCP server yourself as a custom connector. It takes about a minute and works on every host that speaks MCP.

Adding it yourself is the better setup anyway. The project becomes part of the URL, so the assistant can never end up on a project you did not mean.

---

Set it up

Step 1: Get your project id

The project id is the UUID of the project. You find it in the MetaCopier web app on the project, and it is returned by the REST API on GET /rest/api/v1/projects. It looks like this:

3f6b0c22-8d41-4a7e-9f0e-2c5b1d7a44e9

Step 2: Build the URL

https://ai.metacopier.io/p/{projectId}/mcp

For the example above:

https://ai.metacopier.io/p/3f6b0c22-8d41-4a7e-9f0e-2c5b1d7a44e9/mcp

You can narrow the URL further, for example to read only access or to a single toolset. See endpoints and toolsets.

Step 3: Choose how to authenticate

Both work on this URL:

• OAuth. Add the URL as a custom connector. The host discovers MetaCopier's sign in flow on its own, you sign in, and because the project is in the URL, the oldest project rule does not apply.

• API key. Create an API key in the project and send it as a header. This is the only option for clients that cannot do OAuth.

Step 4: Configure your client

ChatGPT

Go to Settings → Connectors, choose Create or Add custom connector, paste the URL and pick OAuth. Some plans hide this behind Advanced → Developer mode. ChatGPT signs you in and stores the connection.

If you prefer an API key, use the header X-API-KEY where the connector form asks for authentication.

Claude (web, Desktop)

Go to Customize → Connectors → Add custom connector and paste the URL. On a Team or Enterprise plan an owner adds it once under Organization settings → Connectors, then every member connects to it individually.

Claude discovers the sign in flow on its own, so there is nothing else to configure. Enable the connector per conversation through the + button.

Claude Code

claude mcp add metacopier --scope user --transport http \
  https://ai.metacopier.io/p/3f6b0c22-8d41-4a7e-9f0e-2c5b1d7a44e9/mcp

--scope user makes the server available in every folder you work in instead of only the current one. Then type /mcp in Claude Code and authenticate. For an API key instead, append --header "X-API-KEY: YOUR_API_KEY".

Claude Desktop also accepts the classic configuration file:

{
  "mcpServers": {
    "metacopier": {
      "type": "http",
      "url": "https://ai.metacopier.io/p/3f6b0c22-8d41-4a7e-9f0e-2c5b1d7a44e9/mcp",
      "headers": {
        "X-API-KEY": "YOUR_API_KEY"
      }
    }
  }
}

Leave headers out for OAuth.

Cursor, VS Code and other editors

{
  "servers": {
    "metacopier": {
      "type": "http",
      "url": "https://ai.metacopier.io/p/3f6b0c22-8d41-4a7e-9f0e-2c5b1d7a44e9/mcp",
      "headers": {
        "X-API-KEY": "YOUR_API_KEY"
      }
    }
  }
}

Anything else

The server speaks streamable HTTP MCP and is stateless, so any compliant client works. Send your requests as JSON-RPC over POST to the URL and add one of:

X-API-KEY: YOUR_API_KEY

Authorization: Bearer YOUR_API_KEY

Step 5: Verify

Ask the assistant:

Describe this connection and list my accounts.

If it answers with your project and your accounts, you are connected.

---

Which project does it use?

The project in the URL, always. If you leave it out and connect to https://ai.metacopier.io/mcp, for example because your client cannot store a long URL, MetaCopier has to pick one for you:

The oldest project you own wins.

The rule in full:

1. Only projects you own are considered. Projects that were shared with you by someone else are not.

2. Deleted projects are skipped.

3. White label projects are skipped. A white label project belongs to another brand, so a generic MetaCopier connection does not speak for it.

4. Of what remains, the oldest project is chosen, meaning the one you created first.

5. If nothing qualifies, the connection fails with [PROJECT_NOT_FOUND].

An example. You created project A in 2023, project B in 2024, and a partner shared project C with you. A connection without a project in the URL works on A.

You can always check which project you ended up on. Just ask the assistant:

Which project are you connected to?

It will call metacopier_describe_connection and tell you the project id, whether it may write, and when the current credential expires.

If you own more than one project, do not rely on this rule. Put the project in the URL.

---

Both at once

Nothing stops you from adding the connector twice, for example one entry per project, or one read only entry for everyday questions and one full entry for the rare moment you want the assistant to change something. Give each entry a name you recognise in the client.