Repository avatar
Developer Tools
v0.1.0
active

driveguide

io.github.CloudCorpRecords/driveguide

Drivings study reads: published guides, test-centre search, study options and plan previews.

Documentation

driveguide

Study for a driving test with published material, not guesswork. driveguide is a local forwarding client for the hosted Drivings MCP service: it answers tools/list locally from the captured tool definitions and forwards every call to Drivings, returning the answers exactly as the service sends them back.

From here you can search the published guides by topic, open one guide in full, see which study courses are offered for the UK or the US, look up verified test centres in the source-backed directory, and compute a bounded study-plan preview that is never saved anywhere. One further read shows the connected learner's own profile and recent activity; that one needs the learner's own Drivings sign-in and consent upstream, and an unauthenticated call simply surfaces the upstream error. Nothing is cached or stored locally — the package is a pipe to the study service, not the service itself.

All 6 captured tools are built; there are no omissions.

The tools

  • search_driving_guides — Search published guides by topic or question; returns concise metadata, update dates and canonical URLs. region and query are required.
  • get_driving_guide — Retrieve one published guide by slug, including bounded Markdown content and review details when available. region and slug are required.
  • list_study_options — List the study courses published for the UK or US, with canonical pages and a confirmation-required onboarding handoff. region is required.
  • find_test_centres — Search the source-backed UK or US test-centre directory by name, locality, address, postcode/ZIP, alias or identifier. region is required; it never books or changes a test.
  • build_study_plan_preview — Compute a deterministic, bounded study schedule. The preview is not saved and creates no account, session, purchase or message. region and course are required.
  • get_my_learning_overview — Read the connected learner's profile, study target and recent activity. Requires Drivings sign-in and explicit OAuth consent upstream; it never changes learner or account data. No parameters.

Install and run

As an MCP server via npm:

npx -y @reneturcios/driveguide mcp

MCP client configuration:

{
  "mcpServers": {
    "driveguide": {
      "command": "npx",
      "args": ["-y", "@reneturcios/driveguide", "mcp"]
    }
  }
}

As a container:

docker run -i ghcr.io/cloudcorprecords/driveguide
docker run --rm ghcr.io/cloudcorprecords/driveguide list_study_options '{"region":"uk"}'

CLI

One binary serves both the command line and the MCP server. Each tool is a subcommand taking a single JSON string with that tool's arguments:

driveguide search_driving_guides '{"region":"uk","query":"roundabouts"}'
driveguide list_study_options '{"region":"us"}'
driveguide build_study_plan_preview '{"region":"uk","course":"car"}'
driveguide --version

Exit codes: 0 when the forwarded call succeeds, 1 when the upstream result is an error, and 2 for usage problems such as an unknown subcommand or a malformed JSON argument.

Configuration

  • DRIVINGS_MCP_URL — Overrides the upstream endpoint. The default is the pinned hosted endpoint, https://mcp.drivings.com/mcp. (The override variable is a reconstruction added by this rebuild.)

The upstream registry record declares no headers, so no authentication header is ever sent; the published-content tools were captured keyless. The learner-overview read depends on the learner's own sign-in upstream, which this client does not perform — without it, the upstream error is what the caller sees.

Upstream failures — a JSON-RPC error from the service, a non-2xx response, an unreadable body, or a request that fails outright — are reported to the caller as an error result whose text starts with driveguide error:.

How forwarding works

The first forwarded call opens a session: an initialize request (protocol version 2025-03-26), followed by a notifications/initialized notification, then the tools/call itself. If the service answers the initialize request with an Mcp-Session-Id header, that value is carried on every later request, and the open session is reused for the rest of the process. Replies are accepted either as plain JSON or as server-sent events. Successful results pass through verbatim, including any isError flag and any extra fields the service includes.

Development

npm install
npm run build   # tsc -> dist/ (dist/cli.js is the bin)
npm test        # tsx --test test/*.test.ts — stubbed upstream, no network
npm run dev     # run the CLI from source

The test suite checks the served tool list against the captured surface (all 6 tools, deep-equal, in order, with captured titles served and no required key added to the parameterless overview tool), exercises the session handshake and its reuse, verifies that no Authorization header is ever sent, and verifies that arguments go upstream untouched and results come back untouched.

License

MIT — see LICENSE. Copyright (c) 2026 Rene Turcios.

NPM
@reneturcios/driveguide
Install Command
npm install @reneturcios/driveguide
Runtime: npx
OCI
ghcr.io/cloudcorprecords/driveguide:0.1.0
Install Command
docker pull ghcr.io/cloudcorprecords/driveguide:0.1.0:undefined
Runtime: docker