Offorte Proposal Software
OfficialRelated Servers
Alternatives to Offorte Proposal Software
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server for the Fathom AI meeting intelligence API520 npmMIT
- AlicenseAqualityBmaintenanceMCP server for opencode that queries GitHub Copilot models via a persistent opencode server, requiring no API keys.288 npm3MIT
- AlicenseNot gradedqualityDmaintenanceMCP Server for the Perplexity API.39 PyPI66MIT
- MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for OpenAI ChatGPT API. Enables chat completions, vision analysis, embeddings, and model listing through natural language.-
- AlicenseAqualityCmaintenanceMCP server that exposes RESTForge capabilities to AI agents, enabling them to set up, configure, generate code, and manage RESTForge projects through natural language.2944 npmMIT
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.