truefoundry-mcp-servers
Skill14 starsChanged 6 months agoMITView on GitHub
Manages TrueFoundry MCP Gateway server registry entries. Covers listing, creating, updating, tool selection, access control, and client attachment for remote, official remote, virtual, hosted STDIO, and OpenAPI-backed MCP servers. Delete operations are manual dashboard-only.
In this repository8 other files it gives its agents.
The file
Show its rules and text
We split this skill into the rules it gives an agent
40 rules. About 0 are common, 26 are distinctive, and 14 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈26
Distinctive · estimate
This author's own choices. Worth a look.
14
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Use this skill when the user wants to:
- Distinctive: line 19
Create virtual MCP servers from tools across multiple source servers.
- Very specific: line 20
Create hosted STDIO MCP servers from mcpServers JSON.
- Distinctive: line 21
Import OpenAPI specs as MCP servers.
- Distinctive: line 23
Update auth, access, metadata, endpoint/spec, or selected tools.
- Distinctive: line 24
Add MCP servers to clients such as Cursor, VS Code, Claude Code, Python, TypeScript, Windsurf, or Codex.
- Distinctive: line 26
Do not delete MCP servers or remove collaborators from the agent.
- Very specific: line 41
Treat the live dashboard Apply using YAML preview as the source of truth when it differs from examples.
- Very specific: line 45
Verify tfy login is complete.
- Very specific: line 46
Verify the target tenant from TFY_BASE_URL/TFY_HOST.
- Very specific: line 48
Use mcp-server-manager as the default role unless the user requests another role.
- Very specific: line 49
Use collaborator subjects as user:<email>, team:<slug>, serviceaccount:<name>, or virtualaccount:<name>.
- Very specific: line 50
Use tfy-secret://... references for shared credentials whenever possible.
- Distinctive: line 51
Never print, paste, or reveal real credentials unless the user explicitly asks and accepts exposure.
- Distinctive: line 52
Do not call DELETE APIs, destructive CLI commands, or collaborator-removal flows.
- Very specific: line 54
Before every final tfy apply, show:
- Distinctive: line 65
Prefer the dashboard when the user is working in the UI.
- Distinctive: line 81
Use this for an existing HTTP MCP endpoint.
- Distinctive: line 90
if auth is enabled: API key/header, OAuth2, or token passthrough
- Very specific: line 94
No auth: omit auth_data.
- Distinctive: line 99
Use references/mcp-yaml-variations.md for concrete YAML shapes.
- Distinctive: line 103
Use this for catalog servers such as GitHub, Linear, Sentry, Atlassian, Figma, Slack, Notion, Stripe, HuggingFace, or similar.
- Distinctive: line 117
Use this to expose selected tools from multiple existing MCP servers through one virtual MCP server.
- Distinctive: line 133
Ask which tools to expose from each source.
- Very specific: line 134
Use servers[].enabled_tools for selected subsets.
- Very specific: line 136
Add collaborators with mcp-server-manager unless requested otherwise.
- Distinctive: line 140
Use references/mcp-yaml-variations.md for virtual server YAML examples.
- Distinctive: line 144
Use this when the user has a local-style MCP config and wants the gateway to host/expose it.
- Distinctive: line 150
Ask for the STDIO JSON or file.
- Distinctive: line 152
Use the gateway import flow or YAML preview as the source of truth for the manifest generated after import.
- Distinctive: line 155
Use references/mcp-yaml-variations.md for the input shape.
- Distinctive: line 159
Use this to expose OpenAPI operations as MCP tools.
- Very specific: line 186
Do not invent field names for normal-server tool filtering.
- Distinctive: line 197
Use secret references for shared credentials.
- Distinctive: line 201
Use references/mcp-yaml-variations.md for auth examples.
- Distinctive: line 213
When changing access, show the before/after collaborator list and preserve unrelated server config.
- Very specific: line 219
Use the dashboard Add to Client modal or the generated snippet.
- Distinctive: line 223
Always run the dry-run first:
- Distinctive: line 229
Run the final apply only after explicit user confirmation:
- Very specific: line 237
Do not call DELETE APIs or tfy delete flows.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<objective>MCP Servers
Manage MCP servers in TrueFoundry AI Gateway.
Use this skill when the user wants to:
- List MCP servers attached to a gateway.
- Connect remote or official remote MCP servers.
- Create virtual MCP servers from tools across multiple source servers.
- Create hosted STDIO MCP servers from
mcpServersJSON. - Import OpenAPI specs as MCP servers.
- Enable or disable tools.
- Update auth, access, metadata, endpoint/spec, or selected tools.
- Add MCP servers to clients such as Cursor, VS Code, Claude Code, Python, TypeScript, Windsurf, or Codex.
Do not delete MCP servers or remove collaborators from the agent. Route those requests to the TrueFoundry dashboard.
</objective><instructions>Reference Map
Load only the reference needed for the user's task:
| Task | Reference |
| Browser/UI operation, click paths, form fields, add-to-client modal | references/mcp-gateway-ui-flows.md |
| YAML examples for auth modes, server types, virtual tool selection, OpenAPI, hosted STDIO | references/mcp-yaml-variations.md |
Treat the live dashboard Apply using YAML preview as the source of truth when it differs from examples.
Safety Rules
- Verify
tfy loginis complete. If not, usetruefoundry-onboard. - Verify the target tenant from
TFY_BASE_URL/TFY_HOST. - Confirm the workspace or registry scope with the user before applying changes.
- Use
mcp-server-manageras the default role unless the user requests another role. - Use collaborator subjects as
user:<email>,team:<slug>,serviceaccount:<name>, orvirtualaccount:<name>. - Use
tfy-secret://...references for shared credentials whenever possible. - Never print, paste, or reveal real credentials unless the user explicitly asks and accepts exposure.
- Do not call DELETE APIs, destructive CLI commands, or collaborator-removal flows.
Before every final tfy apply, show:
- Plain-English summary of the change.
- Target tenant and workspace/scope.
- Full YAML or diff.
- Exact command to be run.
Then ask for explicit confirmation. Run only dry-runs before confirmation.
List MCP Servers
Prefer the dashboard when the user is working in the UI. For API fallback:
TFY_API_SH=~/.claude/skills/truefoundry-mcp-servers/scripts/tfy-api.sh
$TFY_API_SH GET /api/svc/v1/mcp-serversPresent servers as:
MCP Servers
| Name | Type | Auth | ID | URL / Source |Connect Remote MCP Server
Use this for an existing HTTP MCP endpoint.
Collect:
namedescriptionurl- collaborators and roles
- auth enabled or disabled
- if auth is enabled: API key/header, OAuth2, or token passthrough
Auth rules:
- No auth: omit
auth_data. - API key/header auth: support shared credentials and individual credentials; require at least one header.
- OAuth2: support authorization code and client credentials; include optional scopes, PKCE/code challenge methods, Dynamic Client Registration URL, and additional token params only when supplied or shown by the UI preview.
- Token passthrough: use the caller's existing TrueFoundry token; no extra fields are needed.
Use references/mcp-yaml-variations.md for concrete YAML shapes.
Connect Official Remote MCP Server
Use this for catalog servers such as GitHub, Linear, Sentry, Atlassian, Figma, Slack, Notion, Stripe, HuggingFace, or similar.
Flow:
- Identify the official server in the gateway catalog.
- Confirm the catalog auth mode.
- For OAuth2, tell the user they may need to complete a browser authentication flow after creation.
- For header auth, collect header names and use secret references or per-user placeholders.
- Confirm collaborators.
- Generate YAML from the UI preview or the YAML reference.
- Dry-run, show diff, then apply only after confirmation.
Create Virtual MCP Server
Use this to expose selected tools from multiple existing MCP servers through one virtual MCP server.
Collect:
- virtual MCP
name description- source MCP servers
- tools to expose from each source server
- collaborators and roles
- optional source-server auth header override if the gateway requires it
Flow:
- List registered MCP servers.
- Select source MCP servers.
- Enumerate available tools for each source server.
- Ask which tools to expose from each source.
- Use
servers[].enabled_toolsfor selected subsets. - Omit
enabled_toolsfor a source only when exposing every tool from that source. - Add collaborators with
mcp-server-managerunless requested otherwise. - Show virtual server name, source servers, selected tools, and access.
- Show YAML, dry-run, and apply only after confirmation.
Use references/mcp-yaml-variations.md for virtual server YAML examples.
Create Hosted STDIO MCP Server
Use this when the user has a local-style MCP config and wants the gateway to host/expose it.
Collect JSON containing an mcpServers object with server command, args, and optional env.
Flow:
- Ask for the STDIO JSON or file.
- Replace raw environment secrets with secret references where supported, or tell the user which values must be moved to secrets.
- Use the gateway import flow or YAML preview as the source of truth for the manifest generated after import.
- Show summary, YAML/diff, dry-run, and confirmation-gated apply.
Use references/mcp-yaml-variations.md for the input shape.
Import From OpenAPI Spec
Use this to expose OpenAPI operations as MCP tools.
Collect:
namedescription- OpenAPI spec source: trusted remote URL or pasted inline spec
- selected tools/operations
- collaborators
- optional auth using the same modes as remote MCP servers
For remote specs, confirm the URL is trusted before use. Prefer pasted/inline specs for sensitive private APIs.
Enable Or Disable Tools
Tool filtering is supported for normal remote/OpenAPI servers and virtual MCP servers.
For normal remote/OpenAPI servers:
- Fetch the current MCP server config by ID.
- Inspect the API response or UI YAML preview for the existing tool-selection shape.
- Fetch or confirm available tool names.
- Modify only the requested tool-selection fields.
- Preserve name, URL/spec, auth, collaborators, TLS, tags, and unrelated settings.
- Show the before/after tool list or YAML diff.
- Dry-run and apply only after confirmation.
Do not invent field names for normal-server tool filtering. If the API response does not expose the shape, use the dashboard edit screen or ask the user for the Apply using YAML output.
For virtual servers, use servers[].enabled_tools; omit it only when exposing every tool from that source.
Update Auth
Use update-by-manifest:
- Fetch the current MCP server config.
- Preserve name, URL/spec, selected tools, collaborators, TLS, tags, and unrelated settings.
- Replace only the requested
auth_datablock. - Use secret references for shared credentials.
- Show old auth mode and new auth mode.
- Show YAML/diff, dry-run, and apply only after confirmation.
Use references/mcp-yaml-variations.md for auth examples.
Access Control
Adding collaborators is allowed with confirmation. Removing collaborators is dashboard-only.
To list access:
$TFY_API_SH GET '/api/svc/v1/collaborators?resourceType=mcp-server&resourceId=RESOURCE_ID'When changing access, show the before/after collaborator list and preserve unrelated server config.
Add To Client
The gateway UI can generate setup snippets for Cursor, VS Code, Claude Code, Python, TypeScript, Windsurf, and Codex.
Use the dashboard Add to Client modal or the generated snippet. Do not click, reveal, paste, or print API keys unless the user explicitly asks and understands the exposure.
Apply
Always run the dry-run first:
tfy apply -f mcp-server.yaml --dry-run --show-diffRun the final apply only after explicit user confirmation:
tfy apply -f mcp-server.yamlDelete
Do not call DELETE APIs or tfy delete flows. Tell the user:
To delete this MCP server, open the TrueFoundry dashboard, go to AI Gateway -> MCP Servers, select the server, and delete it from the UI.</instructions><success_criteria>
- The user can list MCP servers.
- The user can create remote, official remote, virtual, OpenAPI, and hosted STDIO-backed MCP servers.
- Auth-disabled, API key, OAuth2, and token-passthrough configurations match the live gateway YAML shape.
- Tool enable/disable updates preserve unrelated server config.
- Auth and access changes use reviewed full-manifest updates.
- Client attachment guidance covers Cursor, VS Code, Claude Code, Python, TypeScript, Windsurf, and Codex.
- Shared credentials use
tfy-secret://...references or explicit placeholders. - Final
tfy applyis gated by summary, YAML/diff, exact command, and explicit confirmation. - Deletes and collaborator removals are dashboard-only.
</success_criteria>
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

