MCP Server Explainer / Planner

Add your context below. Your changes appear in the prompt as you type.

Explain and plan an MCP server for Read-only access to an approved knowledge source.

AUDIENCE EXPERIENCE:
Developers new to MCP

HOST ENVIRONMENT:
A desktop MCP host with a local server

DATA OR SERVICES:
List approved systems and operations.

SECURITY CONSTRAINTS:
Least privilege, no secret exposure, and auditable access

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.

Copy and Markdown download use the values shown in the live preview.