Custom integrations
Register a custom MCP server for your organization.
A custom integration is an MCP server your org runs or trusts that isn't in Proliferate's catalog. Once registered it behaves like any catalog row: members see it in their own Settings and connect it themselves.
| Who | Owner or admin |
| Affects | The organization — creates a definition every member can see |
| Plan | No plan requirement |
| Local / Cloud | Same either way |
Add by URL
Settings > Organization > Integrations > Add custom MCP.
| Field | Notes |
|---|---|
| Display name | Shown to members in their Settings and in the org table. |
| Namespace | Prefixes the integration's tool names for agents. Lowercase letters, digits, _, -; must start with a letter or digit. functions is reserved. |
| MCP URL | Any http:// or https:// endpoint. |
The definition is created enabled for the org immediately, no separate save step.
Authentication
The Authentication selector picks how members will connect to the server:
| Option | What it does |
|---|---|
| Auto-detect | Probes the server when you add it and picks up the auth scheme it advertises. |
| None | The server needs no credential; members connect in a single click. |
| OAuth | The server speaks OAuth. Proliferate registers a client automatically via Dynamic Client Registration, and each member then connects with their own account. |
Custom API-key auth is the one thing this form does not support today. If the server you point at only authenticates with a static API key, it isn't connectable through this flow yet.
What members see
Once added and enabled, the integration shows up in every member's own Settings > Integrations. If it needs no credential, connecting is a single click; if it uses OAuth, each member connects their own account first. See Adding an integration for that flow.