Skip to content
mcp/harbor

Toolstile changelog

io.github.toolstile/toolstile

1 change recorded. MCP Harbor re-reads this listing from the official registry every six hours and asks the live server what it exposes, and keeps what changed between one look and the next.

  • llms.txt 1 field changed
    file
    absent published

    https://toolstile.com/llms.txt 

    + # Toolstile+ > Managed MCP gateway: connect remote MCP servers once, then choose which tools each AI app (Claude Code, Codex, Cursor, Claude Desktop) can use. Server credentials stay in Toolstile instead of each app's config.+ Every page below also returns its Markdown source when requested with `Accept: text/markdown`. Agents authorize through the browser OAuth flow in https://mcp.toolstile.com/auth.md; the MCP endpoint is https://mcp.toolstile.com/mcp and its discovery document is https://mcp.toolstile.com/.well-known/ai-catalog.json.+ ## Product+ - [Home](https://www.toolstile.com/): Connect MCP servers once, choose which tools Claude Code, Codex, Cursor and Claude Desktop can use, and share accounts without passing tokens around.+ - [Pricing](https://www.toolstile.com/pricing): Compare Toolstile's Free, Starter, Team and Scale plans. Paid plans start at $29 per workspace with a seven-day trial. No per-seat fees or paid overages.+ - [Security](https://www.toolstile.com/security): How Toolstile checks agent access, stores MCP credentials, handles gateway traffic and limits debug capture, with retention and reporting details.+ - [FAQ](https://www.toolstile.com/faq): Answers about Toolstile's managed MCP gateway: server connections, workspace access, shared accounts, activity logs and monthly operation limits.+ - [What is an MCP gateway?](https://www.toolstile.com/mcp-gateway): An MCP gateway sits between AI apps and MCP servers. Learn how auth and per-agent tool rules work, how it differs from a proxy, and when to skip one.+ - [MCP config audit](https://www.toolstile.com/audit): Free MIT MCP config audit for plaintext tokens, unpinned packages and auto-approved tools. Scans run locally; --fix checks versions on npm or PyPI.+ - [Engineering](https://www.toolstile.com/use-cases/engineering): Bring issue and repository context into Codex or Claude Code. Choose each app's MCP tools, keep server tokens out of configs and trace requests.+ - [Marketing](https://www.toolstile.com/use-cases/marketing): Build briefs and reports from campaign and CRM context in your AI apps. Share approved MCP accounts and choose which tools each app may use.+ - [Support](https://www.toolstile.com/use-cases/support): Give your AI apps customer history and help articles through MCP. Choose their lookup tools, keep server credentials centralized and review activity.+ - [Privacy policy](https://www.toolstile.com/privacy): How Toolstile handles account information, connected services and gateway traffic.+ - [Terms of service](https://www.toolstile.com/terms): The terms for using Toolstile’s managed MCP gateway, accounts and subscriptions.+ - [Integrations](https://www.toolstile.com/integrations): Connect remote MCP servers from the current catalog once, then choose which tools Claude Code, Codex and Cursor can use.+ ## Documentation+ - [Documentation](https://www.toolstile.com/docs): Set up Toolstile, connect a remote MCP server, authorize an agent, and choose what it can access. Start with the getting-started guide.+ - [Getting started](https://www.toolstile.com/docs/getting-started): Connect a remote MCP server to Toolstile, sign in from your agent app, set workspace access, and verify the permitted tools without running one.+ - [Client setup](https://www.toolstile.com/docs/clients): Set up Toolstile in Claude Code, Codex, Cursor or Claude Desktop, authorize a workspace, then grant the agent access to its MCP connections.+ - [Claude Code](https://www.toolstile.com/docs/clients/claude-code): Add MCP servers to Claude Code through one Toolstile URL: claude mcp add, scopes, /mcp sign-in, workspace access, permission rules and fixes.+ - [Codex](https://www.toolstile.com/docs/clients/codex): Connect Codex to MCP servers through Toolstile: codex mcp add and login, config.toml, workspace access, approval modes and troubleshooting.+ - [Cursor](https://www.toolstile.com/docs/clients/cursor): Connect Cursor to MCP servers through Toolstile with one mcp.json entry: sign-in, workspace access, approvals, logs and troubleshooting.+ - [Claude Desktop](https://www.toolstile.com/docs/clients/claude-desktop): Add a remote MCP server as a Claude custom connector in claude.ai or Claude Desktop: plan availability, the Toolstile URL, sign-in, tool permissions and fixes.+ - [Connections](https://www.toolstile.com/docs/connections): Add a public HTTPS MCP server to Toolstile. Learn where to find its URL, when to use OAuth or a bearer token, and how to verify agent access.+ - [Permissions](https://www.toolstile.com/docs/permissions): Set per-agent MCP permissions in Toolstile. Learn how direct grants, policies and blocks combine, when edits take effect and how to revoke access.+ - [Shared accounts](https://www.toolstile.com/docs/shared-accounts): Share MCP accounts with a team, approve contributions, set account preferences, and understand what happens when a contributor withdraws or leaves.+ - [Usage and billing](https://www.toolstile.com/docs/billing): Learn what counts as a Toolstile operation, when allowances reset, and how limits work. Read the rules for trials, plan changes, cancellations and refunds.+ - [Troubleshooting](https://www.toolstile.com/docs/troubleshooting): Diagnose MCP sign-in errors, missing tools, unavailable accounts, paused forwarding and debug capture problems in Toolstile.+ ## Guides+ - [Guides](https://www.toolstile.com/guides): Practical guides to MCP servers, tool allowlists and agent permissions in Claude Code, Codex and Cursor, from the team behind Toolstile.+ - [Best remote MCP servers](https://www.toolstile.com/guides/best-mcp-servers): 35 official remote MCP servers by team, live-checked in October 2026: what each is good for, how sign-in works and which tools to keep on approval.+ - [Best MCP servers for Claude Code](https://www.toolstile.com/guides/best-mcp-servers-for-claude-code): 11 remote MCP servers for coding in Claude Code, from GitHub and Sentry to Context7 and Supabase, with setup commands, sample prompts and permission tips.+ - [MCP allowlist](https://www.toolstile.com/guides/mcp-allowlist): Allowlist MCP servers and tools in Claude Code, Cursor, Codex and VS Code, see where client lists fall short, and enforce per-agent rules at a gateway.+ - [MCP security risks](https://www.toolstile.com/guides/mcp-security): MCP security risks explained: prompt injection, tool poisoning, rug pulls, token passthrough and SSRF, with real incidents and the controls for each.+ - [MCP authentication](https://www.toolstile.com/guides/mcp-authentication): How MCP server authentication works with OAuth 2.1: the 401 challenge, metadata discovery, CIMD, PKCE, token audiences, scopes and gateways.+ - [MCP elicitation](https://www.toolstile.com/guides/mcp-elicitation): How MCP elicitation works in the 2026-07-28 spec: form and URL modes, requestedSchema limits, accept, decline and cancel, security rules and client support.+ - [Remote MCP servers](https://www.toolstile.com/guides/remote-mcp-server): What a remote MCP server is, Streamable HTTP vs legacy SSE, OAuth sign-in, and how to add one in Claude Code, Codex, Cursor and Claude, with commands.+ - [Claude Code permissions](https://www.toolstile.com/guides/claude-code-permissions): How Claude Code permission modes, settings.json allow/ask/deny rules, --allowedTools and precedence apply to MCP tools, and how to pair them with gateway rules.+ - [Claude Code --dangerously-skip-permissions](https://www.toolstile.com/guides/claude-code-dangerously-skip-permissions): What Claude Code's --dangerously-skip-permissions flag skips, what still applies, how admins disable it, and how to keep MCP tools safe once prompts are gone.

    Showing the first 40 of each.

Toolstile MCP server