Fieldproxy

io.github.Fieldproxy由 GitHub 账号 Fieldproxy 发布v1.0.0更新于 Oct 24, 2026

Field service management: jobs, dispatch, invoices, quotes and building apps, confirm before change.

已验证Streamable HTTP可网页运行效率与工作流开发者工具商业与电商

概览

AI 生成的概览

Fieldproxy 托管的 MCP 服务器让 AI 助手读取并修改现场服务工作区（工单、派工、发票、报价），还能构建应用，每项变更都需人工确认。

可以做什么
读取数据库结构与只读 SQL，以及客户、工单、技师、发票、报价、合同和 AR 账龄、技师绩效、漏斗等报表。提出、确认并撤销写入；导入导出 CSV；回滚记录、恢复已删除记录。规划派工与路线，查询地址、行驶时间、最近技师和实时位置。搜索收件箱、起草邮件和短信并确认发送；预览提案、生成估价和 PDF。读取 PDF、Word、Excel、CSV 和邮件文件，查看工单照片。在沙箱中构建应用、数据表、自动化和智能体草稿，再推送到正式环境。
适用场景
适合使用 Fieldproxy 管理现场服务运营的团队：让助手跨工单、发票和排班回答问题，起草客户邮件，规划派工，或在管理员批准下构建和修改工作区应用与自动化。
运行要求
远程 streamable HTTP 端点，地址取决于工作区所在区域（美东、加拿大、印度、挪威或新西兰）。认证方式为带动态客户端注册的 OAuth 2.0，或在 Authorization 请求头中发送 bearer 密钥。AI 助手访问默认关闭，需管理员按工作区启用；构建功能还需开启 Allow build。
安装前请注意
该服务器可写入、发送、导入和删除数据，并修改工作区软件；写入以提案形式在 30 分钟内由用户确认，且可撤销。密钥只显示一次，可按有效期、数据表、行和隐藏列限制范围。邮件发送有频率上限且仅限用户本人邮箱。每次调用都会记录工具、密钥、人员与结果。Copilot Studio 需要 Microsoft 许可证，且可能被 Power Platform 数据策略阻止。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Fieldproxy，将其添加到工作区。
  2. 连接 所需的 凭据。它们会被私密存储，绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.Fieldproxy%2Ffieldproxy-mcp/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。

{
  "mcpServers": {
    "fieldproxy": {
      "type": "http",
      "url": "https://api-us-east-1.fieldproxy.ai/mcp"
    }
  }
}

README

Fieldproxy MCP server

[Fieldproxy MCP connector – tool definition quality and endpoint health on Glama]

The official Model Context Protocol server for Fieldproxy, AI-native field service management.

It lets the AI assistant your team already uses (Claude, ChatGPT, Microsoft 365 Copilot and Teams, GitHub Copilot, Cursor, OpenAI Codex, Claude Code, or any MCP client) read and change a Fieldproxy workspace, and build on it, with a person confirming every change.

The part no other field service MCP server does: your AI can change the software itself. Ask for a new field, screen, table, automation or agent, and it is built as a draft in a sandbox copy of your workspace and goes live only when an administrator approves, with rollback.

This repository holds documentation and client configuration. The server itself is hosted by Fieldproxy; there is nothing to install or run.

Addresses

Use the address for your workspace's region.

RegionAddress
US Easthttps://api-us-east-1.fieldproxy.ai/mcp
Canadahttps://api-canada.fieldproxy.ai/mcp
Indiahttps://api-india-1.fieldproxy.ai/mcp
Norwayhttps://api-norway.fieldproxy.ai/mcp
New Zealandhttps://api-nz.fieldproxy.ai/mcp

Transport: streamable HTTP. Auth: OAuth 2.0 with dynamic client registration (sign in with workspace ID, email and password), or a bearer key (fpmcp.…).

Before you connect

AI assistant access is off by default. Fieldproxy switches it on per workspace (Portal, Org features, AI assistant access, Enabled, and optionally Allow build). Ask your Fieldproxy contact, or book a demo.

Keys (fpmcp.…) are made in the Fieldproxy web app under Settings, AI assistant, New key. Each key is shown once. An administrator can set up a key for someone else; that person claims it once from their own screen, so the administrator never sees the key.

Connect a client

Claude (Desktop and claude.ai)

Add a custom connector with your region's address, then sign in with workspace ID, email and password and tick the scopes. The sign-in lasts 1 hour and renews itself for 30 days. Guide: https://www.fieldproxy.ai/mcp/claude

Claude Code

bash
claude mcp add --transport http fieldproxy https://api-us-east-1.fieldproxy.ai/mcp \  --header "Authorization: Bearer fpmcp.…"

ChatGPT (web: Plus, Pro, Business, Enterprise, Edu)

  1. Settings, Security and login: turn on Developer mode.
  2. Create a developer-mode app named Fieldproxy with your region's address, and choose OAuth with dynamic client registration.
  3. Sign in on the Fieldproxy page and tick the permissions to allow.

ChatGPT asks before each write action by default; Fieldproxy's own confirm step still applies on top. Guide: https://www.fieldproxy.ai/mcp/chatgpt

