MCP (AI Agents)
Connect Claude and other AI agents to Servicebay via the Model Context Protocol
Servicebay ships a remote MCP server so AI agents — Claude Code, Claude Desktop, or anything else that speaks the Model Context Protocol — can work with an organisation's jobs, customers, quotes, and invoices on a user's behalf.
Authentication is OAuth under the hood: the agent registers itself automatically, the user approves the connection on the standard consent screen (organisation + permissions), and every action the agent takes is checked against the granted scopes.
Connecting from Claude Code
claude mcp add --transport http servicebay https://oauth.servicebay.io/mcpThen run /mcp inside Claude Code to trigger sign-in. A browser window opens
on the Servicebay consent screen; pick the organisation, review the
permissions, and approve. That's it — the agent is connected.
Admins only
Only organisation admins can authorize an agent, and the connection is
bound to a single organisation. Grant read scopes only, unless you
genuinely want the agent creating and editing records.
Available tools
The MCP server exposes a compact toolset over the same REST API documented in the API Reference — identical validation, sequential ID allocation, and business rules.
| Tool | What it does |
|---|---|
get_organisation | The connected organisation's profile |
list_resources | List any resource type, with the REST API's query filters |
get_resource | Fetch one resource by ID |
create_resource | Create a resource (scoped :write required) |
update_resource | Update a resource by ID |
delete_resource | Delete a resource by ID |
lookup_customer | Find a customer by email or phone |
Resource types: tickets (jobs), customers, devices, services,
inventory, quotes, invoices, payments, calendar-events, stations,
tax-rates, ticket-statuses.
Managing and revoking access
Connected agents appear under Connected Apps in the developer portal, alongside regular OAuth apps. Revoking disconnects the agent within a few minutes.
For other MCP clients
Any MCP client that supports the streamable-HTTP transport with OAuth authorization works. The server advertises everything a client needs via standard discovery:
https://oauth.servicebay.io/.well-known/oauth-authorization-serverDynamic client registration (RFC 7591) is enabled, so clients self-register — no manual credential setup is required.