write_proposal_from_hours — docx MCP Prompt
write_proposal_from_hours
is one of 2 prompts on the
docx
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke write_proposal_from_hours from your client
- Claude Code docx Prompt/write_proposal_from_hours run in your project directory
- Claude Desktop docx Prompt/write_proposal_from_hours ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor docx Prompt/write_proposal_from_hours ~/.cursor/mcp.json
- VS Code docx Prompt/write_proposal_from_hours .vscode/mcp.json
- Zed docx Prompt/write_proposal_from_hours ~/.config/zed/settings.json
- Windsurf docx Prompt/write_proposal_from_hours ~/.codeium/windsurf/mcp_config.json
- Cline docx Prompt/write_proposal_from_hours ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI docx Prompt/write_proposal_from_hours ~/.gemini/settings.json
- Grok docx Prompt/write_proposal_from_hours .mcp.json (in your project root)
- ChatGPT docx Prompt/write_proposal_from_hours Settings → Connectors → Advanced → Developer mode
- Claude.ai docx Prompt/write_proposal_from_hours Settings → Connectors → Add custom connector
- LangChain docx Prompt/write_proposal_from_hours pip install langchain-mcp-adapters
Other prompts on this server
docx also offers 2 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.