TMCP HubOwner submits a provider
A scoped organization owner will submit the exact compatible HTTPS MCP endpoint, provider identity, intended users and upstream authorization model. The request begins pending and inert.
Product 02 · Private remote MCP
Connect a private MCP service through reviewed access.
A compatible standard HTTPS MCP server can be proposed for TMCP admission. The platform never gains another organization's business permissions merely because a provider is listed or approved.
Provider admission plannedGeneric routing not implemented
Planned process
From request to authorized tools
Sole Root reviews admission
TMCP will validate the endpoint and standard protocol, assess network safety, ownership and separate upstream authorization before admitting a provider. A submitted URL is never automatically fetched or executed.
Exact grants control use
Authorized clients will discover only currently granted tools. Upstream MCP retains independent OAuth audience and resource rights; a TMCP token is not forwarded as an upstream token.
Who owns the integration?
Resource owner
A personal user or organization may own and manage its submitted provider under delegated scope. The external business service and its data remain with their real owner.
TMCP catalog distribution
The sole Root controls platform admission and publication; current user/organization grants control availability. A catalog listing does not create upstream business authority or a second global admin.
Organization self-creation, general provider submission, upstream discovery and runtime routing are not available yet. The documentation describes the approved target, not a deployed feature.
For providers and partners
Prepare for a standards-based connection.
Review the intake requirements and approval boundaries. There is no open public endpoint-submission form at present.