External MCP servers

If your workspace already runs its own MCP server, register it on the External MCP servers page (/byomcp). Its tools then join your discovered catalog, and Syncanix forwards tool calls to it — optionally as the signed-in end user.

Register a server

Register a server from the dashboard or the CLI. You provide where it lives, how to authenticate, which tools to expose, and whose identity to forward.

• Server URL — must use https. Syncanix connects to exactly this endpoint.
• Authentication — API key, OAuth bearer token, basic auth, or a custom header. The credential is sent once and stored securely; it is never shown again.
• Allowed tools — an optional allowlist; leave it empty to expose every tool the server advertises.
• Forward calls as — Service uses one shared identity; End user forwards the signed-in user’s identity so the server can act on their behalf.

syncanix byomcp register

Managing a server

Each registered server has a detail drawer for ongoing management, and a status that reflects its health.

• Connection — edit the URL, auth method, and forward-as identity.
• Rotate credential — replace the stored secret; the new value is sent once and never read back.
• Exposed tools — add or remove tool names to tighten or widen the allowlist.
• Status — Active, Disabled, or Needs attention. Enable or disable a server, or remove it to stop its tools reaching the agent immediately.

Next steps