Integration

Acquibee integration

Acquibee is a German sales CRM for canvassing and acquisition. Read, create, update, archive and delete clients (contact and company data, canvass status, sales probability, custom fields, campaign, project group and lead membership) and read their comments, follow-ups, deals, leads and project groups; read, create, edit and delete comments; read and delete campaigns, leads, deals, follow-ups and project groups and rename project groups; create, read and delete activity statistic reports (optionally emailed), read and delete cyclic report requests, and list each resource's fields. Not exposed: creating campaigns, leads, deals, follow-ups, project groups and cyclic report requests (their answer is a bare numeric id this platform cannot read) and the exists checks (HEAD). Answers carry personal data of contacts (names, emails, phones, birthdays). Authentication is an API token sent in the X-ACQUIBEE-TOKEN header, generated in the Acquibee app (Erzeugen API Token).

Connect Acquibee How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Acquibee

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.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

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

Client, 6 operations

archive_clientArchive clientDELETEAgents: ask firstArchives a client (the vendor's route for archiving; it answers like a delete, HTTP 204 with no body).
create_clientCreate clientPOSTAgents: ask firstCreates a client (contact) in Acquibee. Every field is optional. Returns Location, the full link to the new client; the numeric ID in the answer body cannot be read here (list_clients with getModifiedSince finds the new client).
delete_clientDelete clientDELETEAgents: ask firstPermanently deletes a client. To keep it out of the way without deleting it, use archive_client instead.
get_clientGet clientGETAgents: ask firstReturns one client by ID: contact and company data, address, canvass status, probability, custom fields and the IDs of its campaigns, leads, project groups, comments, follow-ups and deals.
list_clientsList clientsGETAgents: ask firstLists clients (contacts with company, address, canvass status, probability, custom fields and linked campaign, lead, project group, comment, follow-up and deal IDs). Filter by IDs or change time; page with limit and page.
update_clientUpdate clientPATCHAgents: ask firstUpdates a client: only the fields you send change. For campaigns, project groups or leads, read get_client first and send the full list of IDs you want. Answers with no body.

Comment, 5 operations

create_commentCreate commentPOSTAgents: ask firstAdds a comment (a note, email, meeting or call entry) to a client, visible on the client's page. Returns Location, the link to that client; the new comment's ID is not returned (list_client_comments finds it).
delete_commentDelete commentDELETEAgents: ask firstPermanently deletes a comment.
get_commentGet commentGETAgents: ask firstReturns one comment by ID: type, text, client, author, marked and private flags and dates.
list_commentsList commentsGETAgents: ask firstLists comments (notes, emails, meetings, calls and system entries) with type, text, author and client. Filter by comment IDs, client IDs or change time; page with limit and page.
update_commentUpdate commentPATCHAgents: ask firstEdits a comment: its text and its marked and private flags; only the fields you send change. Answers with no body.

Project group, 4 operations

delete_project_groupDelete project groupDELETEAgents: ask firstPermanently deletes a project group.
get_project_groupGet project groupGETAgents: ask firstReturns one project group by ID: name, member client IDs and dates.
list_project_groupsList project groupsGETAgents: ask firstLists project groups with name, member client IDs and dates. Filter by IDs or change time; page with limit and page.
update_project_groupUpdate project groupPATCHAgents: ask firstRenames a project group. Answers with no body.

Statistic report, 4 operations

create_statistic_reportCreate statistic reportPOSTAgents: ask firstCreates activity statistic reports for clients, project groups, campaigns or leads over a period, and EMAILS them when send_email is true. Returns the main report ID and the group's report IDs.
delete_statistic_reportDelete statistic reportDELETEAgents: ask firstPermanently deletes a statistic report.
get_statistic_reportGet statistic reportGETAgents: ask firstReturns one statistic report by ID: its settings and the activity counts of the period (calls, canvass statuses, meetings, newsletter data, per project group, campaign or lead).
list_statistic_reportsList statistic reportsGETAgents: ask firstLists activity statistic reports with type, period and what each covers. Filter by IDs, type or creation time; page with limit and page. Read one with get_statistic_report.

Campaign, 3 operations

delete_campaignDelete campaignDELETEAgents: ask firstPermanently deletes a campaign.
get_campaignGet campaignGETAgents: ask firstReturns one campaign by ID: name, type (marketing or telemarketing), member client IDs and change time.
list_campaignsList campaignsGETAgents: ask firstLists campaigns with name, type (marketing or telemarketing), member client IDs and change time. Filter by IDs or change time; page with limit and page.

Cyclic report request, 3 operations

delete_cyclic_report_requestDelete cyclic report requestDELETEAgents: ask firstPermanently deletes a cyclic report request, which stops its recurring reports.
get_cyclic_report_requestGet cyclic report requestGETAgents: ask firstReturns one cyclic report request by ID: type, period, counted days, holiday calendars, attachment formats, recipient emails and what it covers.
list_cyclic_report_requestsList cyclic report requestsGETAgents: ask firstLists cyclic (recurring) statistic report requests with type and what each covers. Filter by IDs, type or creation time; page with limit and page.

Deal, 3 operations

delete_dealDelete dealDELETEAgents: ask firstPermanently deletes a deal.
get_dealGet dealGETAgents: ask firstReturns one deal by ID: client, closing amount, estimated value, probability, forecast and change time.
list_dealsList dealsGETAgents: ask firstLists deals with client, closing amount, estimated value, probability and forecast. Filter by IDs or change time; page with limit and page.

Follow up, 3 operations

delete_follow_upDelete follow upDELETEAgents: ask firstPermanently deletes a follow-up.
get_follow_upGet follow upGETAgents: ask firstReturns one follow-up by ID: client, assigned user, scheduled time and change time.
list_follow_upsList follow upsGETAgents: ask firstLists follow-ups with client, assigned user and scheduled time. Filter by IDs or change time; page with limit and page.

Lead, 3 operations

delete_leadDelete leadDELETEAgents: ask firstPermanently deletes a lead.
get_leadGet leadGETAgents: ask firstReturns one lead by ID: name, member client IDs and change time.
list_leadsList leadsGETAgents: ask firstLists leads with name, member client IDs and change time. Filter by IDs or change time; page with limit and page.

Campaign field, 1 operation

list_campaign_fieldsList campaign fieldsGETAgents: ask firstLists the campaign fields: each field's name and type, whether the create route accepts it. Use the names in the fields parameter of the list tools.

Client comment, 1 operation

list_client_commentsList client commentsGETAgents: ask firstLists the comments (notes, emails, meetings, calls and system entries) of one client, by client ID, with type, text, author and dates.

Client deal, 1 operation

list_client_dealsList client dealsGETAgents: ask firstLists the deals of one client, by client ID, with closing amount, estimated value, probability and forecast.

Client field, 1 operation

list_client_fieldsList client fieldsGETAgents: ask firstLists the client fields: each field's name and type, whether create_client accepts it and whether update_client does. Use the names in the fields parameter of the list tools.

Client follow up, 1 operation

list_client_follow_upsList client follow upsGETAgents: ask firstLists the follow-ups scheduled for one client, by client ID, with the assigned user and scheduled time.

Client lead, 1 operation

list_client_leadsList client leadsGETAgents: ask firstLists the leads one client belongs to, by client ID, with each lead's name and client IDs.

Client project group, 1 operation

list_client_project_groupsList client project groupsGETAgents: ask firstLists the project groups one client belongs to, by client ID, with each group's name, dates and client IDs.

Comment field, 1 operation

list_comment_fieldsList comment fieldsGETAgents: ask firstLists the comment fields: each field's name and type, whether create_comment accepts it and whether update_comment does. Use the names in the fields parameter of the list tools.

Cyclic report request detail field, 1 operation

list_cyclic_report_request_detail_fieldsList cyclic report request detail fieldsGETAgents: ask firstLists the cyclic report request detail fields: each field's name and type, whether the create route accepts it. Use the names in the fields parameter of the list tools.

Cyclic report request field, 1 operation

list_cyclic_report_request_fieldsList cyclic report request fieldsGETAgents: ask firstLists the cyclic report request fields: each field's name and type, whether the create route accepts it. Use the names in the fields parameter of the list tools.

Deal field, 1 operation

list_deal_fieldsList deal fieldsGETAgents: ask firstLists the deal fields: each field's name and type, whether the create route accepts it. Use the names in the fields parameter of the list tools.

Follow up field, 1 operation

list_follow_up_fieldsList follow up fieldsGETAgents: ask firstLists the follow-up fields: each field's name and type, whether the create route accepts it. Use the names in the fields parameter of the list tools.

Lead field, 1 operation

list_lead_fieldsList lead fieldsGETAgents: ask firstLists the lead fields: each field's name and type, whether the create route accepts it. Use the names in the fields parameter of the list tools.

Project group field, 1 operation

list_project_group_fieldsList project group fieldsGETAgents: ask firstLists the project group fields: each field's name and type, whether the create route accepts it and whether update_project_group does. Use the names in the fields parameter of the list tools.

Statistic report detail field, 1 operation

list_statistic_report_detail_fieldsList statistic report detail fieldsGETAgents: ask firstLists the statistic report detail fields: each field's name and type, whether create_statistic_report accepts it. Use the names in the fields parameter of the list tools.

Statistic report field, 1 operation

list_statistic_report_fieldsList statistic report fieldsGETAgents: ask firstLists the statistic report fields: each field's name and type, whether create_statistic_report accepts it. Use the names in the fields parameter of the list tools.

User, 1 operation

get_meGet meGETAgents: ask firstReturns the user the API token belongs to: ID, name, email, phone, address, company, plan, team ID and team role. Use the ID as user_id when assigning clients.

Use Acquibee from Claude Code, Cursor or Codex

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

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