Integration

Agrello integration

Agrello is an electronic signature and document automation platform. Organize documents in folders, create reusable templates with variables, create signing containers from a template, invite signers and viewers, read a container's status and signatures, get invitation share links, and manage webhooks for signing events (DOCUMENT_SIGNED, DOCUMENT_SIGNATURE_ADDED, REMINDER_CREATED). Authentication is OAuth 2.0 client credentials: the client id and secret are exchanged for a Bearer token valid 24 hours.

Connect Agrello How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Agrello

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.

Folder, 5 operations

create_folderCreate folderPOSTCreates a top-level folder and returns its id.
create_sub_folderCreate sub folderPOSTCreates a sub-folder inside a folder and returns its id.
delete_folderDelete folderDELETEDeletes a folder by id.
list_foldersList foldersGETLists the folders of the workspace, paged (page from 0, size up to 500).
list_sub_foldersList sub foldersGETLists the sub-folders of a folder.

Container, 4 operations

create_containerCreate containerPOSTCreates a signing container in a folder, from an uploaded file or from a template (templateId). By default it is published at once and invitations are emailed; set immediatePublish false to keep it unsent.
delete_containerDelete containerDELETEDeletes a container by id.
get_containerGet containerGETReturns a container by id: status, files, parties, invitations and collected signatures. Compare signatures with the expected signers to check completion.
list_folder_containersList folder containersGETLists the containers in a folder, paged (page from 0, size up to 500), each with its id and status.

Template, 4 operations

create_templateCreate templatePOSTUploads a document file as a new template in a folder. Returns the template with its id and the variables found in it, for create_container's templateId and variables.
delete_templateDelete templateDELETEDeletes a template by id.
get_templateGet templateGETReturns a template by id, with its variables (the names create_container fills).
list_folder_templatesList folder templatesGETLists the templates in a folder, optionally only one templateType.

Webhook, 4 operations

create_webhookCreate webhookPOSTRegisters a webhook: Agrello calls url when event (DOCUMENT_SIGNATURE_ADDED, DOCUMENT_SIGNED or REMINDER_CREATED) happens.
delete_webhookDelete webhookDELETEDeletes a webhook by id.
get_webhookGet webhookGETReturns a webhook by id.
list_webhooksList webhooksGETLists the webhooks registered for these credentials, each with its event and callback url.

Invitation, 1 operation

add_container_invitationsAdd container invitationsPOSTEmails signing or viewing invitations to the listed people for a container. Listing someone already added resends their invitation.

Output, 1 operation

download_container_outputDownload container outputGETDownloads the signed output file of a container that has signatures, in the container's outputType (PDF, ASICE, EDOC, ADOC_B or ZIP).

Url, 1 operation

get_container_invitation_linksGet container invitation linksGETReturns each sent-out invitation's latest share link in `links`, its `url` plus `expiresAt`, regardless of whether that link is still live.

Workspace, 1 operation

get_workspaceGet workspaceGETReturns the workspace these API credentials belong to (id and name).

Use Agrello from Claude Code, Cursor or Codex

Connect Agrello in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Agrello 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 Agrello

Create your workspace
Sign up free. Nothing to install.
Connect Agrello once
Add your Agrello 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.