MCP.so
Sign In

RoutebaseVerifiedFeatured

@Routebase

About Routebase

Routebase keeps your API's design, docs, contract tests, mocks and monitoring in one living OpenAPI spec so they can't drift apart. Agents work on that same source of truth, under your team's permissions.

Connection details

https://mcp.routebase.dev

Setup

claude mcp add routebase --transport http https://mcp.routebase.dev

Tools

No tools detected

Fetch the live tool list directly from this server's endpoint using the button above.

Overview

What is Routebase

Routebase is the single source of truth for your APIs. Design your OpenAPI spec once in a visual editor, and your documentation portal, mock servers, contract tests, and monitoring all derive from it. Change the spec, publish — and Routebase catches what drifted before your consumers do, with field-level diffs against your live API. Work on specs the way you work on code: branch, review, merge, with breaking-change detection. And because every workspace ships a built-in MCP server, your AI agents read and act on the same source of truth, under your team's permissions.

What agents can do

Agents design endpoints and schemas, run contract and security test suites, manage mock servers, publish documentation, and read monitoring results — all under the same role-based permissions as the human team. Billing and organization access stay read-only.

The server exposes 400+ tools across 31 toolsets, so you can enable only the surface a given agent needs.

Features

  • Visual OpenAPI design editor — endpoints, schemas, reusable components, no YAML
  • Spec branches with merge requests, review, and breaking-change detection
  • Auto-generated documentation portal on a custom domain — never drifts from the spec
  • Mock servers generated straight from the spec, with custom rules and proxy mode
  • Contract testing: assert live responses against the spec across environments
  • Scheduled drift monitoring with field-level diffs and alerts
  • Security scanning built into the test workflow
  • API governance rules and style-guide enforcement
  • Built-in MCP server — 400+ lifecycle tools, every API agent-ready
  • OpenAPI import & export, Postman collection export

Getting started

Hosted endpoint (Streamable HTTP), EU by default:

https://mcp.routebase.dev

US region:

https://mcp.routebase.dev/?region=us

Authentication is OAuth 2.1 with Dynamic Client Registration (RFC 7591), so most MCP clients complete the connection in the browser without manual setup. An X-API-Key header works as an alternative.

For a local stdio connector, the npm package is MIT-licensed:

npx routebase-mcp init

Documentation: https://docs.routebase.dev → MCP Quickstart

Frequently asked questions

What is the Routebase remote MCP server?

The Routebase remote MCP server is a hosted Model Context Protocol endpoint at https://mcp.routebase.dev, so AI assistants can connect to it without installing or running anything locally.

How do I connect to the Routebase MCP server?

Add the endpoint https://mcp.routebase.dev to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

Does the Routebase MCP server require authentication?

Yes. Routebase uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.

Which transport does the Routebase MCP server use?

Routebase exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments