truefoundry-mcp-servers

To register remote MCP servers, you apply a manifest via tfy apply or the REST API within TrueFoundry. This centralizes discovery and applies guardrails, requiring user confirmation before the server creation action completes.

Yes, you can wrap external OpenAPI specs as MCP servers to expose a consistent tooling surface to agents. This registration process integrates the API into TrueFoundry's centralized access control and discovery system.

Secret handling for virtual MCP servers is enforced through tfy-secret references. This mechanism securely injects required credentials during registration, ensuring sensitive data is managed safely without exposure.

MCP registrations include security gates and collaborator management options to enforce access control. Users can list, update, and delete registrations while managing TLS settings and requiring explicit confirmation for destructive actions.

User confirmation is explicitly required before create and delete actions for MCP server registrations. Updates to existing registrations, including TLS settings and collaborator management, can be applied via tfy apply.

The best way to manage TLS settings for remote MCP servers is through the TrueFoundry registration manifest. Configuring TLS during the initial tfy apply ensures secure connections are enforced within the centralized guardrails.