Skip to content

Reference

MCP tools

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:

ToolReturnsMain parameters
get_codebase_namesAccessible codebases, optionally with descriptions and type tagsinclude_metadata
get_branchesAvailable branches for a codebasecodebase_name
get_source_fileSource with line numberscodebase_name, relative_file_path, start_line, max_lines, branch_name
glob_filesFile paths matching a patterncodebase_name, pattern, max_results, branch_name
grep_sourceSource lines matching a regular expressioncodebase_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.

ToolReturnsMain parameters
get_atlas_indexThe thematic map of subsystemscodebase_name, node_id, budget_tokens, cursor, branch_name
get_atlas_detailOne Atlas section or the sections owning a filecodebase_name, id, cursor, branch_name
get_code_mapDirectories and files with their purposecodebase_name, relative_directory_path, max_depth, start_node, max_nodes, branch_name
get_relatedDependencies, mirrored definitions, registration, and co-change relationshipscodebase_name, path, symbols, branch_name
change_impactSymbol dependents and candidate testscodebase_name, symbol, mode, detail, depth, file_hint, path_prefix, branch_name
get_changelogPrepared codebase change historycodebase_name, branch_name
get_detailed_changelogDetailed history for a monthcodebase_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.