Routebase

Your workspace ships a Model Context Protocol server. Describe the API you want — your agent designs the spec, writes the tests, and runs them, under your team's permissions.

14-day Pro trial — no credit card required.

Describe the API. Get the spec — and the tests.

Two shipped prompts carry the whole job: design_api builds the contract, generate_tests turns it into a suite that runs.

- design_api walks it call by call: create_spec, create_schema, create_endpoint, add_response, validate_spec
- Your organization's style guide is loaded as context first, so the draft arrives already linted
- generate_tests covers happy path, 400, 401, 403, 404, response schema, latency, and edge cases
- run_test_suite executes the suite and reports which assertion failed, on which case
- The agent works on a draft version — nothing reaches consumers until someone publishes

What comes back is your workspace, not a transcript

No wall of YAML to paste. Every call creates a real object in Routebase — one your team can open, diff, and review.

- Endpoints, schemas, and folders land in the visual editor
- Agent work can run on a spec branch and arrive as a merge request
- validate_spec has a dry-run mode: same errors and counts, nothing written
- publish_version is the one step that freezes an immutable OpenAPI snapshot

Design is where it starts. Mocks, monitors, security triage, and docs are the same connection — 400+ tools across 31 toolsets.

- generate_rules_from_spec turns the new endpoints into a running mock
- generate_monitors_from_spec puts the same contract under monitoring
- 87 testing tools — suites, scenarios, runs, results, schedules
- Monitoring, Security, and Mock Server are fully agent-reachable, enforced by a CI coverage ratchet

Context and whole workflows, prepackaged

Beyond tools: 12 read-only resources hand agents context without spending a call, and 13 prompts package multi-step work into one invocation.

- Resources: spec as OpenAPI YAML, changelog, validation report, test summary, style guide
- Design prompts: design_api, review_spec, fix_violations, generate_schema
- Operations prompts: analyze_test_failures, triage_security_findings, triage_incidents, run_deprecation
- Structured logs and usage metrics per session

400+ tool definitions would fill a context window before the agent does anything. A default session sees 48.

- Five core toolsets: context, navigation, projects, specs, endpoints
- About 6k tokens of tool definitions instead of 55k — an 88% cut
- enable_toolset adds what the task needs, mid-session
- A scoped API key or an OAuth sign-in skips the staging entirely
- Hidden is never disabled — a tool stays callable by name

An agent is a user, not a backdoor. Every call runs through the same RBAC your team already has — once at discovery, again at execution.

- Agents only see tools their permissions allow
- OAuth 2.1 sign-in or a scoped API key
- Billing and org access stay read-only: an agent explains a limit, it never grants a role or spends money
- 200 requests per minute per user, separate from the REST API
- EU or US region — the same choice as the app

Connect in a minute — or with nothing installed

Claude adds the server as a custom connector and signs you in. Every other client is one command.

- Remote connector at mcp.routebase.dev for Claude web, desktop, and mobile — OAuth, no API key, nothing on disk
- Claude Code, Cursor, and VS Code talk to the hosted endpoint over streamable HTTP
- npx routebase-mcp init writes the config for your IDE
- stdio bridge with self-contained binaries for macOS, Windows, and Linux

Practicing what we preach:this site ships llms.txt

Build and deploy full-stack Next.js apps with 98 tools for React, AWS, and MongoDB