Meta-Prompt MCP
Instant access to Google and Anthropic's official prompting guides within your LLM workflow—optimized for crafting high-quality meta-prompts and system prompts.
What It Does
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.
How It Works
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 │
└──────────────────────────┘
Key Features
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 thinking- Zero dependencies — Runs entirely offline with bundled guides; no API keys or network calls required
Validation
We 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
Quick Start
1. Install
# 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.
2. Configure Your MCP Host
Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"meta-prompt-mcp": {
"command": "uvx",
"args": ["meta-prompt-mcp"]
}
}
}
Cursor
Add to your MCP settings:
{
"mcpServers": {
"meta-prompt-mcp": {
"command": "uvx",
"args": ["meta-prompt-mcp"]
}
}
}
Claude Code
Run the following command in your terminal:
claude mcp add meta-prompt-mcp -- uvx meta-prompt-mcp
Usage
Query the guides while crafting your prompts. Examples:
- "I'm building a code reviewer agent. Reference the Google guide to help me write a better system prompt."
- "Based on the Anthropic guide, suggest improvements to this prompt for better reasoning."
- "What technique from the guides would work best for this task?"
The LLM reads the guides and uses that knowledge to give you more informed suggestions and feedback on your prompts.
Development
# 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
Available Commands
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
Project Structure
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
Contributing
Issues, feature requests, and contributions welcome. Please open an issue on GitHub.
License
MIT
Metadata
Release files for meta-prompt-mcp 1.0.12
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| meta_prompt_mcp-1.0.12.tar.gz | 52.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| meta_prompt_mcp-1.0.12-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 88.2 kB
Release files / meta_prompt_mcp-1.0.12.tar.gz
| Download URL | meta_prompt_mcp-1.0.12.tar.gz |
|---|---|
| Size | 52.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
508dc71395684352d5f06ec6f83c8df7e7e19109dca783e763df9edfbaf67786
|
|
BLAKE2b-256 checksum How to use checksums |
d50269545560f701b7f27eb7b00d76558dec5168dfc6fb2bb701388753f01173
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 19, 2026.
Transparency logRelease files / meta_prompt_mcp-1.0.12-py3-none-any.whl
| Download URL | meta_prompt_mcp-1.0.12-py3-none-any.whl |
|---|---|
| Size | 36.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
29763311479428d7018739bfdcf4e708e2e3535ba0ad5ba21611124d7d613e50
|
|
BLAKE2b-256 checksum How to use checksums |
aa2eb5c1f16a96a377e509c48a449f9b3ec83746e9887ef8d69ba675ae9ac883
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 19, 2026.
Transparency log