Skip to main content
Glama
Offorte Proposal Software

Offorte Proposal Software

Official
by offorte

Offorte MCP Server

MCP server for Offorte - Create & send proposals using AI.

This server acts as the bridge between AI agents and Offorte's proposal engine. It enables external models to create and send proposals via Offorte. Built for automation workflows, the MCP makes it easy to integrate proposal actions into AI tools, chat interfaces, and autonomous systems.

Early technology Please note that MCP (Model Context Protocol) is a new approach to AI integration. While powerful, it's still evolving and may occasionally produce unexpected or undesired results.

Table of Contents

Related MCP server: mcp-clickup

About Offorte

Offorte is automated proposal software which helps businesses create, send, and track beautiful interactive proposals. Built for speed, flexibility, and real-world use, it combines automation and smart workflows without sacrificing the personal touch. Learn more about Offorte.

API

The MCP server is using the Offorte Public API v2. Read the API documentation for more information.

Demo

Experience the future of proposals: voice-triggered, AI-powered, fully automated. See how Offorte connects voice and workflow in this real demo.

Goals & Coverage

The goal of this project is too create & send proposals using AI via the protocol. Because of the experimental character, the full Offorte API is not covered and its limited to the tools needed to create, copy & send proposals and to update their price tables. Update tools exist for proposal price tables only: update_proposal_pricetables replaces the rows of named price tables. Other update tools and delete tools are not implemented. They might be added in the future, based on reallife results & user feedback.

Prerequisites

  • Node.js 24.x LTS (>=24, see .nvmrc)

  • Offorte API Key (see Authentication Section of the Offorte API Docs)

  • PNPM for development

  • TRANSPORT_TYPE (optional): Set to sse to enable Server-Sent Events (SSE) mode, or leave unset/default for stdio (default: stdio).

Available Tools

Context & Setup

  • get_initial_context – IMPORTANT: Must be called before using any other tools to initialize context and get usage instructions

Account

  • get_users – Lists all account users for the current account

Automations

  • get_automation_sets – Lists automation sets which are used as an optional input to create a new proposal

Contacts

  • create_contact – Create a new contact (organisation or person/individual)

  • get_contact_details - Get all details for a contact by id

  • search_contact_organisations - Search for organisations by name in the contacts

  • search_contact_people - Search for people by name in the contacts

Favorites

  • get_proposal_templates – Lists proposal templates which are used as starting points to create new proposals

Proposals

  • copy_proposal – Copy a proposal into a new proposal with status edit and a new link

  • create_proposal – Create a new proposal

  • get_proposal_details – Get all details for a proposal by id, including its price tables with their Unique IDs and rows

  • get_proposal_directories – Get all proposal directories grouped by status

  • search_proposals – Search for proposals by query

  • send_proposal – Send a proposal to its assigned contacts

  • update_proposal_pricetables – Replace all rows of the named price tables in a proposal. Tables need a Unique ID. A Unique ID is text: copy it exactly from the price table settings, including any leading zeroes (001 is not 1), and never guess or normalize it. Won and lost proposals cannot be updated

Settings

  • 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_text_templates – Lists available language text templates which are used to create new proposals

MCP Clients

Currently, this MCP server has only been tested with Claude Desktop. More client examples will be added in the future.

Claude Desktop Configuration

Find your claude_desktop_config.json at Claude > Settings > Developer > Edit Config and depending on which option you'd like, add JUST ONE of the following:

NPX

Running it straight from the npm registry.

{
	"mcpServers": {
		"offorte-proposals": {
			"command": "npx",
			"args": ["-y", "@offorte/mcp-server"],
			"env": {
				"OFFORTE_ACCOUNT_NAME": "<YOUR_ACCOUNT_NAME>",
				"OFFORTE_API_KEY": "<YOUR_TOKEN>"
			}
		}
	}
}

Local Node

Dependencies should have been installed & the project is build before you use this method (pnpm install).

{
	"mcpServers": {
		"offorte-proposals": {
			"command": "node",
			"args": ["/path/to/directory/offorte-mcp-server/dist/server.js"],
			"env": {
				"OFFORTE_ACCOUNT_NAME": "<YOUR_ACCOUNT_NAME>",
				"OFFORTE_API_KEY": "<YOUR_TOKEN>"
			}
		}
	}
}