OpenAI Codex (CLI, IDE extension, desktop)

bash
export FIELDPROXY_MCP_KEY="fpmcp.…"codex mcp add fieldproxy --url https://api-us-east-1.fieldproxy.ai/mcp --bearer-token-env-var FIELDPROXY_MCP_KEY

Or in ~/.codex/config.toml: see examples/codex-config.toml. To sign in instead of using a key, add the server without --bearer-token-env-var, then run codex mcp login fieldproxy.

GitHub Copilot in VS Code

Copy examples/vscode-mcp.json to .vscode/mcp.json. VS Code asks for the key once and hides it. Leave out headers to sign in through the Fieldproxy page instead.

Microsoft 365 Copilot and Teams (Copilot Studio)

  1. In your Copilot Studio agent: Tools, Add a tool, New tool, Model Context Protocol.
  2. Name it Fieldproxy, add a one-line description, and enter your region's address.
  3. Authentication: OAuth 2.0, Dynamic discovery (each person signs in with their own Fieldproxy account), or API key, type Header, name Authorization, value Bearer fpmcp.….
  4. Create the connection, Add to agent, then publish the agent to Teams and Microsoft 365 Copilot.

Copilot Studio needs its own Microsoft licence, and a Power Platform data policy can block the connection. Guide: https://www.fieldproxy.ai/mcp/copilot

Cursor and other JSON-config clients

See examples/cursor-mcp.json.

What it can do

145 built-in tools, plus up to 14 Command Center ready-made reads and any tools the workspace defines itself (saved SQL tools).

AreaWhat it can do
ReadSchema and SELECT-only SQL. Customers, jobs, technicians, invoices, quotes, contracts. AR ageing, technician performance, funnels.
WritePropose a change, confirm it, undo it. CSV import and export, record history, revert a record, restore deleted records.
Dispatch and mapsSpread jobs across technicians, plan daily routes, apply the schedule. Addresses, drive times, nearest technicians, live locations and routes, job sign-off links.
CommsSearch the inbox and read threads. Draft emails and SMS (with templates), then confirm the send. Notifications, comments, email follow-ups, list and place calls.
Sales documentsPreview and issue proposals, generate estimates and PDF documents.
Files and photosRead PDF, Word, Excel, CSV and email files. View job photos, up to 10 at a time.
MonitoringDashboards, alerts, scheduled reports, the activity feed, insights, usage.
Automation operationsRun a rule, retry or dismiss failed runs, decide approvals (named approvers only).
Workspace settingsService zones, saved views, Command Center memory.
AI oversight (admins)Every AI connection in the workspace, what each one did, usage by key, person and tool, revoking access.
BuildApps: validate, draft, publish, roll back. Tables and columns (nothing is ever dropped). Automations and voice or text agents: validate, save, simulate, enable, restore a version. Document, email, proposal and estimate templates.
SandboxCopy the workspace, build in the copy, then plan and confirm a promotion to live.

Seven ready-made workflows (prompts): daily_ops_briefing, plan_the_schedule, triage_my_inbox, why_did_this_automation_fail, customer_360, build_an_app, build_a_dashboard.

Scopes

ScopeRequiresUnlocks
data:readCommand Center on, and the user has Command Center accessSchema, ready-made reads, read-only SQL
data:writeTables the workspace lets Command Center write, and no approval gateWrites with undo, email and SMS drafts
buildAn administrator, plus Allow build on the workspaceApps, tables, automations, agents, sandboxes

The user's own Command Center access sets the ceiling. A key can be limited further: expiry (1 hour to 90 days), tables, rows (for example "only team A's jobs"), hidden columns, insert/update/delete, and switches for SQL, sending and build areas. Postgres enforces row limits, and hidden columns are removed from every result.

Guardrails

  • Confirm before change. Every write, send or action is a proposal the user confirms within 30 minutes. Writes can be undone. More than 5 rows needs bulk permission; more than 1,000 is refused.
  • Builds save as drafts. Saving or publishing is blocked if the linter, a SQL check against the database, or a navigation check finds a new error. New automations and agents are saved switched off. Public apps are never published or changed.
  • Sends are limited. Email goes only from the user's own mailbox, at most 20 sends an hour per key, inside the workspace's quiet hours. A sandbox never sends.
  • Stateless and audited. Every request is authorised from scratch, so a revoked key is refused on the next call. Every call is logged with the tool, key, person and outcome.

Example asks

  • "What did we finish last week that nobody invoiced?"
  • "Mike is out sick. Move his jobs to whoever is closest and show me the plan."
  • "Which quotes over $5,000 have had no follow-up in two weeks? Draft the emails."
  • "Add a warranty expiry date to every job, and alert the service manager 30 days before one runs out."
  • "Build a subcontractor compliance screen that flags missing insurance."

Links

来源：README.md，提交 b93d5fc

工具

0
该服务器需要登录，因此 SourceWeft 无法在没有账号的情况下读取其工具，也未收录。已连接账号所能看到的内容可能因账号及其权限而异。

版本历史

1
  1. v1.0.0最新Sep 27, 2026

评分

已满足适用检查项的 75%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。