Integration

Offorte integration

Offorte is proposal software for sending, signing and tracking sales proposals. List proposals by status, read a proposal's full details (price tables, comments, emails, history), create one from a template, update, delete or send it to the client's contact people; manage organisation and person contacts and the people of an organisation, product directories and products, and webhooks; list users, proposal templates, design, email and text templates, tags, VAT groups and automation sets. Custom contact fields (custom_ keys) cannot be set through these tools. Authentication is an API key created in Offorte under Settings, API Integrations, sent as it is in the Authorization header, plus the account name (the subdomain of your Offorte address).

Connect Offorte How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Offorte

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.

Person, 6 operations

create_organisation_personCreate organisation personPOSTAdds a person to an organisation contact; that person can then receive proposals (give an email). Returns the created person with its id.
delete_organisation_personDelete organisation personDELETERemoves a person from an organisation contact.
get_organisation_personGet organisation personGETReturns one person of an organisation contact: name, salutation, address, phone, mobile, email and social links; record also carries the account's custom_ fields.
list_organisation_peopleList organisation peopleGETLists the people of an organisation contact, 50 per page, with name, address, phone, email and number of proposals. Tags and custom fields come only from get_organisation_person.
list_person_contactsList person contactsGETLists the main contacts of type person, 50 per page, with name, address, phone, email, organisation and proposal counts. Search by name with query. Tags and custom fields come only from get_contact.
update_organisation_personUpdate organisation personPATCHChanges a person of an organisation contact; only the fields sent change.

Webhook, 5 operations

create_webhookCreate webhookPOSTCreates a webhook (at most 10 per account) that posts the chosen events to an HTTPS URL; events default to all. A webhook is deactivated after 10 failed attempts.
delete_webhookDelete webhookDELETEDeletes a webhook, so its URL no longer receives events.
get_webhookGet webhookGETReturns one webhook: URL, content type, subscribed events, whether it is active, and when it was created, changed and last failed.
list_webhooksList webhooksGETLists the webhooks of the account (at most 10) with URL, subscribed events, whether each is active and when a delivery last failed.
update_webhookUpdate webhookPATCHChanges a webhook; only the fields sent change (URL, content type, events, active).

Contact, 4 operations

create_contactCreate contactPOSTCreates a main contact: an organisation (type organisation, with coc_number, vat_number, fax) or a private person (type person, with firstname, lastname, salutation, mobile). Returns the created contact with its id.
delete_contactDelete contactDELETEDeletes a main contact. It is moved to the trash can in Offorte and can be restored there by hand.
get_contactGet contactGETReturns one main contact with its address and social links, tags, owner, the people of an organisation and its proposals; record also carries the account's custom_ fields.
update_contactUpdate contactPATCHChanges a main contact; only the fields sent change. Organisations take coc_number, vat_number and fax; persons take firstname, lastname, salutation and mobile.

Directory, 4 operations

create_product_directoryCreate product directoryPOSTCreates a product directory with the given name.
delete_product_directoryDelete product directoryDELETEDeletes an empty product directory; the call fails while the directory still holds products.
list_product_directoriesList product directoriesGETLists the product directories (id and name); a directory id is what list_products and create_product take.
update_product_directoryUpdate product directoryPATCHRenames a product directory.

Product, 4 operations

create_productCreate productPOSTCreates a product in a product directory and returns its id. Products can then be used as rows of proposal price tables.
delete_productDelete productDELETEDeletes a product from its product directory.
list_productsList productsGETLists the products of a product directory with name, short description, SKU, price, VAT group, recurring period and whether the client may select them.
update_productUpdate productPATCHChanges a product; only the fields sent change. Answers true when the product was updated.

Proposal, 3 operations

create_proposalCreate proposalPOSTCreates a proposal from a proposal template for a contact and the contact people who will receive it. Price table rows and custom field values can be filled in. Returns the proposal id; send it with send_proposal.
delete_proposalDelete proposalDELETEDeletes a proposal. It is moved to the trash can in Offorte and can be restored there by hand.
list_proposal_templatesList proposal templatesGETLists the proposal templates (favorites) with their design, text template and automation set, and the custom fields each uses. A template id is what create_proposal takes as proposal_template_id.

Detail, 2 operations

get_proposalGet proposalGETReturns everything about one proposal: status, value and price tables, the contact and receivers, custom fields, comments and questions from the client, sent emails, acceptance form answers and the view and change history.
update_proposalUpdate proposalPATCHChanges a proposal's details; only the fields sent change. Set status to won, lost or closed to record the outcome, or change its name, value, owner, contact, receivers, templates, directory, tags or custom fields.

Design template, 1 operation

list_design_templatesList design templatesGETLists the design templates (id and name) a proposal can use.

Email template, 1 operation

list_email_templatesList email templatesGETLists the email templates (id and name); an id is what send_proposal takes as send_message_id.

Open, 1 operation

list_proposalsList proposalsGETLists proposals in one status (edit, open, won, lost or closed), 50 per page, with contact, value, number, dates and tags. With query it searches all proposals and ignores status. Sort by name (default) or a date.

Organisation, 1 operation

list_organisation_contactsList organisation contactsGETLists the main contacts of type organisation, 50 per page, with address, phone, email, owner and open and won proposal counts. Search by name with query. Tags and custom fields come only from get_contact.

Proposal directory, 1 operation

list_proposal_directoriesList proposal directoriesGETLists the proposal directories (folders) users created, grouped by proposal status: edit, open, won, lost and closed, each with id and name.

Send, 1 operation

send_proposalSend proposalPOSTSends a proposal to its receivers by email through Offorte, with a plain-text message or an email template; with send_method self nothing is emailed and you get each receiver's personal proposal link to send yourself.

Set, 1 operation

list_automation_setsList automation setsGETLists the automation sets of the account (id and name); pass an id as automations_set_id to create_proposal.

Tag, 1 operation

list_tagsList tagsGETLists the tags defined in the account (id and name).

Text template, 1 operation

list_text_templatesList text templatesGETLists the text (language) templates (id and name), for example English or Nederlands.

User, 1 operation

list_usersList usersGETLists the active users of the Offorte account with their id, name, email, phone, job title and last login. A user id is what create_proposal takes as account_user_id.

Vat group, 1 operation

list_vat_groupsList vat groupsGETLists the VAT groups with id, name, label and rate; an id is what products take as vat_id.

Use Offorte from Claude Code, Cursor or Codex

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

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