Support Agent MCP

The Support Agent MCP server is how you build support agents on Road. It gives an agent a defined set of tools to answer customer questions and act on the platform on a customer's behalf, over the Model Context Protocol.

The documentation has three parts:

Endpoint

The partner MCP server is at:

https://partner-mcp.road.io

Connect to it as an MCP client. Every request is authenticated with a client token (Authorization: Bearer <jwt>), which identifies the client and the provider tree it may reach.

Getting access

Access is granted per client. To have a client registered and the tools you need enabled, contact your Road account support manager. They will set up the client, scope it to the right providers, and enable the tools for your integration. A client only ever sees the tools it has been granted.

Tool naming

Tool names are <category>-<action>, hyphenated and globally unique, for example charge-points-find and customer-verify. The category matches the tool's group in the reference.

What a tool can see

Access is layered. A call passes through each gate before it reaches a tool:

  1. Client authentication. Every request carries the client token, which resolves the provider tree the client may reach (a root provider and all of its children).
  2. Per-client tool access. An operator enables each tool per client (see Getting access above). A tool that is not enabled is hidden from tool listings and rejected if called.
  3. Provider scoping. Provider-scoped data is filtered to the client's providers. Anything outside that tree is invisible.
  4. Caller identity. Some tools require a verified customer attached to the conversation. A caller with account-level read access to a resource sees it across the whole account; other callers see only their own users, cards, charging stations and home-charging sessions. A colleague's home charging station (employee reimbursement) is never shown, whatever the caller's access. A lookup that falls outside your scope returns the same "not found" response as a record that does not exist, so ownership is never revealed.

Client vs customer

Because the client is always authenticated, each tool's Access line in the reference is about the customer, not the client: whether the tool needs a verified customer attached to the conversation.

  • No customer verification tools work without one, for example a person standing at a station, or a first-line card check.
  • Requires a verified customer tools need the customer to be verified first. See Customer verification.

Read-only and state-changing tools

Most tools are read-only. A few change state or act on hardware, and are flagged in the reference:

  • charge-points-reboot sends a reset to a station, behind a server-side safety check.
  • charge-points-unlock releases a stuck cable.
  • customer-request-verification, customer-verify and customer-authorize create or upgrade a conversation.