← Resources
Blog

Ask Claude About Your Test Drives: AlgoDriven Is Now a Claude Connector

20 August 2026 · 5 min read · Glenn Harwood

AlgoDriven is now listed in Claude's connector directory, and our MCP server works with ChatGPT, Cursor, Groq and any MCP-compatible assistant. Ask about your drives, bookings and appraisals in plain language — signed in as you, no API keys to manage.

Ask Claude About Your Test Drives: AlgoDriven Is Now a Claude Connector — cover image

TLDR: You’ll now find AlgoDriven in Claude’s connector directory — add it, sign in, and ask about your drives, bookings and appraisals in plain language. The same server works with ChatGPT, Cursor, Groq and anything else that speaks the Model Context Protocol. It signs in as you with your existing permissions, and there are no API keys to paste anywhere. Setup instructions are at algodriven.xyz/developers/mcp.

“How many test drives did we do last week, and how many turned into bookings?”

Until now, answering that meant opening the dashboard, setting a date range and reading the numbers off a report. Which is fine — the dashboard is good at this. But increasingly, the people asking that question are already sitting in a chat window with Claude for half their working day. The report is in one place; the question is in another.

So we closed the gap. AlgoDriven is now a connector you can add to Claude straight from its directory — no config files, no URLs to paste, nothing to install.

What it does

MCP — the Model Context Protocol — is the open standard that lets AI assistants talk to external systems. Anthropic published it, and the rest of the industry adopted it: Claude, ChatGPT, Cursor, Groq and a long list of other clients all speak it now. Building on the standard rather than one vendor’s API is why the same server that powers our Claude connector also works everywhere else.

Once connected, your assistant can pull your drive records — status, vehicle, times, odometer and fuel, salesperson, the lot — plus your booking records, filtered by date, status, source or drive type, and your EvalExpert appraisals. Then it does what AI assistants are good at: answers the actual question.

Some things our early users have asked:

  • “Which salesperson did the most test drives this month?”
  • “Show me overdue drives right now.”
  • “How far in advance do customers book, on average?”
  • “Summarise last week’s drives by source and tell me which one converts.”
  • “What did we appraise last month, and what was the average trade-in figure?”

No report builder. No export to Excel. You ask; it answers from live data.

It can also start work, not just report on it: two of the five tools create new appraisals in EvalExpert, one vehicle at a time or a list at once. Your assistant asks you to approve that before it happens, and what lands is an ordinary appraisal you pick up in EvalExpert as usual.

Built to your permissions, signed in as you

We’re a company that holds dealership data for a living — we take that seriously — so the security posture here was designed before the first line of code:

  • Your login, your permissions. The connection authenticates with your own AlgoDriven account via OAuth. It can’t see anything you couldn’t already see in the dashboard, and it doesn’t extend your access.
  • Nothing gets edited or deleted. Most tools only return records. The two that create appraisals add new ones and ask your approval first. No tool can change or remove anything that already exists.
  • No keys to leak. There’s nothing to paste into a config file. Adding the connector opens your browser to sign in, the same way you’d sign in to the dashboard.
  • Revocable in one click. Disconnect from your assistant’s settings, or revoke access from your AlgoDriven account, any time.

That last point matters for dealer groups in particular. Because every person connects with their own login, a salesperson and a group GM asking the same question get answers scoped to what each of them is already allowed to see.

One thing worth being straight about: when you ask a question, the specific records the assistant fetches are shared with the provider of that assistant — Anthropic, OpenAI, Groq or Cursor — so it can generate your response. That’s how every MCP connection works, on any platform. We’ve updated our privacy policy and terms of service to spell it out.

Connecting takes about two minutes

In Claude, open Customize → Connectors, click the +, search for AlgoDriven and connect. If you’re on a Claude Team or Enterprise plan, an owner or admin adds it once for the whole organisation and everyone else then signs in with their own account.

Everywhere else, point your client at https://mcp.algodriven.io/mcp: Cursor is a single click, Claude Code is one command, and ChatGPT uses a developer-mode connector on a paid plan. Groq works differently again — it’s for developers building their own agents on the Responses API. The setup page has step-by-step instructions for each, plus a generic config for everything else.

Where this goes

We started where the demand was loudest — DriveExpert drives and bookings, and EvalExpert appraisals. But the direction is obvious once you see it working: stock and pricing live on the same platform, and the same question-in-plain-language pattern applies to every one of them. If there’s a dataset you want your assistant to reach first, tell us.

Not an AlgoDriven customer yet? Book a demo and we’ll show you the platform the assistant plugs into.

More resources

FAQ

Frequently asked questions

What is the AlgoDriven MCP server?

It's a remote server that connects your AlgoDriven account to AI assistants that support the Model Context Protocol — Claude, ChatGPT, Cursor, Groq and others. Once connected, you can ask about your drives and bookings in plain language and the assistant pulls live records from your dealership.

How do I add AlgoDriven to Claude?

AlgoDriven is listed in Claude's connector directory. Open Customize then Connectors in Claude, click the plus button, search for AlgoDriven and click Connect, then sign in with your AlgoDriven account. On Claude Team and Enterprise plans an owner or admin adds it once for the organisation from Organization settings, after which each person connects their own account.

Which AI assistants work with it?

Claude (web, desktop and mobile), Claude Code, ChatGPT in developer mode on a paid plan, Cursor, applications built on Groq's Responses API, and any other client that supports remote MCP servers over HTTP — including VS Code, Windsurf and Zed.

Is it safe to connect an AI assistant to dealership data?

The connection signs in with your own AlgoDriven credentials and inherits your existing permissions — it can't see anything you couldn't already see in the dashboard. Most of the tools only read records; the two that start new appraisals ask for your approval first, and no tool can edit or delete anything that already exists. You can disconnect at any time from the assistant's settings or by revoking access in your AlgoDriven account.

What data does the AI assistant provider receive?

Only the specific records you ask for are shared with the provider of that assistant so it can generate your response. Details are in the AlgoDriven privacy policy.

Who can use the AlgoDriven MCP server?

It's available to DriveExpert and EvalExpert customers, exposing drive records, booking records and appraisals — you get the tools for whichever products your account is licensed for. Setup takes a couple of minutes at algodriven.xyz/developers/mcp.

Ready to price with confidence?

Book a demo Or get market insights in your inbox