write_proposal_from_hours — sow MCP Prompt
write_proposal_from_hours
is one of 2 prompts on the
sow
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 sow Prompt/write_proposal_from_hours run in your project directory
- Claude Desktop sow Prompt/write_proposal_from_hours ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor sow Prompt/write_proposal_from_hours ~/.cursor/mcp.json
- VS Code sow Prompt/write_proposal_from_hours .vscode/mcp.json
- Zed sow Prompt/write_proposal_from_hours ~/.config/zed/settings.json
- Windsurf sow Prompt/write_proposal_from_hours ~/.codeium/windsurf/mcp_config.json
- Cline sow Prompt/write_proposal_from_hours ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI sow Prompt/write_proposal_from_hours ~/.gemini/settings.json
- Grok sow Prompt/write_proposal_from_hours .mcp.json (in your project root)
- ChatGPT sow Prompt/write_proposal_from_hours Settings → Connectors → Advanced → Developer mode
- Claude.ai sow Prompt/write_proposal_from_hours Settings → Connectors → Add custom connector
- LangChain sow Prompt/write_proposal_from_hours pip install langchain-mcp-adapters
Other prompts on this server
sow 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.