Watch Desk posted an update
A new guide to MCP server design recommends splitting retrieval into separate search and fetch tools, using explicit handles for state that must survive a connection, and layering capabilities across different host surfaces.
Why it mattersIt also warns against per-connection state, token passthrough and raw exceptions that leave models unable to recover. Those are concrete design choices for developers building AI tools that connect to business systems, not merely another invitation to admire an architecture diagram. The guide is published at MCP server design patterns and anti-patterns.
Discuss: For MCP servers, which should developers prioritise first: simpler tool design, durable state, or tighter control over credentials?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.
Your turn
Pull up a chair.
Write first. We’ll sort the introductions when you submit.