Clevra MCP server

Clevra runs a remote Model Context Protocol (MCP) server. Add it to any AI assistant that supports remote MCP servers, such as Claude or ChatGPT, and the assistant can work with your company's Clevra data: answer questions about your schedule, jobs, invoices and clients, and take a small set of everyday actions, such as drafting an estimate or booking a visit. The assistant always acts as you, with exactly the access your Clevra role gives you.

Using Claude? The Clevra for Claude page has step-by-step instructions for Claude.

Server details

Server URL	`https://app.clevra.ai/api/mcp`
Transport	Streamable HTTP, stateless. Requests are JSON-RPC over `POST`; there is no server-initiated stream and no session to keep.
Protocol versions	2025-11-25 (with the `initialize` handshake) and 2026-07-28.
Authentication	OAuth 2.1 authorization code flow with PKCE (S256). The person signs in with their usual Clevra login and approves access; the assistant receives a revocable access token and sends it in the `Authorization: Bearer` header. Tokens in the URL are refused.
Discovery	Protected Resource Metadata (RFC 9728) at `https://app.clevra.ai/.well-known/oauth-protected-resource/api/mcp`. It names the authorization server, whose own metadata lists the authorize, token and registration endpoints. Every 401 response points to it in its `WWW-Authenticate` header.
Client registration	Client ID Metadata Documents or Dynamic Client Registration. No API key or pre-shared secret is needed.
Scopes	None. What the assistant can see and do is decided by the person's Clevra role on every request.
Capabilities	Tools (`tools/list`, `tools/call`). Every tool declares a JSON Schema for its input and carries a title and read-only or write annotations.

What you need

A Clevra account with the Org Admin, Manager or Dispatcher role.
A Clevra plan that includes the AI assistant: Pro, Business or Custom (or an active trial).
An AI assistant or MCP client that supports remote MCP servers with OAuth sign-in.

Connect your assistant

In your assistant's settings, add a custom connector. Depending on the assistant it may be called a connector, an app, an integration or an MCP server.
Paste the server URL:
https://app.clevra.ai/api/mcpNo API key is needed. If the assistant asks for an authentication type, choose OAuth.
Sign in with your usual Clevra login and approve access on the consent screen.
That's it. Ask your first question.

You can check your connection at any time in Clevra under Settings → Connected apps. That page also shows the server URL and exactly what an assistant can and cannot do.

Tools

Read tools. These look things up, limited to what your role can see:

Tool	What it does
`list_clients`, `get_client`	Find clients and read a client's details
`list_client_notes`	Read the notes on a client
`get_client_billing_standing`	A client's outstanding and overdue balance
`list_jobs`, `get_job`	Find jobs and read a job, including its booked visits
`get_job_stats`	Job counts and totals
`get_job_profit`	A job's profit, only for roles that can see costing
`list_invoices`, `get_invoice`	Find invoices and read one
`list_quotes`, `get_quote`	Find estimates and read one
`list_requests`, `get_request`	Find service requests and read one
`get_schedule`	The schedule for a date range
`find_open_slots`	Free time for a team member in a date range
`list_activities`	Calls, emails, meetings and other logged activities
`list_team_members`	Your team list
Report tools	Run any report on the Reports hub your plan includes

Action tools. These are marked as write tools, so your assistant can ask you to confirm before each one runs:

Tool	What it does
`create_client`	Create a client
`add_client_note`	Add a note to a client
`create_activity`	Log an activity
`create_task`	Create a task
`create_quote_draft`	Draft an estimate. It stays a draft until you send it from Clevra.
`schedule_visit`	Book a visit. Booking sends your company's automatic messages, such as confirmations and reminders, exactly as booking it in Clevra does, so this tool is marked destructive.

Every action runs through the same rules as the Clevra app and is recorded in Clevra's audit trail as done through an AI assistant. Every record in an answer includes a link that opens it in Clevra.

What the server can't do. It never:

sends emails or texts on its own
takes or refunds payments
deletes anything
converts estimates into jobs
imports data
changes billing, payroll, team membership or company settings.

Do those in Clevra.

Try asking

"What's on the schedule tomorrow, and who is assigned to each visit?"
"Which invoices are overdue, and how much is outstanding in total?"
"Show me everything we've done for Acme Property Management this year."
"Find a two-hour slot for Maria next week and book the follow-up visit for the Oak Street job."
"Draft an estimate for Jane Smith: annual furnace service plus one filter replacement."
"Run last month's revenue report and tell me which services grew the most."

Permissions and privacy

Your role, nothing more. The assistant sees and does only what your Clevra role allows. Pay rates and costing are hidden from roles that can't see them in the app, and a role change takes effect on the next request.
Clevra doesn't receive your conversations. Clevra sees only the requests the assistant makes on your behalf. For each request it keeps an access record (which connection, which tool, the outcome and how long it took), never the content. Access records are deleted after 90 days.
What the assistant receives is handled by its provider. Data returned to your assistant is processed under your agreement with that assistant's provider. See our Privacy Policy.
Your password stays with Clevra. You sign in through Clevra's own sign-in page, and the assistant receives a revocable access token.

Controls for admins

In Clevra, under Settings → Connected apps, admins can:

see every connection in the company, and disconnect any of them;
turn Allow AI assistant connections off to pause every connection at once;
turn Allow actions through AI assistants off to keep every assistant read-only for the whole company.

Limits

Up to five active connections per person.
120 requests per minute per connection, and 3,000 requests per 10 minutes per company.
2,000 tool calls per connection and 10,000 per company each day, counted in your company's time zone.
Using the server doesn't count against your in-app AI assistant's monthly message allowance.

Disconnect or reconnect

Disconnect: in Clevra, go to Settings → Connected apps and select Disconnect. The assistant's next request is refused. You can also remove the connector in your assistant's settings.
Reconnect after disconnecting: in Settings → Connected apps, select Connect, then reconnect Clevra in your assistant within an hour.

Troubleshooting

What your assistant says	What to do
"Your role does not include the AI assistant connector"	Ask your admin to give you the Org Admin, Manager or Dispatcher role. No reconnect is needed.
"The AI assistant is not included in your company's plan"	An admin can change the plan in Settings → Billing. No reconnect is needed.
"AI assistant connections are paused"	An admin turned off Allow AI assistant connections in Settings → Connected apps.
"This connection was disconnected…"	In Clevra, press Connect in Settings → Connected apps, then connect Clevra again in your assistant.
"Connect Clevra to continue"	Sign in with your staff Clevra account. If you just pressed Connect in Clevra, press it again; each Connect request is valid for an hour.

Support

Questions or problems: hi@clevra.ai.