---
title: "routebase"
description: "Design, mock, test, document and monitor your APIs from one living OpenAPI spec."
canonical: https://agentpluginsdirectory.com/plugins/routebase
last-updated: 2026-10-02
---

# routebase
Design, mock, test, document and monitor your APIs from one living OpenAPI spec.
- Slug: routebase
- Publisher: routebase-dev
- Repository: https://github.com/routebase-dev/routebase-mcp
- Manifest: plugin.json
- Version: 1.1.4
- License: MIT
- Category (editorial): integrations
- Skills: 0
- MCP servers: 1 (routebase)
- Stars: 0
- Repository created: 2026-08-14
- Repository last pushed: 2026-09-29
- Publisher type: Organization
- Listing: https://agentpluginsdirectory.com/plugins/routebase
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What routebase does, in the publisher's words

Connect your AI agent to your Routebase APIs. This is the connector for Routebase: an API lifecycle platform where documentation, mock servers, contract tests and monitoring are all derived from one OpenAPI spec. Agents work that same spec: designing endpoints and schemas, running contract and security test suites, managing mocks, publishing docs and reading monitors, under the same role-based permissions as the human team. Billing and organization access stay read-only.

There are two ways to connect. Pick the hosted endpoint unless your client only speaks stdio.

Streamable HTTP, with OAuth 2.1 and dynamic client registration: you sign in with your Routebase account, nothing to install and no key to rotate. Clients that prefer a static credential can send an X-API-Key header instead.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/routebase-dev/routebase-mcp/HEAD/README.md

## MCP servers

- routebase: transport: streamable-http; url: https://mcp.routebase.dev

Read from the plugin's own mcp.json. Environment variable names only, never values.