Field Control MCP Server

Remote MCP (Model Context Protocol) server that connects Claude to the Field Control Integration API (https://developers.fieldcontrol.com.br/), allowing you to query and create customers, work orders, employees, service requests, equipment, etc. directly in a conversation with Claude.

What it exposes

Tools available to Claude:

Related MCP server: Jobber MCP Connector

1. Get your Field Control API key

1. Access the Field Control dashboard as an administrator.

2. Go to Settings > Developer settings (or directly: https://app.fieldcontrol.com.br/#/configuracoes/configuracao-para-desenvolvedores).

3. Under "Integration key", click to create a new key, give it a name, and click Create.

4. Save that key — you'll use it as the FIELD_CONTROL_API_KEY environment variable.

2. Run locally (optional, for testing)

npm install
FIELD_CONTROL_API_KEY="sua-chave-aqui" npm start

The server starts at http://localhost:3000, with the MCP endpoint at POST /mcp.

3. Put the server on the internet (required for Claude to access it)

Claude connects from the Anthropic cloud, so the server needs to be publicly accessible over HTTPS. Any provider that runs Node.js works. Two simple options with a free tier:

Option A: Render.com

1. Push this project to a GitHub repository.

2. On Render, create a Web Service pointing to the repository.

3. Build command: npm install — Start command: npm start.

4. Under "Environment", add the FIELD_CONTROL_API_KEY variable with your key.

5. After deployment, you'll have a URL like https://seu-app.onrender.com. The MCP endpoint will be https://seu-app.onrender.com/mcp.

Option B: Railway.app

1. Push the project to GitHub.

2. On Railway, "New Project" > "Deploy from GitHub repo".

3. Add the FIELD_CONTROL_API_KEY environment variable.

4. Railway detects npm start automatically and exposes a public URL.

(Any other Node.js host — Fly.io, Vercel with functions, your own VPS with Nginx, etc. — works the same way, as long as it exposes /mcp over HTTPS.)

4. Connect to Claude as a custom connector

1. In Claude, go to Settings > Connectors.

2. Click + and then Add custom connector.

3. Paste your server URL ending in /mcp (e.g., https://seu-app.onrender.com/mcp).

4. Give it a name (e.g., "Field Control") and click Add.

That's it — in future conversations, Claude will be able to list your work orders, customers, employees, etc. whenever that helps answer what you ask.

On Team/Enterprise plans, an Owner must enable the connector first in Organization Settings > Connectors > Add > Custom > Web; then each member connects their own account.

Security

• The API key stays only on the server (environment variable), never exposed to Claude or the browser.

• By default, everyone using this server shares the same API key (the one from the environment). If you want to offer this connector to multiple people with different keys, adapt getApiKeyFromRequest() in src/server.js to read the key from a per-request header, and have each person configure that in the connector's "Advanced settings".

• Never commit your API key to the repository — always use environment variables from the hosting provider.