Fill-Rite MCP
This server allows agents to interact with a Fill-Rite fuel management system, providing access to tanks, sites, vehicles, and drivers.
Tanks
List all tanks (
get_all_tanks)Get detailed information on a specific tank by ID (
get_single_tank_detail) — ID must not be revealed to users
Sites
List all sites (
get_all_sites)Get detailed information on a specific site (
get_site_details)
Vehicles
List all vehicles (
get_all_vehicles)Retrieve a filtered list of vehicles (
get_all_vehicles_filtered)Get detailed information on a specific vehicle (
get_vehicle_detail)
Drivers
List all drivers (
get_all_drivers)Get detailed information on a specific driver (
get_driver_detail)
Note: Access tokens are automatically refreshed, provided the server is used at least once per week.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Fill-Rite MCPshow my current fuel tank levels"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Fill-Rite MCP
This project is an MCP to allow agents to interact with a user's Fill-Rite.
Access Tokens
Fill-Rite access tokens go stale in 30 minutes, and refresh tokens go stale in 7 days. You must run the refresh_tokens() function at least once per week (before the 7 days are up!) otherwise you will need to add new tokens to your tokens.json file.
Tokens are checked for staleness at every tool call, and refreshed if needed, so as long as the MCP is used once per week you will be fine.
You could also set up a cron job to refresh your token every 3-4 days, or you could set a scheduled prompt on your AI agent that makes any tool call in this MCP at least once per week.
Related MCP server: Access
Setup
I have only tested this on macOS, and these setup steps assume you use macOS. In the future I plan to write an install script that will make setup simple.
Claude Code
Navigate to the directory you want to run the MCP in and clone the repo:
git clone https://github.com/ribeck18/fill-rite-mcp.gitRegister the MCP with Claude Code:
claude mcp add fillrite -- uv run --directory {path_to_repo} main.pyIn the directory you just cloned, make a new file called
tokens.json. Paste the following into it, replacing the placeholders with your API tokens from Fill-Rite:
{
"access_token": {
"token": "{your_access_token}",
"expires_at": ""
},
"refresh_token": {
"token": "{your_refresh_token}"
}
} Make sure your access token starts with "Bearer ". Leave expires_at blank for now.
In the same directory, make a file called
.env. Paste the following into it:
BASE_URL=https://fmsapi.fillrite.com/rest/v1.0/Your MCP should now function properly in Claude Code.
Claude Desktop
Navigate to the directory you want to run the MCP in and clone the repo:
git clone https://github.com/ribeck18/fill-rite-mcp.gitIn the directory you just cloned, make a new file called
tokens.json. Paste the following into it, replacing the placeholders with your API tokens from Fill-Rite:
{
"access_token": {
"token": "{your_access_token}",
"expires_at": ""
},
"refresh_token": {
"token": "{your_refresh_token}"
}
} Make sure your access token starts with "Bearer ". Leave expires_at blank for now.
In the same directory, make a file called
.env. Paste the following into it:
BASE_URL=https://fmsapi.fillrite.com/rest/v1.0/Navigate to your claude desktop config file. If it does not exist, create it.
~/Library/Application\ Support/Claude/claude_desktop_config.jsonAdd the following to that file.
{
"mcpServers": {
"Fill-Rite": {
"command": "{path_to_uv}",
"args": [
"run",
"--directory",
"{path_to_cloned_repo}",
"main.py"
]
}
}
}Your path to uv can be found with which uv.
Restart your Claude Desktop app. After restart the MCP should function.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityFmaintenanceEnables AI assistants to interact with GoHighLevel's complete API including contacts, opportunities, calendars, workflows, communications, and business management tools. Supports both Bearer token and OAuth2 authentication with automatic token management.137MIT
- Alicense-qualityCmaintenanceSelf-hosted credential store and API proxy for AI agents. One Bearer token, all your services. Handles OAuth refresh, encrypted storage, audit logging, and per-agent permissioning.38MIT
- AlicenseBqualityDmaintenanceProvides AI agents with direct access to FileMaker databases through the FileMaker Data API, enabling natural language interactions for querying, managing records, and database introspection.28203MIT
- Flicense-qualityDmaintenanceEnables AI assistants to create notes, save links, append to daily notes, and manage knowledge graphs in Reflect via the Reflect Notes API, with OAuth2 authentication and token management.3
Related MCP Connectors
Odoo ERP for AI agents: hosted OAuth endpoint, gated writes, one endpoint for every instance.
Connect AI agents to bank accounts, transactions, balances, and investments.
Provide AI agents and automation tools with contextual access to blockchain data including balance…
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ribeck18/fill-rite-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server