FieldRoutes MCP Server
FieldRoutes MCP Server for Claude
Connects Claude to your FieldRoutes account so you can look up customers, check routes, view appointments, pull service history, and more — directly in conversation.
Tools included
Tool | What it does |
| Find a customer by name, phone, email, or address |
| Full details for a customer by ID |
| Past and open service tickets for a customer |
| Full details on a single service ticket |
| Scheduled appointments by date, customer, route, or tech |
| Routes running on a specific date |
| All stops on a specific route |
| Recurring service plans for a customer |
| Employee/technician list and IDs |
| Invoices and balances for a customer |
Setup
1. Copy this project and install dependencies
npm install2. Configure your credentials
cp .env.example .envOpen .env and fill in:
FR_AUTH_KEY— from FieldRoutes: Admin → API → Manage KeysFR_AUTH_TOKEN— same locationFR_SUBDOMAIN— the part before.pestroutes.comin your URL (e.g.crownpest)
3. Build and run locally to test
npm run build
npm startYou should see:
FieldRoutes MCP server running on port 3000
MCP endpoint: http://localhost:3000/mcpDeploy to Railway (recommended — free tier available)
Go to railway.app and sign up (free)
Click New Project → Deploy from GitHub repo
Connect your GitHub account and push this code to a new repo
Railway will detect Node.js and deploy automatically
In Railway, go to your project → Variables and add:
FR_AUTH_KEYFR_AUTH_TOKENFR_SUBDOMAIN
Railway will give you a public URL like
https://fieldroutes-mcp-production.up.railway.app
Deploy to Render (alternative — also free)
Go to render.com and sign up
Click New → Web Service
Connect your GitHub repo
Set Build Command:
npm install && npm run buildSet Start Command:
npm startUnder Environment, add
FR_AUTH_KEY,FR_AUTH_TOKEN,FR_SUBDOMAINDeploy — Render gives you a URL like
https://fieldroutes-mcp.onrender.com
Connect to Claude
In the Claude desktop app, go to Settings → Connectors
Click Add custom connector
Enter your deployed URL +
/mcp:https://your-app.up.railway.app/mcpSave — Claude can now use all 10 FieldRoutes tools
Verify endpoints against your FieldRoutes docs
The API paths in this server (customer/search, appointment/search, etc.) follow the standard
FieldRoutes REST pattern. If any return a 404, check your tenant-specific API docs at:
https://YOUR_SUBDOMAIN.pestroutes.com/api/docsor contact FieldRoutes support to confirm the exact path for your account tier.
Security notes
Your API credentials are stored only in environment variables — never committed to code
The server does not require its own authentication (Claude is the only caller)
For extra security, you can add an
API_SECRETenv var and validate it as a bearer token on incoming requests
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/glbryce7795/fieldroutes-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server