Integration

Crove integration

Crove automates document paperwork from templates. List templates and read their field and role names, create a document from a template with values keyed by field name, update those values, send it to recipients to fill or sign (or get a link without email), or complete it yourself; then export it as PDF, DOCX or an audit-trail PDF and read the export job for its 15-minute download link. Also list and read documents, and manage outgoing webhooks and their deliveries. Rotating a webhook secret is not exposed. Authentication is a workspace API key (Settings, API keys) sent in the X-Api-Key header; a plan without API access answers 403 quota_required.

Connect Crove How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Crove.Built from the 19 Crove tools below, on the connection you add once.

What you can do with Crove

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Webhook, 5 operations

create_webhookCreate webhookPOSTCreate an outgoing webhook. Deliveries carry an X-Crove-Signature, but the signing secret is not passed back here, so they cannot be verified from this connection.
delete_webhookDelete webhookDELETEDelete one outgoing webhook endpoint.
get_webhookGet webhookGETFetch one webhook endpoint.
list_webhooksList webhooksGETList workspace-level outgoing webhook endpoints.
update_webhookUpdate webhookPATCHUpdate the URL, active flag, event list, or description.

Document, 3 operations

create_documentCreate documentPOSTCreate a document from a template and optionally prefill named values.
get_documentGet documentGETReturn current document status and values.
list_documentsList documentsGETList documents in the active workspace. Results never cross workspace boundaries. Filters AND-combine.

Export, 2 operations

create_document_exportCreate document exportPOSTStarts an export of a document as pdf (sealed when sign is true, the default), docx or audit_trail_pdf. Returns a job_id: read get_export until status is done, then use its signed_download_url (valid 15 minutes).
get_exportGet exportGETReturns an export job. When status is done, signed_download_url is a download link valid for 15 minutes; format echoes the requested type (pdf, docx or audit_trail_pdf).

Template, 2 operations

get_templateGet templateGETFetch field and role names for one template. Values are submitted by field name, not field id.
list_templatesList templatesGETList reusable templates in the credential's workspace. Use a template id to create documents.

Delivery, 1 operation

list_webhook_deliveriesList webhook deliveriesGETInspect recent delivery attempts for one webhook endpoint.

Me, 1 operation

get_workspaceGet workspaceGETConfirm the credential and return the workspace bound to the API key or OAuth token.

Redeliver, 1 operation

redeliver_webhook_deliveryRedeliver webhook deliveryPOSTQueue a new attempt for a previous webhook delivery.

Send, 1 operation

send_documentSend documentPOSTInvite recipients to fill or sign. Set notify to false to create and return a link without sending email.

Submit, 1 operation

submit_documentSubmit documentPOSTCompletes a document yourself, with no recipient and no email. Every sender-only required field must already be set (create_document or update_document_values). Fires document.completed; export it afterwards with create_document_export.

Test, 1 operation

send_test_webhookSend test webhookPOSTSend a test event to verify delivery and signature handling.

Value, 1 operation

update_document_valuesUpdate document valuesPATCHPartially update named field values. Existing values not included in the request are preserved.

Use Crove from Claude Code, Cursor or Codex

Connect Crove in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Crove operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Crove

Create your workspace
Sign up free. Nothing to install.
Connect Crove once
Add your Crove connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.