# All your tools. One MCP gateway. Source: https://corespeed.io/solutions/mcp-gateway CoreSpeed is a hosted MCP gateway: one endpoint, api.corespeed.io/mcp, that signs your agents in, lists the tools each identity may use, and passes each call to a connected app, a built-in tool or an HTTPS MCP server your organization registers. Claude Code, Codex, Cursor and other clients connect once, and every call is recorded. ## Set up an agent Give your agent this line: `set up https://corespeed.io/SKILL.md (read it raw, e.g. with curl)` It fetches the skill at https://corespeed.io/SKILL.md, adds the CoreSpeed MCP server, signs you in (or up), and keeps the skill for next time. One CoreSpeed endpoint. The tools your identity can use. Create an account: https://app.corespeed.io/sign-up ## Less setup. More getting to work Put connected apps, built-in tools, and your own remote MCP servers behind one endpoint. Each agent finds the tools your identity can use. You ask your agent: "Find the customer in our internal tools, then pull up their latest Slack conversation." It calls CoreSpeed: - `org__ops__find_customer`: ok, 268 ms - `slack__search_messages`: ok, 388 ms It reads from: Your remote MCP, Slack. ### A tool request, end to end: One way in. **Your MCP client** - Claude Code, Codex, Cursor, or another client **CoreSpeed · api.corespeed.io/mcp** - Signs you in - Lists the tools you can use - Records each call **Behind the gateway** - Connected apps - Your remote MCP servers - Built-in tools _Illustrative architecture · Your tools follow your sign-in, enabled capabilities, and connected accounts._ Read the MCP docs: https://corespeed.io/docs/mcp ## One connection. More possibilities What sits behind the one endpoint. The examples are illustrative. ### Connect your work apps Your connected apps · Available through CoreSpeed - GitHub: Issues, pull requests, and code (Connected) - Slack: Conversations and channels (Connected) - Notion: Pages and project knowledge (Connected) - Private or shared, per connection ### Bring your own MCP Internal tools · Your organization’s remote MCP - Server: ops.example.com/mcp - Tools: find_customer · get_order · update_ticket - Your server. Your tools. Same gateway. ### Use your favorite agents One CoreSpeed identity · Across compatible clients - Claude Code: Your connected tools - Codex: Your connected tools - Cursor: Your connected tools - Each agent signs in once ## Add CoreSpeed. Keep your agents The same endpoint works across compatible MCP clients. 1. **Set up CoreSpeed**: Give your agent the setup line. It adds CoreSpeed and signs you in. 2. **Bring your tools**: Connect an app, or register an HTTPS MCP server you already run. 3. **Start a real task**: Your agent finds and calls the tools available to you. Setup guides: Claude Code https://corespeed.io/docs/mcp#claude-code · Codex https://corespeed.io/docs/mcp#codex · Cursor https://corespeed.io/docs/mcp#cursor ## Questions ### Is this an MCP proxy? It is a hosted gateway. CoreSpeed signs your agents in, lists each identity's tools, and passes each call on; you run no local proxy. ### Is this MCP server hosting? No. CoreSpeed is the gateway your agents connect to. A server you register stays hosted and run by you. ### Can I bring my own remote MCP server? Yes. Register an HTTPS MCP server with OAuth, an organization bearer token, or no authentication. Its tools stay inside your organization. Remote MCP servers: https://corespeed.io/docs/connectors/remote-mcp ### Do I sign in separately in each agent? Yes, once per agent. Agents with the same identity in the same organization use the same connections. ### Will every tool in the catalog appear? No. Your tool list follows your connected accounts and enabled capabilities. A connection may need authorizing again before its calls work. ## Related pages - [Apify for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/apify): Find an Apify Actor, run it, and read its dataset from the agent you already use, on your own Apify account. - [Clink for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/clink): Shop and pay from a Clink agent wallet. Your agent prepares the checkout; paying is a separate call a person can approve. - [Connectors](https://corespeed.io/docs/connectors): Connect the apps your organization already uses and let every agent act through them without holding the provider credential. - [Datadog for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/datadog): Bring Datadog monitors, logs, traces and incidents into your agent. Turn an alert into a timeline and a likely cause. - [Daytona for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/daytona): Create Daytona sandboxes, run commands and read their files from your agent, with your own Daytona API key. - [Exa for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/exa): Search the web with Exa, read the pages that matter, and get cited answers inside the agent you already use. - [Firecrawl for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/firecrawl): Turn web pages, whole sites and PDFs into clean Markdown your agent can read, with your own Firecrawl key. - [Google Cloud for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/gcp): Debug Cloud Run from its logs, find idle spend, and read billing inside your agent, with your own Google account. - [GitHub for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/github): Turn GitHub issues and pull requests into a clear project update inside your agent, without the tab tour. - [GitLab for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/gitlab): Bring GitLab merge requests, issues and pipelines into your agent. See what needs review and which pipelines failed. - [What is an MCP gateway? One server for every tool](https://corespeed.io/glossary/mcp-gateway): An MCP gateway puts many tools and app accounts behind one remote MCP server and one sign-in. What it does, and what CoreSpeed's gateway holds for you. - [Hugging Face for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/hugging-face): Search Hugging Face models, datasets, Spaces and papers from your agent, and read a repo's files, commits and discussions. - [App integrations for Claude Code, Codex, and Cursor](https://corespeed.io/integrations): Connect Gmail, Slack, Notion, GitHub, and more to Claude Code, Codex, Cursor, and other MCP clients. Manage private and shared connections. - [Tavily for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/tavily): Search the web, extract clean page text, and run research jobs with Tavily, inside the agent you already use. - [Shared agent tools and controls for teams](https://corespeed.io/solutions/teams): Manage shared connections, approval policies, and tool usage for teams working across Claude Code, Codex, and other MCP clients. - [Tools](https://corespeed.io/tools): Models, the live web and nine social platforms, on one balance. No account for any of them. - [Webflow for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/webflow): Let your agent read Webflow sites, pages and CMS items, and draft updates. Publishing is a separate call approvals can hold. - [Zeplin for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/zeplin): Give your coding agent the Zeplin spec: screens, components, colors, text styles and spacing tokens, read with your own Zeplin account. ## Sources - MCP server: https://corespeed.io/docs/mcp - Remote MCP: https://corespeed.io/docs/connectors/remote-mcp Reviewed 2026-11-07. ## Links - Product overview: https://corespeed.io/ (Markdown: https://corespeed.io/index.md) - Documentation: https://corespeed.io/docs - Pricing: https://corespeed.io/pricing (Markdown: https://corespeed.io/pricing.md)