Use Driver from an AI tool through MCP or the CLI. Choose the connection that fits the task:
| Task | Connection |
|---|---|
| Run investigations and see evidence inside Claude Cowork or ChatGPT Work | Driver Investigations MCP App. Contact Driver support for early access. |
| Give a coding agent access to source and prepared codebase context | Driver MCP. Basic provides source discovery and search; Advanced adds prepared context tools. |
| Ask Driver to run an investigation, continue it, or read its report | Driver CLI, from a tool that can run terminal commands. |
Investigate with the MCP App
The Driver Investigations MCP App lets you start an investigation, ask follow-up questions, and review findings and source evidence directly in Claude Cowork or ChatGPT Work.
Contact Driver support for early access. Support will provide the investigation App’s connection URL and setup instructions for your AI tool. Once connected, ask the tool to investigate a Jira ticket URL or a question about your codebase, then use the App to review the evidence and continue the investigation.
Connect to codebase context through MCP
Use https://api.us1.driverai.com/mcp/v1 for the standard Driver codebase MCP server, or your organization’s private-deployment URL. Add it in your AI tool’s MCP connection settings and complete Driver sign-in.
The server advertises the tools available to your organization. Ask the AI tool to discover your codebases with get_codebase_names, find a known file, and read its source. See MCP tools for the Basic and Advanced tool lists.
For Claude Code, Cursor, and VS Code setup, use Use it in your editor. A managed AI workspace may require an administrator to enable the connection.
Investigate through the CLI
Install and sign in to the Driver CLI in the environment where your AI assistant runs commands. Ask the assistant to use Driver for the investigation, retain its identifier, and use that identifier for follow-ups.
driver investigate start "Investigate https://example.atlassian.net/browse/SUP-2143. Webhook retries stop after the first failure in the payments codebase."
driver investigate send <investigation> "Check which retry condition explains the reported failure."
driver investigate report <investigation>Replace the example URL with your Jira ticket URL and <investigation> with the identifier returned by start. Jira and the relevant codebase must be connected. To use Answers, pass a code question to start and read the response in the output or transcript. The CLI also supports requesting a draft from your ticket report and giving feedback. The CLI reference lists the full command options.
Check evidence before acting
Ask the assistant to show the report’s evidence and distinguish confirmed findings from hypotheses. Review a proposed workaround or customer reply before using it, and copy the relevant result into Jira or the destination where your team works.
Codebase MCP and CLI requests use the access of the Driver account or credential used by the connection. Keep credentials in the tool’s supported credential storage rather than putting them in the prompt.