MCP Tools
The Driver MCP server exposes 7 tools. Each tool returns pre-computed context about your codebases. Your AI agent calls these tools automatically based on your prompts.
You do not call these tools directly. Ask your agent a question in natural language, and it selects the right tool. This reference helps you understand what is available and how to prompt for it.
get_codebase_names
Returns all codebases available in your Driver organization.
Parameters
None.
When to use
Call this first in any session. It returns the list of valid codebase names that other tools require.
Example prompt
"What codebases are available in Driver?"
get_architecture_overview
Returns a comprehensive architecture document that covers system structure, key components, design patterns, and relationships.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| codebase_name | string | Yes | Name of the codebase. Must match a value from get_codebase_names. |
When to use
Start of any task that requires broad codebase understanding. This is the single most valuable tool for grounding the agent in accurate structure before it answers questions.
Example prompt
"Show me the architecture of my-backend"
get_llm_onboarding_guide
Returns a guide optimized for AI agents. It covers navigation tips, key entry points, coding conventions, and cross-references to important files.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| codebase_name | string | Yes | Name of the codebase. Must match a value from get_codebase_names. |
When to use
Start of a session to build broad codebase familiarity. Pairs with get_architecture_overview to give the agent a complete foundation.
Example prompt
"Get oriented with my-backend"
Most agents call both get_architecture_overview and get_llm_onboarding_guide together when you ask them to "get oriented." This loads 1-2 pages of dense context into the agent's working memory.
get_changelog
Returns a high-level development timeline organized by year and month. Each entry summarizes the major changes for that period.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| codebase_name | string | Yes | Name of the codebase. Must match a value from get_codebase_names. |
When to use
Understanding development history, major feature introductions, and architectural decisions over time. Use this to identify which time period to inspect, then call get_detailed_changelog to drill in.
Example prompt
"What has changed in my-backend recently?"
get_detailed_changelog
Returns detailed commit-level information for a specific month. Includes descriptions of what changed and why.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| codebase_name | string | Yes | Name of the codebase. Must match a value from get_codebase_names. |
| year | string | Yes | The year to query (e.g., "2026"). |
| month | string | Yes | The month to query (e.g., "01" for January). |
When to use
Deep-diving into why specific changes were made during a given month. Call get_changelog first to identify the relevant time period.
Example prompt
"What happened in my-backend in January 2026?"
get_code_map
Returns a flat list of files and directories with AI-generated descriptions. Supports adjustable depth and pagination for large codebases.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| codebase_name | string | Yes | Name of the codebase. Must match a value from get_codebase_names. |
| relative_directory_path | string | No | Directory to explore, relative to the codebase root. Defaults to the root directory. |
| max_depth | integer | No | How many levels deep to traverse. Defaults to 2. |
When to use
Finding relevant files, understanding directory structure, and exploring unfamiliar areas of a codebase. The agent typically starts broad at the root, then narrows to a specific directory.
Example prompt
"What files handle authentication in my-backend?"
get_file_documentation
Returns symbol-level documentation for a specific file: functions, classes, interfaces, imports, and their descriptions. Supports pagination for large files.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| codebase_name | string | Yes | Name of the codebase. Must match a value from get_codebase_names. |
| relative_file_path | string | Yes | Path to the file, relative to the codebase root (e.g., "src/auth/middleware.ts"). |
When to use
Understanding the internals of a specific file. Use after get_code_map identifies the relevant file path.
Example prompt
"Show me the documentation for src/auth/middleware.ts"
Code maps and file documentation work best after orienting. When the agent already knows the architecture, it navigates to the right file on the first try instead of scanning the full tree.