# MCP Server Explainer / Planner

Explain an MCP server and turn a use case into a scoped implementation and security plan.

## Prompt

Explain and plan an MCP server for {{use_case}}.

AUDIENCE EXPERIENCE:
{{experience}}

HOST ENVIRONMENT:
{{host}}

DATA OR SERVICES:
{{services}}

SECURITY CONSTRAINTS:
{{security}}

First explain, in language appropriate to the audience:
- what the MCP server does;
- hosts, clients, servers, tools, resources, prompts, and transport;
- the request/response path;
- where authentication and authorization belong.

Then produce an implementation plan:
1. define the smallest useful capabilities;
2. choose tools versus resources and justify each choice;
3. specify input/output schemas and error behavior;
4. map trust boundaries, credentials, least privilege, confirmation points, and audit logging;
5. address injection risks from tool results and external content;
6. plan local development, tests, deployment, versioning, and observability;
7. provide a phased milestone list and acceptance criteria.

Do not include secrets. Do not assume remote hosting is required. Clearly label choices that depend on the selected SDK or host.

## How to use

Name the host application and the systems the server may access. Use the plan to create a technical design before implementation.

## Examples

Example input: a local MCP server that lets a desktop assistant search approved internal runbooks read-only.

Expected output: accessible explanation, capability map, schemas, trust-boundary review, phased build plan, and acceptance tests.

## Variables

- use_case: What the MCP server should enable.
- experience: The audience technical level.
- host: The MCP host and deployment environment.
- services: Data stores or APIs the server may access.
- security: Authentication, privacy, and approval constraints.

Version: 1
Author: JRamos / John Ramos
License: All Rights Reserved

Initial original UMG Prompt Library release.