singleops-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@singleops-mcp Find client by email jane@example.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
SingleOps MCP
First MCP server for the SingleOps Public API — let Claude, Cursor, or any MCP client read operations, look up clients, and create leads in SingleOps, the leading US green-industry field-service platform (landscaping, tree care, irrigation, lawn care, sod farms), part of Granum (1,000+ customers).
Why this exists
SingleOps is the operations backbone for thousands of tree-care companies,
lawn-care operators, and full-service landscaping businesses across the US
and Canada. The public REST API at app.singleops.com/api/v1/ has been
documented since the mid-2010s, but until now no one had wrapped it for
MCP clients. The fitness/wellness MCP space is saturated (Mindbody, Glofox,
Wodify, PushPress, etc. all have multiple wrappers), but the green industry
is wide open.
The same MCP works across the SingleOps and Granum family because Granum (acquired SingleOps) and LMN share infrastructure. Tools that help an arborist or lawn-care owner get a lead into the system in 30 seconds from their phone or browser are an obvious fit for AI agents.
Related MCP server: Jobber MCP Server
What you can do with it
You: "What divisions does our account have?"
Claude: *calls list_operations, returns Maintenance / Install / Irrigation*
You: "Did we already quote Jane Doe? Her email is jane@example.com."
Claude: *calls search_clients_by_email, finds client_id 42*
You: "Create a new lead for client 42 in the Maintenance division for a backyard cleanup."
Claude: *calls create_lead_for_existing_client, returns the new lead id*
You: "New lead from a phone call — John Smith at 555-123-4567, wants irrigation estimate."
Claude: *calls create_lead_with_new_client with the new client details*Install
pip install -e ".[dev]"Configure
SingleOps uses an user_email + user_token pair (NOT a bearer token).
Contact support@singleops.com to provision an API user on your account.
API access is gated to the MAX plan (the doc explicitly states: "API
access may not be available on all pricing tiers").
export SINGLEOPS_USER_EMAIL="api+youraccount@singleops.example.com"
export SINGLEOPS_USER_TOKEN="<secret-token-issued-by-singleops-support>"Use with Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"singleops": {
"command": "singleops_mcp",
"env": {
"SINGLEOPS_USER_EMAIL": "api+youraccount@singleops.example.com",
"SINGLEOPS_USER_TOKEN": "<your-token>"
}
}
}
}Tools
Tool | Purpose |
| Verify the credentials work. If this fails, all other tools will too. |
| List the divisions configured in your account (e.g. Maintenance, Install, Irrigation). |
| List the per-account custom fields that augment the default lead/job/client schema. |
| Find clients by email (prefix match, up to 50 per page). |
| Find clients by phone (prefix match, up to 50 per page). |
| Create a lead attached to an existing client record. |
| Create a new client + lead in a single call. |
API surface
SingleOps's public REST API is at https://app.singleops.com/api/v1/. The
MCP wraps:
GET /operations— list divisionsGET /custom_inputs— list custom field definitionsGET /clients/search_by_field?search_field=email|phone&search_term=...&page=...— search clientsPOST /jobs— create a new lead (either for an existing client or with a new client profile)
Engineering
33 tests via
respx+hypothesis, 0% live API callsruff(full rule set) +mypy --strict+ruff-formatall cleanTyped exception hierarchy (
SingleopsAuthError,SingleopsNotFoundError,SingleopsRateLimitError,SingleopsAPIError,SingleopsConnectionError)isError-compliance: tools
raise(not return) on failure, so FastMCP setsisError: trueon the wire (per the Blackwell MCP security audit)JSONL audit logging per tool call with secret redaction (
user_token,email,phone,mobileall stripped)Retry with exponential backoff + full jitter, honoring
Retry-After
License
MIT — see LICENSE.
Available Tools
7 toolscreate_lead_for_existing_clientA
Create a lead (Job) for an existing client already in SingleOps.
Use after search_clients_by_email / search_clients_by_phone to
attach a new lead to an existing client record. The lead moves
through the SingleOps Job workflow (Lead -> Proposal -> Schedule ->
Complete -> Invoice).
client_id is the SingleOps client.id (NOT email, NOT name). Look it
up with one of the search tools first.
operation_id is the SingleOps operation.id for the division the work
belongs to (look it up with list_operations).
visit_stage_id defaults to 8 (the standard "Lead" stage) but can be
set to whatever stage IDs your account has configured.
Inputs: client_id (required), operation_id (required), name, tags, +3 more. Returns: result
create_lead_with_new_clientA
Create a lead (Job) for a brand-new client, in a single call.
Use this when the prospect is NOT yet in SingleOps. The new client profile is created under the "portal_lead" object inside the same request — the lead is attached to that new client automatically.
At minimum pass first_name + last_name. Providing email or phone is strongly recommended so SingleOps can later deduplicate if the same person contacts you again.
Inputs: last_name (required), first_name (required), operation_id (required), name, +14 more. Returns: result
health_checkA
Verify credentials work. If this fails, all other tools will too.
Hits /operations as a low-cost liveness probe (a single small GET that exercises the auth + network path).
Inputs: no named parameters. Returns: result
list_custom_inputsA
List custom input fields configured for the account.
Custom inputs are per-account fields that augment the default lead/job/ client/item schema — e.g. "Lead Source", "Property Acreage", "Service Tier". Each entry has a key, label, type, and the entity it applies to. Cache this list; the lead-creation endpoint accepts custom field values keyed by the custom input's key.
Inputs: no named parameters. Returns: result
list_operationsA
List operations (divisions) configured in the account.
Operations are the divisions a green-industry business runs under — e.g. "Maintenance", "Install", "Irrigation", "Tree Care", "Snow". Each lead (Job) must be assigned to exactly one operation, so this list is the entry point for any lead-creation flow.
Returns the list of operation objects with id, name, and any division- specific metadata the account has configured.
Inputs: no named parameters. Returns: result
search_clients_by_emailA
Find clients by email address (prefix match, up to 50 per page).
Use this before creating a lead to check whether the prospect already
exists in the SingleOps account. Returns 0-50 matching clients;
paginate with the page parameter when the count approaches 50.
Common pattern: search the prospect's email; if found, reuse
client_id when creating the lead instead of supplying a portal_lead
block.
Inputs: email (required), page. Returns: result
search_clients_by_phoneA
Find clients by phone number (prefix match, up to 50 per page).
Use this when a prospect's email is unknown (e.g. a phone call comes in) to find their existing record before creating a new lead. Sometimes clients have multiple phone numbers or extensions, so the prefix match lets the search catch those variations.
Inputs: phone (required), page. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: two lead creation variants for existing vs. new clients, two search methods by email/phone, two list tools for operations and custom inputs, plus a health check. No overlap or ambiguity.
Most tools follow a verb_noun snake_case pattern (create_lead_, search_clients_, list_). 'health_check' deviates as noun_noun but is a standard term. Overall consistent and predictable.
Seven tools is well-scoped for a focused CRM server covering lead creation, client lookup, and account configuration. It's neither too few nor too many.
The set covers lead creation and client search but lacks tools to update, delete, or list leads, and no tool to get lead details. Agents cannot manage leads beyond creation, which is a significant gap for a lead-management system.
Related MCP Connectors
Search clients, list operations and custom inputs; create leads in SingleOps.
Run a field-service business from chat: schedule, jobs, customers, invoices and expenses.
Run a service business from your assistant: appointments, clients, invoices, calls and tasks.
Run a service business from your AI agent: CRM, leads, scheduling, invoicing, jobs and more.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides AI assistants with direct access to ServiceTitan's field service management platform for home services contractors. It enables users to manage customers, jobs, appointments, technician dispatching, and invoices through natural language.1MIT
- AlicenseAqualityFmaintenanceEnables AI assistants to access and manage Jobber field-service data including clients, jobs, invoices, and quotes through natural language interactions.679 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables querying and managing a CRM database through natural language conversations with Claude Desktop.-
- AlicenseBqualityDmaintenanceConnects AI assistants to Housecall Pro to look up and manage customers, jobs, invoices, and more through natural language. Operates in read-only mode by default with optional write capabilities.301MIT