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_usersA | 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_detailsB | Get all details for a contact by id |
| get_design_templatesA | Lists available design templates which are used to create new proposals |
| get_email_templatesA | Lists available email templates which are used to send proposals |
| get_proposal_directoriesA | 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_organisationsA | Search for organisations by name in the contacts |
| search_contact_peopleB | 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_proposalC | Create a new proposal |
| send_proposalC | Send a proposal to its assigned contacts |
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 15 tools
Each tool has a clear, distinct purpose. Tools like create_contact, create_proposal, search_proposals, and send_proposal are unambiguous. The special get_initial_context tool is clearly separated.
All tool names follow a consistent snake_case verb_noun pattern (e.g., create_contact, get_design_templates, search_proposals). Even compound names like get_account_users are consistent.
With 15 tools, the set is well-scoped for a proposal software. It covers contacts, proposals, templates, automation, and sending without being bloated or sparse.
The tool set covers creation, retrieval, search, and sending, but lacks update and delete operations for both contacts and proposals. Missing get_proposal_details creates a gap.