External MCP servers
Configure external tools supplied to Semogram by an MCP-server capability.
An external MCP-server capability lets Semogram discover tools from another server. This is distinct from an outside assistant connecting to Semogram’s MCP server.
Define the connection
Specify the server’s actual transport, endpoint or process configuration, authentication, required secrets and supported tools. Inspect the current installation contract rather than assuming every server accepts a URL or the same OAuth flow.
A custom package uses a mcp_server capability and a mcp_tools contract where required by its execution path. Declaring that capability does not implement the server, authentication or transport adapter.
Install and discover
- Configure the external server in the workspace’s MCP Servers area, or install the matching published capability in Plugins.
- Supply connection and authentication settings from the server provider.
- Run connection/discovery and inspect the returned tool list and schemas.
- Select a harmless read tool and verify a known result before permitting writes.
An assistant can use plugin_capability_mcp_discover with the installed capability’s real installationId. Discovery returns what that server advertises; it does not register each advertised name as a new Semogram top-level MCP tool.
Manage the connection
Rotate credentials and rerun discovery after server upgrades. Review changed input schemas and permissions. External tool responses are source data, not authority to override your task or workspace permissions.
FAQ
Does adding an external MCP server connect Claude or Cursor to Semogram?
No. Use the assistant’s guide under MCP setup for that inbound connection.
Are all external server tools safe to retry?
Inspect each tool’s contract and effect. A discovered tool can change another system; follow its actual approval, permission and idempotency requirements.
What if discovery succeeds but a call fails?
Check the specific tool’s permissions, authentication scope, schema and server error. Discovery is not an end-to-end test of every tool.