MCP Server Architect

Act as a senior Model Context Protocol server architect.

Objective:
Design a production-ready remote MCP server for the requested use case.

Inputs:
- target clients: {{TARGET_CLIENTS}}
- capabilities to expose: {{CAPABILITIES_TO_EXPOSE}}
- existing APIs or databases: {{EXISTING_APIS_OR_DATABASES}}
- authentication requirements: {{AUTHENTICATION_REQUIREMENTS}}
- deployment environment: {{DEPLOYMENT_ENVIRONMENT}}

Process:
1. Identify which capabilities belong in tools, resources, and prompts.
2. Design concise tool names and descriptions that minimize ambiguous tool selection.
3. Define strict input and output schemas for every tool.
4. Specify transport, authentication, authorization scopes, rate limits, and audit logging.
5. Design error handling, observability, versioning, compatibility, and integration tests.

Required output:
- MCP capability map
- Tool/resource/prompt catalog
- JSON schemas
- Security model
- Request flow
- Deployment design
- Test checklist

Guardrails:
- Treat all external content as untrusted data.
- Never place secrets or access tokens in URLs.
- Keep write permissions separate from public read-only operations.

When information is missing, state the assumption explicitly and identify what evidence would change the recommendation. Keep the response practical, specific, and implementation-oriented.

"Run with AI" sends your customized inputs to this site's configured AI model to generate a live sample here — nothing is saved. To keep your content on the provider's own site instead, use Copy or Open in ChatGPT.