Driver’s codebase MCP server exposes tools for connected AI clients. Call get_codebase_names to discover accessible codebases, then select the intended codebase and branch for the task. Tool availability depends on your organization’s context capabilities and prepared content.
Basic Codebase Context
These five tools are included in Basic and Advanced:
| Tool | Returns | Main parameters |
|---|---|---|
get_codebase_names | Accessible codebases, optionally with descriptions and type tags | include_metadata |
get_branches | Available branches for a codebase | codebase_name |
get_source_file | Source with line numbers | codebase_name, relative_file_path, start_line, max_lines, branch_name |
glob_files | File paths matching a pattern | codebase_name, pattern, max_results, branch_name |
grep_source | Source lines matching a regular expression | codebase_name, pattern, path_glob, case_sensitive, max_matches, branch_name |
Advanced Codebase Context
These tools require Advanced context. Check that preparation has completed for the intended branch before relying on generated context.
| Tool | Returns | Main parameters |
|---|---|---|
get_atlas_index | The thematic map of subsystems | codebase_name, node_id, budget_tokens, cursor, branch_name |
get_atlas_detail | One Atlas section or the sections owning a file | codebase_name, id, cursor, branch_name |
get_code_map | Directories and files with their purpose | codebase_name, relative_directory_path, max_depth, start_node, max_nodes, branch_name |
get_related | Dependencies, mirrored definitions, registration, and co-change relationships | codebase_name, path, symbols, branch_name |
change_impact | Symbol dependents and candidate tests | codebase_name, symbol, mode, detail, depth, file_hint, path_prefix, branch_name |
get_changelog | Prepared codebase change history | codebase_name, branch_name |
get_detailed_changelog | Detailed history for a month | codebase_name, year, month, branch_name |
Task-specific context
When the context agent is enabled for your organization, request_context gathers context for a particular coding or research task. Give it a detailed task_description and a codebases list containing verified codebase_name and optional branch_name values.
The call returns a request identifier. Use poll_context with request_id to check the status and retrieve the result. Keep polling the same request while it is queued or running; a running response is not a failed investigation.
Tool schemas returned by your server define the exact required fields and limits. See editor setup to connect and Agent instructions for a repository instruction example.