Privacy choices: we'd like to measure visits anonymously (our own cookie-free counter plus Google Analytics, which sets its own cookies; no ads) and load Beehiiv's newsletter sign-up, which may set its own cookies. Nothing optional runs until you choose. Privacy policy
Prompts for working with MCP servers: wire one up, audit what it can touch, debug it when it goes quiet.
Starter
Wire up an MCP server, then prove it works
MCPClaude CodeCursor
Add the server, list its tools, and smoke-test one read-only call.
Use it when: Adding a new MCP server to your agent.
Show promptHide prompt
Add the MCP server [SERVER NAME] to my agent config. Its [COMMAND / URL] is [CONNECTION DETAILS]. After wiring it up: 1) list the tools it exposes, 2) call the simplest read-only tool once to prove the connection works, 3) tell me what each tool can do and what permissions it needs. If a tool asks for credentials or write access, stop and ask me first — do not approve anything on your own.
Audit what an MCP server can touch
MCPClaude CodeCursor
A permission check before you connect a server you have not vetted.
Show promptHide prompt
Before I connect this MCP server, audit it: [SERVER NAME / REPO OR CONFIG]. Tell me: 1) every tool it exposes and whether each one reads, writes, deletes, or runs code, 2) what data it can reach (files, network, credentials, other apps), 3) anything it sends outside my machine, 4) any known issues or red flags in its repo or docs. End with a verdict: safe to connect, connect with limits (say which), or do not connect — and why.
Debug a silent MCP tool call
MCPClaude CodeCursor
A step-by-step diagnosis when a tool returns nothing, errors, or hangs.
Show promptHide prompt
This MCP tool call is failing: server [SERVER], tool [TOOL], arguments [ARGUMENTS], result [ERROR OR EMPTY RESPONSE]. Diagnose it step by step: 1) is the server running and reachable, 2) are the arguments valid for this tool's schema, 3) is it an auth or permissions problem, 4) is the server returning an error it is swallowing? Fix the smallest thing that is actually wrong. Do not retry the same call more than twice, and do not invent a successful result.
Pick the right MCP server for the job
MCPClaude CodeCursor
Compare candidates on what they really do, setup effort, and upkeep.
Use it when: Two or more MCP servers claim to do the same thing.
Show promptHide prompt
I need an MCP server for [TASK]. Candidates: [SERVER A], [SERVER B], [SERVER C]. Compare them on: 1) does it actually do [TASK] or only part of it, 2) setup effort and what it needs from me, 3) what it can read, write, or send, 4) maintenance — last update, open issues, who runs it. Recommend one, name the runner-up, and say what would change your pick.
Write a minimal MCP server spec
MCPClaude CodeCursor
A tight spec for a small custom server: tools, inputs, and limits only.
Use it when: You need a small custom MCP server and want it built once, properly.
Show promptHide prompt
Design a minimal MCP server for [PURPOSE]. Keep it to at most [NUMBER] tools. For each tool, give: name, what it does, inputs (name, type, required or optional), outputs, and what it must never do. List the permissions it needs and nothing more. Then write the config snippet to add it to [AGENT: Claude Code / Cursor / ...]. Do not add features I did not ask for — if something is nice-to-have, list it separately as 'later'.
Send us one prompt that makes a coding, MCP or browser agent do better work. Hand-written and original only — we check every prompt by hand before it goes live.