Promptheus MCP Server

Promptheus MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. result = refine_prompt("Write a technical blog post", skip_questions=True) print(result["refined_prompt"]) ```.

What you get

Promptheus analyzes your prompts and refines them with: - Adaptive questioning: Smart detection of what information you need to provide - Multi-provider support: Works with Google, OpenAI, Anthropic, Groq, Qwen, and more - Interactive refinement: Iteratively improve outputs through natural conversation - Session history: Automatically track and reuse past prompts - CLI and Web UI: Use from terminal or browser

Setting it up

The server ships on PyPI as promptheus, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What the assistant can call

Once Promptheus is connected, these are the calls the assistant has available:

• refine_prompt — Intelligent prompt refinement with optional clarification questions
• tweak_prompt — The tweak_prompt tool exposed by this server
• list_models — The list_models tool exposed by this server
• list_providers — The list_providers tool exposed by this server
• validate_environment — The validate_environment tool exposed by this server

Configuration and credentials

You will need 5 environment variables: PROMPTHEUS_TELEMETRY_ENABLED, PROMPTHEUS_HISTORY_DIR, GOOGLE_API_KEY, ANTHROPIC_API_KEY, OPENAI_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the promptheus mcp server does with a few real requests.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Promptheus's toolset — refine_prompt, tweak_prompt, list_models and 2 more — is a fair guide to whether it matches your workflow. It is maintained by abhichandra21; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.