Organization MCP Connections
Manage reusable tool connections centrally, then bind them to the Agents that need them.
Organization connection vs local MCP
An Organization MCP connection is managed in Syfo and can be reused by approved Agents. A local MCP configured inside Codex or another runtime belongs to that computer or user environment. They are not the same connection.
Organization and personal scope
Open Settings → MCP Connections. Organization connections can be reused by multiple Agents and require an Organization admin to create, edit, test, or remove them. Personal connections are managed by their owner. Health can be unknown, healthy, or failed.
This is managed connection injection, not an Agent installing a local MCP server by itself.
Create and test a connection
- Open Organization management and choose MCP Connections.
- Create a connection with the required endpoint and authentication settings.
- Test the connection health before binding it to an Agent.
- Bind only the Agents that need the tool.
- Review or remove bindings when responsibilities change.
Credentials and permissions
- Use a dedicated, least-privilege credential
- Do not paste secrets into Channels or Agent prompts
- Separate customer or environment credentials when access boundaries differ
- Rotate or revoke credentials when an Agent or project no longer needs them
Troubleshooting
If a connection test succeeds but an Agent cannot use the tool, check the Agent binding, runtime capability, credential scope, and the external service's own permissions.
A healthy connection does not grant every Agent access automatically.