MCP Reference

Governance — MCP Tools

6 tools in the Governance group of the Routebase MCP server.

get_breaking_changes

Identify and classify breaking changes between two specification versions. Returns changes classified as Breaking, NonBreaking, or Deprecated with migration hints. Requires project context.

Required scope: specs:read

Parameter Type Required Description
specId string Yes Public ID (GUID) of the API specification
sourceVersionId string Yes Public ID (GUID) of the source (older) version
targetVersionId string Yes Public ID (GUID) of the target (newer) version

get_header_policies

Get resolved headers for an endpoint, showing the full cascade of header policies (organization → project → specification). Requires project context.

Required scope: specs:read

Parameter Type Required Description
specId string Yes Public ID (GUID) of the API specification
endpointId string Yes Public ID (GUID) of the endpoint

get_style_guide_rules

Get all available style guide rules with their effective severity at the organization level. Includes built-in rules and custom rules. Use list_project_style_guide_rules for how they resolve inside one project. Requires organization context.

Required scope: org:manage-governance

No parameters.

get_versioning_strategy

Get the versioning strategy configured for an API specification, including version aliases. Requires project context.

Required scope: specs:read

Parameter Type Required Description
specId string Yes Public ID (GUID) of the API specification

lint_spec

Validate an API specification against style guide rules. Returns violations grouped by severity (error, warning, info) with rule details and affected paths. Requires project context.

Required scope: specs:read

Parameter Type Required Description
specId string Yes Public ID (GUID) of the API specification to lint

set_versioning_strategy

Set or update the versioning strategy for an API specification. Defines how API versions are transmitted (URL path, header, query param, content negotiation). Requires project context.

Required scope: specs:write

Parameter Type Required Description
specId string Yes Public ID (GUID) of the API specification
strategyType string Yes Strategy type: 'urlPath', 'header', 'queryParam', or 'contentNegotiation'
parameterName string Yes Parameter name for the version (e.g., 'v' for URL path, 'Api-Version' for header, 'api-version' for query)
urlPattern string No URL pattern for urlPath strategy (e.g., '/v{major}'). Only required for urlPath.
defaultBehavior string No (default "latest") Default behavior when no version is specified: 'latest' (default), 'specific', or 'requireExplicit'
strictMode boolean No (default false) If true, reject requests without explicit version identifier (default false)