MCP reference
Connection ownership, authentication and configuration
A connection identifies the server, its authentication and the scope in which its tools can be used.
Where to manage connections
Use Agent → MCPs for installed connections, the marketplace and custom servers. A public integrations page helps you discover services; the signed-in connection status tells you whether a service is ready to use.
Authentication
Catalog providers commonly use their own sign-in and consent flow. Custom remote servers can require an endpoint and a bearer token. Follow the provider's requirements and the fields shown by PlutoAI; there is no single no-keys flow that applies to every server.
Saved credentials are handled by the server. Enter them through the appropriate connection controls rather than including them in a project prompt or source file.
Ownership and scope
- Personal connections belong to their account owner.
- A connection explicitly attached to a shared chat can be used there according to the chat's permissions.
- Sharing a chat does not share all of its owner's personal connections.
- Only the connection owner can edit protected settings, attach integrations or disconnect the chat's connections.
If you see a settings conflict, preserve your draft, reload the current settings and review the differences before retrying. Repeatedly saving an outdated copy will not resolve the conflict.
Connection health
A saved configuration may still fail authentication, endpoint checks or tool discovery. Inspect the displayed error. If consent has expired, reconnect through the provider. If an endpoint or token changed, the owner should update the connection.
See Connect MCP tools and Custom MCP.