Skip to main content
There is no verified first-party hosted MCP service for managing Threetone agents. Do not configure a guessed Threetone MCP URL or assume a documentation search integration can modify workspace resources. The existing MCP server integration stores connections to external servers. It is a different workflow. Server reads can confirm saved configuration. They do not prove connectivity or tool execution. Connection testing is disabled, and tool discovery returns an unavailable result.

Prepare for a future service

Before connecting an assistant to an agent-management service, require a published endpoint, supported authentication, workspace scoping, and an explicit list of read and write tools. Review how it requests approval for publication, deletion, and credential changes. Keep the current public API as the reference for supported management operations. No MCP client configuration or SDK import is required for those API workflows.
No. Registration stores an external server connection; it does not provision or operate that server.
Runtime enforcement still needs a released and verified execution path.