Road User Tools Agent & API Platform
Connect to an AI client
Connect the Road User Tools MCP server to an AI assistant and authorize it with your account. No prior MCP experience needed.
What your agent gets
Road User Tools provides an MCP server. MCP, the Model Context Protocol, is an open standard that lets AI assistants use external tools. When you connect it, a compatible AI assistant or agent gains access to the Road User Tools calculators and can find and call those tools when a conversation needs them, for example to convert fuel economy or calculate a journey time.
https://roaduser.tools/mcpManual setup
Most AI clients follow the same pattern. The wording differs between products, but the steps are:
- Open the MCP, connectors or integrations settings in your AI client.
- Choose to add a custom or remote MCP server.
- Enter the Road User Tools MCP URL shown above.
- Continue or connect.
- Your browser opens the Road User Tools authorization page.
- Sign in to your Road User Tools account, or create one for free.
- Review the requested permissions and choose Allow access.
- Return to your AI client.
- Confirm that Road User Tools appears as connected.
- Ask a road question, for example the fuel cost of a journey, to verify the connection.
Troubleshooting
- The browser authorization page did not open
- Look for a link or button in the client such as Connect, Authorize or Sign in, and check that a pop-up was not blocked. Removing and re-adding the server usually restarts the flow.
- The client reports that authentication is required
- The connection was added but not authorized yet. Trigger the client's sign-in or reconnect action so the authorization page opens.
- Authorization was denied
- If you chose Deny, the client cannot use Road User Tools. Reconnect and choose Allow access to grant it.
- Access was revoked
- If you removed the application from your account page, its connection stops working. Reconnect from the client and authorize it again.
- The client does not support automatic authorization
- Some clients cannot run the browser sign-in flow. Use the manual setup with an API key below.
- The client requires manual configuration
- Clients configured through a JSON file rather than a settings screen can use the manual setup below.
- Connected, but no tools appear
- Refresh the client's tool list or restart the client. If tools still do not appear, remove the server and connect again.
Advanced: manual setup with an API key
For programmatic clients, scripts, or clients without browser authorization, Road User Tools also accepts API keys on the MCP server. Create a key on your account page and reference it in the client configuration:
{
"mcpServers": {
"roaduser-tools": {
"url": "https://roaduser.tools/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Both sign-in methods reach the same tools with the same permissions model.