Context & Session — MCP Tools
Session context, organizations, projects and toolset management. This page documents the Context & Session group of the Routebase MCP server, with the scope and the parameters of each tool.
The group is part of the core set, so every session advertises it from the start.
enable_toolset
Enable one or more toolsets for this session so their tools appear in tools/list. Pass a comma-separated list of toolset slugs (see list_toolsets). Sends a tools/list_changed notification; clients that ignore it can still call hidden tools directly.
No special scope — available to any authenticated key.
| Parameter | Type | Required | Description |
|---|---|---|---|
names |
string | Yes | Comma-separated toolset slugs to enable, e.g. 'testing,mock-server' |
get_session_usage
Return usage metrics for the current MCP session: total tool calls, error count, aggregate duration and response size, per-tool call counts, and session timestamps. Metrics are in-memory and reset when the server restarts or the session goes idle. Use this for what this session has spent; for which toolsets exist at all use list_toolsets.
No special scope — available to any authenticated key.
No parameters.
list_organizations
List all organizations the authenticated user is a member of, including their role in each. Use this to find an organization id; to make one active use set_context.
No special scope — available to any authenticated key.
No parameters.
list_projects
List all projects in the active organization. Use this to browse projects or find a project id; for one project in full use get_project. Requires organization context (call set_context first).
Required scope: projects:read
| Parameter | Type | Required | Description |
|---|---|---|---|
skip |
integer | No (default 0) |
Number of projects to skip (for pagination, default 0) |
take |
integer | No (default 50) |
Number of projects to return (default 50, max 100) |
list_toolsets
List all toolsets (tool groups) with slug, tool count and whether they are visible in this session. Core toolsets are always visible; enable others with enable_toolset. Full-access API keys see every tool; scoped keys and OAuth sessions automatically see every tool their scopes or role allow. Hidden tools stay callable — enabling only affects what tools/list advertises.
No special scope — available to any authenticated key.
No parameters.
set_context
Set the active organization and optionally a project for this session. Must be called before using any module-specific tools. Pass the organization's public ID (GUID) and optionally a project's public ID. Two areas are deliberately incomplete: billing and organization/access are read-only (an agent must not grant rights or trigger cost), and gateway, service catalog and AI assist have no tools at all while they are not generally available. Most toolsets start hidden — call list_toolsets to see them and enable_toolset to add them.
No special scope — available to any authenticated key.
| Parameter | Type | Required | Description |
|---|---|---|---|
organizationId |
string | Yes | Public ID (GUID) of the organization to set as active context |
projectId |
string | No | Public ID (GUID) of the project to set as active context (optional) |