AI Switch MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| continue_taskA | Use this when a user says continue/resume a feature. Auto-selects the best session and returns a ready continuation prompt. |
| start_sessionB | Create a new cross-assistant coding session for resumable handoff context. |
| append_progressC | Append a progress update from the active assistant to an existing session. |
| update_sessionC | Patch session metadata, task state, notes, status, and optional progress details. |
| get_sessionA | Fetch one session by ID with optional markdown handoff and resume prompt. |
| get_latest_sessionA | Get the most recently updated session, optionally scoped by project path. |
| list_sessionsA | List recent sessions with filters for project path and status. |
| complete_sessionC | Mark a session completed and optionally append final summary/notes. |
| delete_sessionA | Delete a saved session by ID. Requires confirm=true to prevent accidental deletion. |
| generate_handoffC | Generate a portable markdown handoff and resume prompt from a session. |
| store_infoA | Show the active storage file path so different MCP clients share the same history. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools have distinct purposes, but continue_task and generate_handoff both produce handoff/resume prompts, and append_progress overlaps with update_session. However, descriptions clarify the use cases, so ambiguity is minimal.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., start_session, get_latest_session, delete_session). The naming is highly predictable and uniform.
11 tools is well within the ideal 3-15 range. Each tool covers a distinct aspect of session management—create, read, update, delete, resume, and handoff—without unnecessary bloat.
The tool set provides full lifecycle coverage for cross-assistant coding sessions: start, retrieve (single, latest, list), update (append, patch), complete, and delete, along with resume and handoff helpers. No critical ops are missing.