MCP Server Spec Writer
By Marcus Bell · Published · Updated
Spec out a Model Context Protocol server — tools, schemas, auth, and error handling — before you write any code.
Tags: AI, Engineering, Technical
Prompt template
## MCP Server Spec Write a build-ready spec for a Model Context Protocol server. ## Purpose - [text: What system or data the server exposes] — e.g. an internal CRM, a docs wiki - [textarea: What an AI assistant should be able to do with it] — concrete example requests - [dropdown: Read-only, Read and write, Write with confirmation] access level ## Interface - [textarea: Candidate tools] — rough list; the spec should refine names and merge overlaps - [dropdown: API key, OAuth, None - local only] authentication - [toggle: Yes, No] include resources (browsable data) as well as tools ## Constraints - [textarea: Rate limits, data privacy rules, or fields to redact] - [dropdown: TypeScript, Python] implementation language Produce the spec: server overview, each tool with name, description written for the model, input schema with types, return shape, and error cases; auth flow; and a short risks section covering what a misbehaving model could do with write access.