MCP Gateway
roadbeat in your AI assistant
The MCP Gateway connects AI assistants such as Claude, ChatGPT and Cursor to roadbeat through the open Model Context Protocol (MCP). Your assistant can search roadbeat content, work with your goals and draft in Studio — only with your permission, and every call is logged.
What your assistant can do
The gateway offers tools, resources and prompts to the AI app you use. What the assistant may do depends on your account and on what you allow when you connect it.
Discover and research
Search the Discovery Nodes by text, content type, place and time, open teasers, and research a topic with citations — public content, no account needed for reading.
Your goals and bookmarks
With a personal roadbeat account: list and update your Compass goals, follow publishers, keep bookmarks and get a weekly review of matching content.
Draft and publish in Studio
With a Studio account: create schema-checked drafts, translate them, upload images with alt text and publish — publishing always asks you to confirm.
Your data, your rights
Export what the gateway stores about you, revoke the consents you gave to AI apps, or disconnect an app at any time — access ends immediately.
Connect in a minute
Add roadbeat to your assistant with the connector URL below and sign in with your roadbeat account. No client ID or secret is needed.
Connector URL
https://mcp.roadbeat.net/mcpOrganization accounts sign in at studio.roadbeat.net, personal accounts at app.roadbeat.net. During the pre-launch phase the sign-in pages also ask for the pre-launch password.
ChatGPT
Enable developer mode and create a connector with the URL and OAuth sign-in.
Step-by-step guideCursor
Add the URL to mcp.json — handy for building integrations with roadbeat content types.
Step-by-step guideClaude Code
claude mcp add --transport http roadbeat https://mcp.roadbeat.net/mcpBuilt for control and privacy
The gateway is the single place where AI assistants meet roadbeat — so that is where roadbeat enforces its European values.
Your account, standard sign-in
OAuth 2.1 with PKCE at roadbeat. Tokens are short-lived, bound to the gateway and never passed on to other services.
Consent before personal data
Reading your goals, changing data or sharing personal data needs your explicit consent per app — once, for a day, 30 days or until you revoke it.
Every call is logged
An audit log records which app called which tool and when — arguments only as hashes. Logs are deleted after a year.
Disconnect any time
Remove an app under Connected AI apps in your account: its access ends at once.
No AI inside the gateway
The gateway never calls a language model and sends no data to AI vendors. The assistant you choose does the thinking.
Hosted in Europe
roadbeat runs the gateway on its own servers in Germany, under the GDPR. No tracking, no ads, no profiling.
For publishers and newsrooms
Editors can let an assistant research a topic, draft a schema-checked article, localize it and send it for publishing — Studio roles and permissions still apply, and an assistant never gets admin rights.
Open source and self-hostable
The gateway is open source (AGPL-3.0). Organizations can run their own instance next to their Studio, with their own sign-in and audit log.
License: AGPL-3.0
Documentation
Setup guides for every assistant, the full tool reference, permissions and consent, self-hosting and the API reference.
Open the MCP Gateway docs