Product
Build your MCP registry
Speakeasy Team
June 16, 2026 - 3 min read
Speakeasy has been the fastest way to put MCP servers in front of your team. You could quickly generate a server from the API you already have, host it, and publish it to a registry your whole company connects to.
But not every MCP server you want to govern is one you’d build on Speakeasy. You may already run some on your own infra. There may be remotely hosted servers from SaaS vendors. Now you can point Speakeasy at any MCP server, and it joins your MCP registry: same access controls, same audit trail, same view of the traffic.
Register a server by URL
Adding a remote MCP server is as simple as copy & pasting its URL. Speakeasy probes the endpoint with an MCP initialize request and reports back whether it’s reachable and speaking the protocol correctly.
Give it a name, confirm it verifies, and the server becomes a source in your registry like any other. From there it shows up in the same places your hosted and generated servers do, and the governance and security policies you’ve already defined around those servers start applying automatically.
One registry, one set of controls
The point of a registry is that governance lives in one place. A remote MCP server doesn’t get a parallel set of rules. It inherits the model you already use. The network-level access controls that decide who can connect to which servers cover it. The audit trail that records tool calls records its calls too. Security gets one view of what agents are reaching for, whether the server runs on Speakeasy or somewhere you stood up yourself.
A server you can’t observe is a server you can’t trust. Each remote MCP source carries an activity view, so you can see the traffic flowing through it the same way you’d watch any other source. The calls, the patterns, the volume are visible in the same dashboard as the rest of your registry, not scattered across tools that don’t talk to each other. The same view that surfaces shadow MCP usage now covers the servers you’ve brought in by URL.
Get started
Remote MCP servers show up under Add Source in your Speakeasy dashboard, alongside registry servers and OpenAPI sources. Paste the URL, verify the connection, and the server joins your registry — governed, audited, and observable next to everything else you run.
Already running MCP servers you’d like under one roof? Book time with our team and we’ll help you bring them in.