ServiceTrade MCP by usefulapi
Server Details
Read jobs, appointments, deficiencies, invoices and assets, and add comments in ServiceTrade.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 22 tools
Each tool pairs a single verb (get/list/add) with a single, clearly named ServiceTrade entity, so there is no realistic confusion between e.g. get_job and list_jobs or get_asset and list_assets. The one generic tool (list_comments, which takes an entity-type number) is still clearly scoped by its description and does not overlap any other tool's purpose.
Every tool uses the same servicetrade_<verb>_<noun> snake_case convention with a stable verb set (get_, list_, add_), and entity nouns match the API resource names. No camelCase or verb-style mixing anywhere in the set.
22 tools is on the heavy side, but it is a systematic product of ~10 entities each needing list and/or get rather than ad-hoc sprawl, so nearly every tool earns its place. Minor bloat comes from the asymmetry (contracts and service requests get only a list, while others get both), which slightly inflates the surface without adding confusion.
The surface is overwhelmingly read-only: 20 of 22 tools are get/list, with a single write (add_comment) and a whoami, so an agent cannot create, update, close, or delete jobs, invoices, quotes, deficiencies, assets, or appointments. There are also structural gaps such as no get_contract or get_service_request to complement those lists, and no search/filter helper beyond list parameters, which will cause dead ends for most non-trivial workflows.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Read work orders, invoices and customers; add leads, tasks and notes in ServiceBridge.
Read customers, equipment and service requests; add service requests and comments in BlueFolder.
Read ServiceMonster customers, jobs, orders and schedules, and add customer notes.
Read FieldPulse customers, jobs, estimates, invoices, assets and projects; create and update jobs.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables LLMs to query ServiceChannel work orders, locations, and provider assignments through typed, read-only tool calls instead of raw API requests.1MIT
- AlicenseAqualityBmaintenanceEnables AI agents to read and change jobs, job status, customers, quotes with line items, invoices, quote and invoice email, payments, and Scheduler bookings in an account by reusing the user's own signed-in Chrome session, with no official API keys needed. Ships read-only hints and confirmation prompts for tools that reach other people, and can be run over stdio or streamable HTTP.22255 PyPI6Elastic 2.0
- AlicenseAqualityBmaintenanceEnables AI assistants to read field-service business data through a read-only MCP integration, including jobs, invoices, quotes, schedules, clients, and draft client messages. It handles authentication, token refresh, throttling, schema versioning, and account-currency formatting for live Jobber accounts.7MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage jobs, schedules, estimates, invoices, routes, and client records in a connected service-business account through MCP or REST.Elastic 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.