Connect a tool once. Use it from every client.
A hosted front door for your MCP servers: clients sign in over OAuth, the upstream credentials never leave the server, and the team shares one definition.
Speaks to
Three steps, and none of them is emailing a key around
Add the server once
Create a config in the dashboard and give it the upstream MCP server plus whatever credentials it needs. Those credentials stay server-side.
Copy the connect URL
Each config gets its own connect URL — personal, or owned by an organization so the whole team shares one definition.
Paste it into the client
The client registers itself over OAuth and signs in as you. No API key is typed into a config file that later ends up in a screenshot.
Prefer the terminal? The same configs are reachable from the CLI — see the CLI guide.
What the gateway is actually for
OAuth, not pasted keys
Clients register dynamically and authorise against the gateway. The upstream secret is held once, server-side, instead of being copied into every laptop that needs it.
One config for the team
A config can belong to an organization. Everyone reaches the same server through their own identity, and access follows the org rather than a shared file.
Revocable in one place
Access is granted per config and per identity, so removing someone does not mean rotating a key that eight other people are also using.
Every client, one definition
The same connect URL works from an editor, a desktop agent, or a terminal. Adding a second client is a paste, not another integration.
A record of what ran
Calls arrive through the gateway with an identity attached, so usage is attributable instead of anonymous traffic from a shared token.
Bring your own servers
The gateway does not restrict you to a catalogue. Point it at the MCP servers your team already runs.
Questions
What is MCP?+
The Model Context Protocol is a standard way for an AI client to discover and call tools. A server advertises its tools; a client calls them. The gateway sits between the two so the connection is authenticated and shared rather than configured per machine.
Which clients work with it?+
Any client that speaks MCP over HTTP with OAuth. That covers the common editors and desktop agents, and the RenderHour Mac app, which speaks MCP in both directions.
Do I still need API keys?+
The upstream server may need its own credentials, and you give those to the gateway once. What changes is that they stop being copied into every client config on every machine.
Can I render video over MCP?+
Yes — media generation ships as its own MCP server with six tools (images, video jobs, speech, cost preview), billed to your account. See renderhour.com/mcp/media for connector snippets. The gateway on this page is the complementary product: it fronts YOUR upstream MCP servers.
Is it separate from the media catalogue?+
Yes. They are two products that happen to share an account. The gateway is not metered against render credits.
Stop pasting keys into config files
Add a server once, hand the URL to whoever needs it, and take it back when they move on.