Fieldproxy

Name: Fieldproxy
Author: Fieldproxy

作者：Fieldproxy版本 1.0.0i★ –i在云端运行

注册名称io.github.Fieldproxy/fieldproxy-mcp

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在云端运行
传输方式: Streamable HTTP
分类: 其他
你需要填写：Authorization

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
需要你自己填写： Authorization

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

这个地址需要在请求的 header 中放入密钥，而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

在终端中运行这条命令

claude mcp add --transport http fieldproxy https://api-us-east-1.fieldproxy.ai/mcp --header 'Authorization: your-value'

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "fieldproxy": {
      "url": "https://api-us-east-1.fieldproxy.ai/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "fieldproxy": {
      "type": "http",
      "url": "https://api-us-east-1.fieldproxy.ai/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个地址需要在请求的 header 中放入密钥，而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

Authorization 机密 HTTP header
Optional 'Bearer fpmcp.…' key for the US East region. Omit to sign in with OAuth.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

我们还没有读取这个服务器的工具列表；我们会轮流检查各个端点。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 Fieldproxy 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
… 尚未检查
端点有响应
尚未检查；我们会轮流检查各个端点
… 尚未检查
使用 OAuth 登录
尚未检查；我们会轮流检查各个端点
… 尚未检查
工具描述中没有隐藏指令
尚未检查；我们会在检查端点时读取工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32371 个服务器的 0%
发布到注册中心的时间比此分类中其他 32371 个服务器的 50% 更新
基础检查结果等于或优于此分类中其他 32371 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Fieldproxy 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：Authorization

它在我的电脑上运行还是在云端？

它在作者的云端运行。通过互联网连接，无需安装，但你发送的内容会经过作者的服务器。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.0.0）于40天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Opencu

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211昨天更新

安装

Opencu

作者：Daily-AC

Independent local computer-use engine and MCP server for macOS, Windows, Linux and Android

在你的电脑上运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Fieldproxy MCP server

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.

Overview: https://www.fieldproxy.ai/mcp
Which field service software has an MCP server (verified comparison): https://www.fieldproxy.ai/mcp#which-fsm-has-mcp

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.

Region	Address
US East	`https://api-us-east-1.fieldproxy.ai/mcp`
Canada	`https://api-canada.fieldproxy.ai/mcp`
India	`https://api-india-1.fieldproxy.ai/mcp`
Norway	`https://api-norway.fieldproxy.ai/mcp`
New Zealand	`https://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

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)

Settings, Security and login: turn on Developer mode.
Create a developer-mode app named Fieldproxy with your region's address, and choose OAuth with dynamic client registration.
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)

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`](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)

In your Copilot Studio agent: Tools, Add a tool, New tool, Model Context Protocol.
Name it Fieldproxy, add a one-line description, and enter your region's address.
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.….
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).

Area	What it can do
Read	Schema and SELECT-only SQL. Customers, jobs, technicians, invoices, quotes, contracts. AR ageing, technician performance, funnels.
Write	Propose a change, confirm it, undo it. CSV import and export, record history, revert a record, restore deleted records.
Dispatch and maps	Spread jobs across technicians, plan daily routes, apply the schedule. Addresses, drive times, nearest technicians, live locations and routes, job sign-off links.
Comms	Search 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 documents	Preview and issue proposals, generate estimates and PDF documents.
Files and photos	Read PDF, Word, Excel, CSV and email files. View job photos, up to 10 at a time.
Monitoring	Dashboards, alerts, scheduled reports, the activity feed, insights, usage.
Automation operations	Run a rule, retry or dismiss failed runs, decide approvals (named approvers only).
Workspace settings	Service 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.
Build	Apps: 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.
Sandbox	Copy 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

Scope	Requires	Unlocks
`data:read`	Command Center on, and the user has Command Center access	Schema, ready-made reads, read-only SQL
`data:write`	Tables the workspace lets Command Center write, and no approval gate	Writes with undo, email and SMS drafts
`build`	An administrator, plus Allow build on the workspace	Apps, 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."