MCP server to give developers access to prompts from promptz.dev
If you already use Promptz MCP, the promptz mcp mcp server is the piece that lets your assistant work with it directly. MCP server to give developers access to prompts from promptz.dev.
Access prompts from promptz.dev directly within Amazon Q Developer.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Troubleshooting — 1. Check that your API credentials are correct 2. Ensure the server is properly configured in your MCP client 3. Look for error messages in the logsConfiguration is passed through the environment: PROMPTZ_API_URL, PROMPTZ_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
The server ships on npm as npm, 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.
This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Promptz MCP's toolset — Troubleshooting — is a fair guide to whether it matches your workflow. It is maintained by cremich; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Promptz MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Troubleshooting | 1. Check that your API credentials are correct 2. Ensure the server is properly configured in your MCP client 3. Look for error messages in the logs located ad ~/.promptz/logs/mcp-server.log 4. Use the MCP Inspector for |
{
"mcpServers": {
"promptz.dev": {
"command": "npx",
"args": ["-y", "@promptz/mcp"],
"env": {
"PROMPTZ_API_URL": "your-api-url-from-promptz.dev",
"PROMPTZ_API_KEY": "your-api-key-from-promptz.dev"
},
"disabled": false,
"autoApprove": []
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| PROMPTZ_API_URL | Endpoint or connection string the server talks to. | Yes |
| PROMPTZ_API_KEY | Credential the server authenticates with. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.