Development

To get started, clone the repository and install the dependencies. Make sure you have an .env file and it includes the proper values.

git clone https://github.com/offorte/offorte-mcp-server.git
cd offorte-mcp-server
pnpm install
pnpm dev

Commands

Check the NPM scripts for all commands, below is a short summary of the most important onces.

Script

Info

pnpm build

Build the project for production

pnpm start

Start the production server

pnpm dev

Start the development server

pnpm inspect

Inspect the server

pnpm format

Format code using Prettier and ESLint

Available Tools

18 tools
copy_proposalC

Copy a proposal into a new proposal with status edit, a new proposal number and a new link

Inputs: name (required), contact_id (required), proposal_id (required), directory_id, +2 more.

create_contactC

Create a new contact (organisation or person/individual)

Inputs: name (required), type (required), city, tags, +17 more.

create_proposalD

Create a new proposal

Inputs: name (required), contact_id (required), contact_people (required), text_template_id (required), +4 more.

get_account_usersB
Read-only

Lists all account users for the current account

Inputs: no named parameters.

get_automation_setsA
Read-only

Lists automation sets which are used as an optional input to create a new proposal

Inputs: no named parameters.

get_contact_detailsC
Read-only

Get all details for a contact by id

Inputs: contact_id (required).

get_design_templatesB
Read-only

Lists available design templates which are used to create new proposals

Inputs: no named parameters.

get_email_templatesB
Read-only

Lists available email templates which are used to send proposals

Inputs: no named parameters.

get_initial_contextA
Read-only

IMPORTANT: This tool must be called before using any other tools. It will get usage instructions & Offorte context for this MCP server.

Inputs: no named parameters.

get_proposal_detailsB
Read-only

Get all details for a proposal by id, including its price tables with their Unique IDs and rows

Inputs: proposal_id (required).

get_proposal_directoriesB
Read-only

Get all proposal directories grouped by status (edit, open, won, lost, closed)

Inputs: no named parameters.

get_proposal_templatesA
Read-only

Lists proposal templates which are used as starting points to create new proposals

Inputs: no named parameters.

get_text_templatesA
Read-only

Lists available language text templates which are used to create new proposals

Inputs: no named parameters.

search_contact_organisationsC
Read-only

Search for organisations by name in the contacts

Inputs: search (required).

search_contact_peopleC
Read-only

Search for people by name in the contacts

Inputs: search (required).

search_proposalsC
Read-only

Search for proposals by query

Inputs: search (required).

send_proposalC
Destructive

Send a proposal to its assigned contacts

Inputs: proposal_id (required), send_method, send_message, password_reset, +1 more.

update_proposal_pricetablesA
DestructiveIdempotent

Replace all rows of the named price tables in a proposal. Tables that are not named stay unchanged. Returns the updated tables and the proposal total

Inputs: pricetables (required), proposal_id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.9/5.0

    Scored across 18 tools

    Disambiguation4/5

    Each tool targets a distinct resource and action: contact search (organisations vs people), contact details, proposal search vs proposal details, and separate list tools for design, email, text, and proposal templates. The main mild ambiguity is among the several get_*_templates listers and between get_proposal_directories and search_proposals, but descriptions clarify the differences.

    Naming Consistency4/5

    All names use snake_case with a leading verb (get_, search_, create_, copy_, send_, update_), which is a predictable and readable pattern. Minor deviations exist: search_contact_organisations/search_contact_people use a different noun ordering than get_contact_details, and get_initial_context is a meta-tool that breaks the domain pattern.

    Tool Count4/5

    18 tools is slightly above the ideal band but each one maps to a concrete concept in proposal creation (contacts, templates, automation sets, proposals, price tables). None appear redundant, so the surface feels scoped rather than bloated.

    Completeness3/5

    Creation and read paths are well covered (contacts, proposals, templates, price tables, sending, copying), but there are notable gaps: no update for proposal metadata/status (won/lost/closed transitions), no update_contact, and no delete or archive operations for contacts or proposals. Agents will hit dead ends when they need to modify or remove existing records.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers