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 分

    請在儲存庫或註冊中心條目中宣告授權條款。