Connect a project MCP

A project MCP makes one MCP server available to agents of a single project. It gives agents controlled access to external tools without mixing permissions across projects.

When to use it

Use it when:

• an existing connector installation exposes an MCP endpoint, for example Gmail, Google Drive or Notion;
• you have an internal or local MCP server to expose to a project squad;
• you want agents to persist or reuse MCP paths in the project context.

Do not use it as a shortcut for sharing secrets across projects. Each project has its own perimeter.

From a connector installation

1. Open the project.
2. Go to External sources.
3. In the Project MCP panel, choose an already configured connector installation.
4. Click the installation to attach it to the project.
5. Test the MCP from the created card.

If the installation does not carry an MCP endpoint, it is not proposed. arka-deck does not expose fake endpoints.

From a custom endpoint

1. Open External sources → Project MCP.
2. Click Add MCP.
3. Enter a display name.
4. Choose HTTP or SSE.
5. Enter the endpoint.
6. Optionally add the allowed tools list.
7. Add it to the project, then test it.

Endpoint policy:

• HTTPS is required for remote endpoints;
• HTTP is accepted only on loopback (127.0.0.1, localhost);
• URLs with embedded credentials are refused;
• external runtime names are prefixed with connector_*.

What the agent receives

When the test succeeds, arka-deck adds the MCP server to the provider runtime of project agents. The agent sees a connector_* MCP server and can use the tools allowed by the project policy.

Another project does not receive this MCP unless it is attached there too.

Security

• Secrets are not copied into the project MCP file.
• Connector installations keep their encrypted credential.
• Write actions must request approval when the connector declares it.
• Removing the project MCP stops exposing it to agents without deleting the connector installation.