Skip to content
ClaraConverts logo

ClaraConverts MCP server

Which servers in the official MCP registry are ClaraConverts's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-20

← Back to ClaraConverts

Whose server it is
  • Registry namecom.claraconverts/claraverified in the MCP registry

The registry name sits under claraconverts.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-20
  • Stateanswerschecked 2026-10-20
  • Tools11
  • Server calls itselfclara-provisioning-mcp
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-20 the server answered initialize and tools/list without a sign-in. First answer in 39 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 3 of the 7 days it takes to judge reliability.

Once connected

  • create_trial_tenant, update_tenant_settings, set_site_knowledge change data without a sign-in: anyone with the address can call them.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 3, the first on 2026-10-20
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
  • Answeredmeasuring3 of the 7 daily checks it takes to print a share
  • Median first answer268 ms
  • Space in an agent's context≈ 2,382 tokensthe definitions of all its tools (11), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 11 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • not sure · answer visitor questions and book appointments on a website
  • not sure · route new website leads into a CRM
  • not sure · recommend products and build shopping carts for visitors

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

  • Tools that change data, on a server that answers without a sign-in: create_trial_tenant, update_tenant_settings, set_site_knowledge

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers11 tools · read 2026-10-20
  • get_pricing

    Get ClaraConverts pricing: the free 30-day trial (no card, every Pro feature — start it with create_trial_tenant) and the paid plans (Standard, Pro, Volume) in USD/month.

  • list_integrations

    List the CRM, booking, commerce, payments, and other integrations ClaraConverts can connect to.

  • create_trial_tenant

    Create a free, no-card ClaraConverts trial for a website, with every Pro feature (voice replies included). Returns a working embed snippet and a bearer token for follow-up calls (get_embed_snippet, get_upgrade_link). Trial lasts 30 days…

  • get_embed_snippet

    Get the <script> embed snippet for your trial tenant. Requires the secret_key from create_trial_tenant, either as the secret_key argument or an "Authorization: Bearer <secret_key>" header.

  • get_tenant_settings

    Read back your trial tenant's current persona/widget settings and which integrations are connected — the read counterpart to update_tenant_settings and configure_integration, useful for confirming a change actually took or resuming work…

  • update_tenant_settings

    Update your trial tenant's persona and widget settings (name, goal, branding, position, lead notification email). Only the fields you pass are changed. Requires the secret_key from create_trial_tenant, either as the secret_key argument or…

  • refresh_site_knowledge

    Re-crawl your site and update what Clara knows about it. Trials skip the crawl at creation to stay fast, so Clara knows nothing about your business until this runs at least once. Can take up to a minute for a large site. Requires the…

  • set_site_knowledge

    Give Clara the site's content directly, for a site that isn't published yet (localhost, a preview URL, or still being built) so you can test Clara answering real questions before launch. Pass each page's text, markdown, or HTML. Replaces…

  • list_calcom_event_types

    List the meeting types on a Cal.com account by name (with account timezone). Call this BEFORE configure_integration with provider="calcom" — its required event_type_id can't be typed from memory, it has to be picked from this list…

  • configure_integration

    Connect an integration from list_integrations to your trial tenant. For API-key providers, pass api_key and any required config fields and it connects immediately (Cal.com needs list_calcom_event_types called first for event_type_id…

  • get_upgrade_link

    Get a Stripe Checkout link to keep Clara after the trial — Pro by default, the plan every trial runs on. Requires the secret_key from create_trial_tenant, either as the secret_key argument or an "Authorization: Bearer <secret_key>" header.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "clara": {
      "type": "http",
      "url": "https://claraconverts.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http claraconverts https://claraconverts.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://claraconverts.com/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.