create_contact
Create a new contact (organisation or person/individual)
LABSCO SUMMARY
The template listings are the real interface here: create_proposal takes ids, so the ids have to be fetched before anything can be composed.
get_initial_context is a precondition the server declares for itself, and after it the path is fixed — find the contact, list the design, text, proposal and email templates, then call create_proposal with those ids and send_proposal to deliver. Nothing in this surface writes proposal body copy directly; the document's shape comes from templates you already maintain in Offorte, which keeps output consistent with house style and means the server cannot produce a proposal that has no corresponding template behind it.
What it is
The official Offorte server over an Offorte account, exposing contact search and creation, template and automation-set listings, proposal creation and sending, and a pipeline view of proposals by status.
What you get
- get_initial_context returns usage instructions and account context, and its description states it must be called before any other tool.
- Contact handling: search_contact_people and search_contact_organisations look people and organisations up by name, get_contact_details returns everything held against a contact_id, and create_contact adds an organisation or an individual with street, zipcode, city, state, country, email, phone, mobile, vat_number, coc_number, salutation, tags and linkedin, twitter, facebook and instagram handles.
- The template inventory that composition depends on: get_proposal_templates, get_design_templates, get_text_templates, get_email_templates and get_automation_sets each return the ids that create_proposal and send_proposal accept as input.
- create_proposal builds a proposal from contact_id, contact_people, account_user_id, proposal_template_id, design_template_id, text_template_id and custom_fields, with get_account_users supplying the account_user_id.
- send_proposal delivers a proposal to its assigned contacts, taking send_method, send_message or send_message_id, and password_reset.
- Pipeline visibility: get_proposal_directories returns proposal directories grouped by status — edit, open, won, lost and closed — and search_proposals finds proposals by query.
Requirements
An Offorte account, named in OFFORTE_ACCOUNT_NAME, and an API key for that account as OFFORTE_API_KEY.
Setup effort
One command plus a key — npx -y @offorte/mcp-server, then supply credentials
USE CASES
01
Drafting a proposal for a client who is already in your contacts
Find the person, confirm the details held against them, pick the template the work calls for, and create the proposal against that contact.
02
Quoting a prospect who is not on file yet
Add them as an organisation or an individual, assign the colleague who owns the deal, and get a proposal out in the same sitting.
03
Getting a finished proposal out with the right covering email
Choose the email template that suits the recipient, then send the proposal to the contacts already attached to it.
04
Seeing what is still open and what has closed
Read the proposal directories grouped by status to get the state of the pipeline, then search for the specific proposal you want to chase.
05
Making sure a proposal comes out in house style and language
Line up the design, language text and automation choices before composing, so the created proposal carries the right look and follow-up behaviour.
15 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
create_proposal
Create a new proposal
get_account_users
Lists all account users for the current account
get_automation_sets
Lists automation sets which are used as an optional input to create a new proposal
get_contact_details
Get all details for a contact by id
get_design_templates
Lists available design templates which are used to create new proposals
get_email_templates
Lists available email templates which are used to send proposals
get_initial_context
IMPORTANT: This tool must be called before using any other tools. It will get usage instructions & Offorte context for this MCP server.
get_proposal_directories
Get all proposal directories grouped by status (edit, open, won, lost, closed)
get_proposal_templates
Lists proposal templates which are used as starting points to create new proposals
get_text_templates
Lists available language text templates which are used to create new proposals
search_contact_organisations
Search for organisations by name in the contacts
search_contact_people
Search for people by name in the contacts
search_proposals
Search for proposals by query
send_proposal
Send a proposal to its assigned contacts
BEFORE YOU INSTALL
What to know first
Tools you get
15 tools when we connected. Writes are limited to create_contact, create_proposal and send_proposal; nothing edits or deletes a proposal. The documented get_users is registered as get_account_users.
Requires
- npx on PATH
- Node.js
- OFFORTE_ACCOUNT_NAME in your environment
- OFFORTE_API_KEY in your environment
Where it runs
Both documented setups run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 15 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @offorte/mcp-serverMCP Clients
Claude Desktop — npx
CLAUDE DESKTOP — NPX · JSON
{
"mcpServers": {
"offorte-proposals": {
"command": "npx",
"args": [
"-y",
"@offorte/mcp-server"
],
"env": {
"OFFORTE_ACCOUNT_NAME": "<YOUR_ACCOUNT_NAME>",
"OFFORTE_API_KEY": "<YOUR_TOKEN>"
}
}
}
}Claude Desktop — local build
CLAUDE DESKTOP — LOCAL BUILD · JSON
{
"mcpServers": {
"offorte-proposals": {
"command": "node",
"args": [
"<YOUR_PATH_TO_DIRECTORY>/offorte-mcp-server/dist/server.js"
],
"env": {
"OFFORTE_ACCOUNT_NAME": "<YOUR_ACCOUNT_NAME>",
"OFFORTE_API_KEY": "<YOUR_TOKEN>"
}
}
}
}
