ProposalPilot MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | Yes | Your Anthropic API key |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_proposalC | Generate a professional freelance project proposal using AI. Creates a complete proposal with executive summary, scope of work, timeline, pricing, and terms. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The name 'generate_proposal' follows a clear verb_noun pattern.
A single tool is too few for a server named 'ProposalPilot MCP Server', which suggests a broader scope for managing proposals. This minimal set limits functionality and likely leaves gaps in the proposal lifecycle.
The tool set is severely incomplete for the implied domain of proposal management. It only provides generation, with no tools for editing, reviewing, listing, deleting, or other essential CRUD operations, causing significant agent failures.