These are the official developer resources for Clara, the AI receptionist from heyitsclara.com. AI assistants and agents connect to a Clara account through one MCP endpoint, OAuth 2.1, and a documented set of read and write tools.
Clara has no public REST API. The supported way to work with a Clara account programmatically is the Clara MCP server, which speaks the Model Context Protocol.
| Endpoint | https://mcp.heyitsclara.com/mcp |
|---|---|
| Transport | Streamable HTTP (Model Context Protocol) |
| Protocol revision | 2025-06-18 |
| Health and live tool list | https://mcp.heyitsclara.com/health |
| Included with | Clara Pro |
In an MCP client, add Clara as a custom connector and paste the endpoint. Step-by-step guides: Claude, ChatGPT.
Clara uses OAuth 2.1 with PKCE. Clara is both the protected resource and its own authorization server, and it registers clients dynamically, so there is no app to register by hand and no client secret to store. People sign in with the Clara account they already use and approve the connection before a token is issued.
| Issuer | https://mcp.heyitsclara.com |
|---|---|
| Authorization endpoint | https://mcp.heyitsclara.com/authorize |
| Token endpoint | https://mcp.heyitsclara.com/token |
| Dynamic client registration | https://mcp.heyitsclara.com/register |
| Grant types | authorization_code, refresh_token |
| PKCE | S256 (required) |
| Client authentication | none (public clients) |
| Authorization server metadata | https://mcp.heyitsclara.com/.well-known/oauth-authorization-server |
| Protected resource metadata | https://mcp.heyitsclara.com/.well-known/oauth-protected-resource |
An unauthenticated request answers 401 with a WWW-Authenticate: Bearer resource_metadata=… challenge pointing at the protected resource metadata, so a client can discover the authorization server from the resource itself (RFC 9728).
| Identity | Every request carries the individual Clara user's own credential. There is no cross-tenant key and no shared service account. |
|---|---|
| Tenancy | A connection can only reach the businesses on the account that authorized it. Clara's backend enforces tenancy on every call, not the MCP layer. |
| Confirmation | Write tools change a live receptionist, so MCP clients ask the person to confirm each call before it runs. |
| Revocation | Access ends when the person disconnects Clara in their assistant or revokes the connection from the Clara web app. Nothing keeps working on its own afterwards. |
| Rate limits | Per-user rate limits, a global concurrency cap, request timeouts, and a circuit breaker protect the Clara backend behind the MCP server. |
| Scopes | No OAuth scope vocabulary is issued yet, so a client cannot currently request read-only access at the token level. Least-privilege today means connecting only the account that needs it and confirming writes. |
14 read tools and 17 write tools. Read tools never change Clara data. Write tools change a live receptionist or send a message on the account's behalf, and MCP clients confirm each one with the person before calling it.
| Tool | What it does |
|---|---|
get_account | The signed-in Clara account |
list_businesses | Businesses on the account |
get_business | One business and its receptionist setup |
list_inquiries | Inquiries captured from calls and texts |
get_inquiry | One inquiry in full |
list_calls | Answered calls with summaries |
get_call_statistics | Call volume and outcome totals |
list_customers | Callers Clara has spoken to |
get_customer | One customer and their history |
get_recording | A call recording and transcript |
search | Search across calls, messages, and customers |
list_voices | Voices the receptionist can use |
preview_receptionist_voice | Hear a voice before switching |
list_receptionist_rules | Instructions, follow-ups, transfer rules |
| Tool | What it does |
|---|---|
update_business | Edit business details |
update_receptionist | Edit greeting, voice, and intake fields |
update_customer | Edit a customer record |
mark_inquiry_read | Mark an inquiry read |
set_inquiry_status | Change an inquiry status |
add_special_instruction | Add a receptionist instruction |
update_special_instruction | Edit a receptionist instruction |
remove_special_instruction | Delete a receptionist instruction |
add_followup_text | Add an automated follow-up text |
update_followup_text | Edit an automated follow-up text |
remove_followup_text | Delete an automated follow-up text |
test_followup_text | Send yourself a test follow-up text |
add_transfer_rule | Add a live call transfer rule |
update_transfer_rule | Edit a live call transfer rule |
remove_transfer_rule | Delete a live call transfer rule |
reply_to_customer | Send a text reply to a customer |
mark_sms_read | Mark a text conversation read |
Locale-free paths are served by the Worker and negotiate content: send Accept: text/markdown to /, /pricing, /blog, /support/<article> and the other top-level sections, and Clara answers with markdown instead of HTML. Locale-prefixed pages (/us/…, /gb/…) are static files and always return HTML, so this page ships a markdown twin.
For anything about connecting an agent to Clara, email [email protected]. See also the integrations overview, the terms, and the privacy policy.
