Offorte Proposal Software
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRANSPORT_TYPE | No | Set to 'sse' to enable Server-Sent Events (SSE) mode, or leave unset/default for 'stdio' | stdio |
| OFFORTE_API_KEY | Yes | Your Offorte API key | |
| OFFORTE_ACCOUNT_NAME | Yes | Your Offorte account name |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_initial_contextA | IMPORTANT: This tool must be called before using any other tools. It will get usage instructions & Offorte context for this MCP server. |
| get_account_usersB | Lists all account users for the current account |
| get_automation_setsA | Lists automation sets which are used as an optional input to create a new proposal |
| get_contact_detailsC | Get all details for a contact by id |
| get_design_templatesB | Lists available design templates which are used to create new proposals |
| get_email_templatesB | Lists available email templates which are used to send proposals |
| get_proposal_detailsB | Get all details for a proposal by id, including its price tables with their Unique IDs and rows |
| get_proposal_directoriesB | Get all proposal directories grouped by status (edit, open, won, lost, closed) |
| get_proposal_templatesA | Lists proposal templates which are used as starting points to create new proposals |
| get_text_templatesA | Lists available language text templates which are used to create new proposals |
| search_contact_organisationsC | Search for organisations by name in the contacts |
| search_contact_peopleC | Search for people by name in the contacts |
| search_proposalsC | Search for proposals by query |
| create_contactC | Create a new contact (organisation or person/individual) |
| create_proposalD | Create a new proposal |
| copy_proposalC | Copy a proposal into a new proposal with status edit, a new proposal number and a new link |
| send_proposalC | Send a proposal to its assigned contacts |
| update_proposal_pricetablesA | 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 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
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.
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.
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.
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.