.prompts vs Proving Ground
A side-by-side look at the .prompts and Proving Ground MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
.
.promptsDeveloper Tools.prompts, the home to all your AI prompts, everywhere you need them.38FairAuth: not declaredP
Proving GroundDeveloper ToolsAccounts-payable exception environment with a pass/fail verifier and proof packet: AI agents work AP36FairAuth: not declaredVerdict: choose .prompts for developer tools work; choose Proving Ground for developer tools. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
PChoose Proving Ground when
- You need dedicated capabilities in the Developer Tools domain.
- You have the keys it needs:
OPENROUTER_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | . .prompts | P Proving Ground |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 38/100 · Fair | 36/100 · Fair |
| Install command | Not confirmed yet | Not confirmed yet |
| Transport | — | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | OPENROUTER_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 0 |
| Directory activity | 5 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View .prompts | View Proving Ground |
Tools & capabilities
.prompts tools
No tool names declared yet. Check the project README from the listing page.
Proving Ground tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
.prompts
No confirmed install command for .prompts yet — follow the setup steps linked from its listing page rather than a guessed package name.
Proving Ground
No confirmed install command for Proving Ground yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
.prompts is categorized under Developer Tools and uses an install path we have not confirmed yet. Proving Ground belongs to Developer Tools and uses an install path we have not confirmed yet. Pick .prompts for developer tools work and Proving Ground for developer tools.
Neither server has a confirmed install command yet, so we don't publish a guessed config. Follow each project's own setup instructions, linked from its listing page.
.prompts has no declared pricing — check the project's own site. Proving Ground has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add prompts and proving-ground as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, .prompts has a quality signal of 38/100 (Fair) with 5 views, 0 installs and 0 GitHub stars. Proving Ground has 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.