fieldwork-mcp
Enables pest control business owners using Fieldwork to ask plain-English questions about customers, invoices, product usage, schedules, and technicians, returning clear answers from the Fieldwork API. Read-only access with no ability to modify jobs, customers, or payments.
README
Fieldwork MCP
Ask your pest control business questions in plain English.
Works with Claude, Cursor, Codex, and other AI apps that support MCP.
“How many customers do I have?”
“Who owes me money?”
“How much Alpine did we use this week?”
“Who did the most jobs?”
Your AI asks Fieldwork. You get a clear answer.
Read-only — it can’t change jobs, charge cards, or edit customers.
Site: landing/index.html (Relay home) · landing/fieldwork.html (Ask Fieldwork) · Roadmap: ROADMAP.md
Who this is for
Pest and lawn-care owners who run Fieldwork and want answers without digging through reports.
Why can’t they just ask Claude or Cursor to set it up?
Often they can — if they’re already in Cursor or Claude Code with this project open, say:
Set up Fieldwork MCP for me. I’ll paste my API key into
.env.
The agent can create the venv, write MCP config, and wire the launcher.
You still need to get the API key yourself (it’s your Fieldwork password-equivalent).
Don’t paste the key into a random chat if you can drop it straight into .env.
When a copy-paste snippet still helps
- You’re on the website and don’t have an agent in the folder yet
- You’re on Claude Desktop, which doesn’t edit your disk the same way
- Someone else is setting up a machine without opening this repo
The endgame (see Roadmap) is a one-line remote URL + login, like LandingFolio — no Terminal, no JSON.
What you can ask
Customers
- How many customers do I have?
- Do I have a customer named ___?
Money
- Who owes me money?
- How much did we make this month?
- How is business doing?
Product
- How much product was used?
- What chemicals do we carry?
Schedule, routes & technicians
- What’s on the schedule this week?
- Who are my technicians?
- How are my routes doing?
- Who did the most jobs?
Bonus prompt: monday_morning_briefing — one bundled ops snapshot.
Quick start
1. Get your Fieldwork API key
Easiest path (in the Fieldwork app):
- Go to Settings → Users & Routes
- Open your user (or an API Integration user)
- Open the Integration tab and copy the API Key
Help: Fieldwork APIs
2. Install
git clone https://github.com/daisydaines/fieldwork-mcp.git
cd fieldwork-mcp
python3 -m venv .venv
source .venv/bin/activate # Windows: .venv\Scripts\activate
pip install -e .
cp .env.example .env
# put FIELDWORK_API_KEY=... in .env
3. Connect your AI app
Cursor — ~/.cursor/mcp.json:
{
"mcpServers": {
"fieldwork": {
"command": "/ABS/PATH/TO/fieldwork-mcp/scripts/run_mcp.sh"
}
}
}
Claude Desktop — same JSON in
~/Library/Application Support/Claude/claude_desktop_config.json
Claude Code:
claude mcp add fieldwork -- /ABS/PATH/TO/fieldwork-mcp/scripts/run_mcp.sh
Codex — add a stdio MCP server pointing at scripts/run_mcp.sh (same idea as Cursor).
Then restart the app and ask: How many customers do I have?
Hosted connect (no Dropbox-style OAuth)
Fieldwork does not offer a third-party OAuth login popup. Closest path:
./scripts/run_mcp_http.sh
# open http://127.0.0.1:8000/connect
Paste your API key once. You get a bearer token and a one-line snippet for Claude / Cursor / Codex.
Also serves the Relay landing at /.
| URL | What |
|---|---|
http://127.0.0.1:8000/ |
Landing |
http://127.0.0.1:8000/connect |
Paste API key → connect token |
http://127.0.0.1:8000/mcp |
Streamable HTTP MCP (Authorization: Bearer <token>) |
For a shared deploy, set FIELDWORK_VAULT_SECRET (required) and FIELDWORK_PUBLIC_BASE_URL
(e.g. https://mcp.example.com). See Dockerfile. Keep FIELDWORK_MCP_ALLOW_ENV_FALLBACK=0.
Safety
| Can do | Cannot do |
|---|---|
| Read customers, jobs, invoices, usage | Create or edit customers |
| Summarize routes & techs | Cancel or reschedule jobs |
| Report product used on jobs | Take payments or change prices |
Tools are annotated readOnlyHint. The HTTP client refuses non-GET requests.
For builders
pip install -e ".[dev]"
pytest
ruff check src tests
./scripts/run_mcp.sh # stdio
./scripts/run_mcp_http.sh # streamable-http
Auth to Fieldwork: api-key header (default).
Unofficial. Not affiliated with Fieldwork / Anstar Products.
License
MIT — see LICENSE.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。