The current Test Connection button is disabled, and server tool discovery returns an unavailable result. Saving the server is a configuration operation. It does not verify transport connectivity, tool discovery, approvals at runtime, or execution.
Recording pending: Review and save an MCP server configuration. Follow the written guide below.
Before you begin
Have a documented endpoint, its supported transport, its operator, and its authentication requirements. Use an account allowed to manage workspace tools. Keep credentials in the supported auth-connection or secret workflow.Save the configuration
1
Open the server form
Open Integrations and select Add MCP server. Enter a useful Name and an optional Description.
2
Set the endpoint and transport
Set Transport Protocol to the server’s documented Server-Sent Events (SSE) or Streamable HTTP transport. Enter the Server URL and select an appropriate auth connection if required. Review any configured request headers and metadata.
3
Review approval intent
Review the tool approval mode and other settings against the actions this server exposes. A stored approval policy does not establish runtime enforcement. Avoid granting broad mutation access merely to simplify configuration.
4
Acknowledge the operator and save
Select I trust this server only after reviewing its operator and data access. Threetone does not verify custom servers through that checkbox. Select Add Server, then reopen the entry to inspect the saved endpoint, transport, credential reference, and identifier.
Screenshot pending: Add MCP server showing endpoint, transport, auth reference, and approval mode, with private values hidden.
Attach the server
The agent’s Tools > MCP tab currently opens the workspace server list and its details. Selecting an entry there does not save an agent attachment. Use Update agent with an explicitbranch_id to author conversation_config.agent.prompt.mcp_server_ids. Preserve the intended existing server references when replacing that list. Read the selected branch and resulting version back to confirm the saved identifier. Follow versions and drafts when reviewing a complete server draft.
Shared server configuration changes and agent publication are separate actions. Review agents that reference a server before changing or removing it. Retain a server-side record of the resource IDs your integration needs.
Plan execution verification
When discovery and execution are released, confirm the actual tools and schemas returned by the server. Test credential scope, read and write permissions, required confirmations, endpoint failures, and changed tool definitions. Instructions returned by an external server do not override your application’s access policy. The Create MCP server and Update MCP server configuration pages describe the committed public schemas. Check operation permissions before using a programmatic credential.Frequently asked questions
Does Add Server test the endpoint?
Does Add Server test the endpoint?
No. The reviewed create path stores the configuration. The disabled Test Connection control and unavailable tool discovery must not be interpreted as successful tests.
Does I trust this server mean Threetone verified it?
Does I trust this server mean Threetone verified it?
No. You acknowledge the custom server’s operator and intended access. Review the provider independently before sending data or credentials.
Is a saved approval policy sufficient?
Is a saved approval policy sufficient?
No. Confirm enforcement and the actual tool contract when the execution path is released. Storing a policy alone does not demonstrate a confirmation step.