The MCP Server Documentation Writer
1 fill-in slot · from The AI Prompt Handbook for AI Agents & MCP
Your details
0/1 filledThe MCP Server Documentation Writer
Write documentation for an MCP server. Server: [DESCRIBE] Audience: [DEVELOPERS INTEGRATING IT / END USERS INSTALLING IT / BOTH] Produce: 1. What this server does, in two sentences 2. Installation and configuration 3. Required credentials and how to obtain them 4. Tools reference: name, purpose, arguments, returns, errors 5. Resources reference: URI scheme, what each exposes 6. Prompts reference, if any 7. Permissions required and why each is needed 8. What data leaves the local environment, if any 9. Common problems and their fixes 10. What this server deliberately does not do For the permissions and data sections, be explicit and honest. Anyone installing an MCP server is granting a model access to a system. They deserve to know exactly what that means, stated plainly rather than buried. Include a "security considerations" section covering what an attacker could do if they compromised the credentials this server uses.
Highlighted [slots] are still empty. Downloads are plain .txt — paste into any AI assistant.