Skip to main content
Once the MCP Server is enabled, the panel shows a Connect an assistant section. Pick your tool and copy the connection details — they already carry your project’s address, so there’s nothing to type by hand.
Every tool below connects to the same MCP Server. What differs is where you paste the connection details and how the tool authenticates. The exact URL and config are shown in the panel — copy them from there rather than typing them.
Claude connects as a custom connector.
1

Copy the Claude URL

In the panel’s Claude tab, copy the connection URL. Claude needs the per-project address the panel shows for it.
2

Add the connector

In Claude, open Settings → Connectors → Add custom connector and paste the URL.
3

Authenticate

A window opens — sign in with your project account (or, on API-key projects, the config includes the Authorization header to fill in). Approve the tools.
For Claude Code (the CLI), the panel also gives you a ready claude mcp add ... command — run it in your terminal.

​
Sign-in vs. API key

The connection details adapt to your project’s authentication providers:
  • Sign-in (identity): connecting opens a login window — no token to paste. Best for human users.
  • API key: the config includes an Authorization: Bearer header. Create a key under Backend → App Services → Authentication Providers and replace the placeholder. Best for automated agents and CI.
Treat a project API key like a password. It carries the permissions of the role it belongs to. Store it in a secret manager, never commit it, and rotate it if it leaks.

​
Refreshing after a change

Assistants cache the server’s details from when you connected. If you change the server’s name, icon, or description — or switch authentication — disconnect and reconnect the connector so the assistant reads the new details.

​
FAQ

Claude derives the sign-in server from the connection URL, so its address carries the project in the host. The panel shows the correct URL for each tool — always copy Claude’s URL from the Claude tab.
Yes. The MCP Server accepts connections from any number of tools and users at once. Each connection authenticates independently and runs with that user’s permissions.
No. Enabling the MCP Server and copying the connection details is all that’s required on Archie’s side.