Search clients, list operations and custom inputs; create leads in SingleOps. For lawn and tree care companies that capture leads in SingleOps. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"singleops": {
"url": "https://singleops.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"singleops": {
"type": "http",
"url": "https://singleops.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
Search the clients by email or phone number before you add a new lead.
singleops_search_clients
Add a new lead with the contact details, the division and the custom inputs.
Changes data · singleops_list_operations singleops_list_custom_inputs singleops_create_lead
List the operations (divisions) and the custom inputs that a lead can use.
singleops_list_operations singleops_list_custom_inputs
The login page asks for your API user email and API token.
Email [email protected] to get an API user for your account (no extra cost). You receive an email address and a token. The token only allows lead entry. It is used only to call the API for you and is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your API user email and API token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the SingleOps connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
singleops_list_operations | read | List operations (divisions) List the operations (divisions) of the SingleOps account. A lead needs an operation `id` from this list. Read-only. |
singleops_list_custom_inputs | read | List custom inputs List the custom input fields of the account (for example a 'Lead Source' field). Use the `id` as `custom_input_id` when you create a lead. Read-only. |
singleops_search_clients | read | Search clients by email or phone Search existing clients by email or phone (prefix match, up to 50 results per page). Search first, then pass the client `id` to singleops_create_lead to avoid a duplicate client. Read-only. |
singleops_create_lead | write | Create a lead WRITE: create a new lead in SingleOps (stage Lead). Not idempotent: each call creates a new lead, so do not repeat it. Needs `operation_id` (singleops_list_operations) and either `client_id` (singleops_search_clients) or client details in `portal_lead`. A person must confirm the lead in SingleOps before it counts as valid. Optionally creates a task with it. |
singleops_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
singleops_request_feature | Request a missing feature Tell usefulapi that the user needs something the SingleOps tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
singleops_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on SingleOps (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
singleops_cancel_subscription | Cancel the Pro subscription Cancel the caller's SingleOps Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run singleops_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this SingleOps server only. Subscribe with singleops_upgrade (it returns a Stripe Checkout link). Cancel any time with singleops_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running singleops_upgrade before then undoes the cancel. Or write to [email protected].
Check if a client already exists. Create a lead from a call or email. Look up the divisions and custom inputs. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by SingleOps. The server calls the SingleOps API with your own SingleOps access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your API user email and API token. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your API user email and API token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the SingleOps API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in SingleOps.
Yes, if you approve it. 1 of the 4 SingleOps tools can create or change data. The other 3 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this SingleOps server only. Cancel any time: Pro then runs to the end of the paid period. Run singleops_usage_status to see how many calls you used.
Ask the AI to run singleops_upgrade: it returns a Stripe Checkout link. To cancel, run singleops_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with singleops_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.