FieldRobin
RemoteAbout FieldRobin
Authenticated FieldRobin workspace tools, including scope-authorized customer and job creation
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://fieldrobin.com/api/v1/mcpclaude mcp add --transport http com-fieldrobin-fieldrobin https://fieldrobin.com/api/v1/mcp{"mcpServers":{"com-fieldrobin-fieldrobin":{"type":"http","url":"https://fieldrobin.com/api/v1/mcp"}}}Open in Cursor{"servers":{"com-fieldrobin-fieldrobin":{"type":"http","url":"https://fieldrobin.com/api/v1/mcp"}}}Open in VS Code{"mcpServers":{"com-fieldrobin-fieldrobin":{"type":"http","url":"https://fieldrobin.com/api/v1/mcp"}}}{"mcpServers":{"com-fieldrobin-fieldrobin":{"serverUrl":"https://fieldrobin.com/api/v1/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
47| Parameter | Type | Required | Description |
|---|---|---|---|
| name | string | Yes | Customer full name. |
| string|null | No | Customer email address, if known. | |
| notes | string|null | No | Internal customer notes. |
| phone | string|null | No | Customer phone number, if known. |
| address | string|null | No | Customer address, if known. |
| trade_type | string|null | No | Customer trade or service type. |
| location_id | integer|null | No | Business location for the customer. |
| business_name | string|null | No | Customer business name, if known. |
| lifecycle_tag | enum | No | Lifecycle tag.active | inactive | vip |
| idempotency_key | string | Yes | Opaque retry key. Reuse it only for the same request to receive the verified result without creating a duplicate. |
| acquisition_source | string|null | No | How the customer was acquired. |
Details
The maintainer has not added details yet. Check the README in the repository.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.