MCP server providing official Google and Anthropic prompting guides for meta-prompt generation.
Instant access to Google and Anthropic's official prompting guides within your LLM workflow—optimized for crafting high-quality meta-prompts and system prompts.
Meta-Prompt MCP is an MCP server that surfaces official prompting best practices from Google and Anthropic directly within your LLM workflow. Instead of searching documentation or guessing how to instruct an LLM, you can query expert guides on-demand.
This is especially valuable when crafting meta-prompts (system prompts for agents) or optimizing your own prompting strategies. By grounding your prompts in proven methodology, you'll generate more effective, well-structured outputs.
Your MCP host (Claude Desktop, Cursor, etc.) communicates with the server via stdio. When you ask for a guide, the server retrieves it from bundled markdown files—no API calls, no latency.
┌────────────────────────┐ ┌──────────────────────────┐
│ Your LLM Host │◄─stdio──►│ Meta-Prompt MCP Server │
│ (Claude Desktop, etc) │ │ │
└────────────────────────┘ │ • get_google_guide │
│ • get_anthropic_guide │
│ │
│ Data layer: │
│ ./data/ │
│ ├── google_*.md │
│ └── anthropic_*.md │
└──────────────────────────┘
get_google_guide — Retrieves Google's comprehensive prompting guide covering techniques, best practices, and LLM configurationget_anthropic_guide — Retrieves Anthropic's guide on chain-of-thought, multishot prompting, and extended thinkingWe ran a benchmark comparing prompts generated with and without guide access across 5 diverse tasks. An independent judge LLM scored each on Clarity, Specificity, Structure, Effectiveness, and Overall quality (1–10 scale).
To reproduce the benchmark:
export OPENROUTER_API_KEY=sk-or-...
make benchmark
# Via uvx (recommended — run without installing globally)
uvx meta-prompt-mcp
# Or install via pip
pip install meta-prompt-mcp
The package ships with bundled markdown guides — no API keys or setup needed.
Add to your claude_desktop_config.json:
{
"mcpServers": {
"meta-prompt-mcp": {
"command": "uvx",
"args": ["meta-prompt-mcp"]
}
}
}
Add to your MCP settings:
{
"mcpServers": {
"meta-prompt-mcp": {
"command": "uvx",
"args": ["meta-prompt-mcp"]
}
}
}
Run the following command in your terminal:
claude mcp add meta-prompt-mcp -- uvx meta-prompt-mcp
Query the guides while crafting your prompts. Examples:
The LLM reads the guides and uses that knowledge to give you more informed suggestions and feedback on your prompts.
# Clone the repo
git clone https://github.com/kapillamba4/meta-prompt-mcp.git
cd meta-prompt-mcp
# Install in dev mode
make dev
# Run the server
make run
make dev # Install in editable mode with dev dependencies
make run # Start the MCP server locally
make lint # Check code quality
make format # Auto-format code with Black & isort
make test # Run test suite
make benchmark # Run prompt quality benchmark (requires OPENROUTER_API_KEY)
make build # Build distribution packages
make publish # Publish to PyPI
meta-prompt-mcp/
├── pyproject.toml # Dependencies and package config
├── Makefile # Development commands
├── .env.example # Template for OPENROUTER_API_KEY
│
├── benchmarks/
│ ├── benchmark.py # Prompt quality evaluation script
│ └── results.md # Benchmark results
│
└── src/meta_prompt_mcp/
├── __init__.py
├── __main__.py # Entry point (python -m)
├── server.py # FastMCP server & tool definitions
└── data/
├── google_prompting_guide.md
└── anthropic_prompting_guide.md
Issues, feature requests, and contributions welcome. Please open an issue on GitHub.
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
uvx meta-prompt-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-kapillamba4-meta-prompt-mcp": {
"command": "uvx",
"args": [
"meta-prompt-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencemeta-prompt-mcppypiio.github.kapillamba4/meta-prompt-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.