You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a small docs primer that explains MCP accurately, simply, and safely for non-technical business users and beginner developers.
Context
The repo needs a durable explanation layer before adding more demos. The primer should summarize what MCP is, why it exists, and how hosts, clients, servers, tools, resources, and prompts fit together. It should also make security/data-handling boundaries clear from the start.
Exact filenames can differ if the final structure is cleaner.
Acceptance criteria
Explains MCP in plain English.
Explains host, client, and server roles with a simple analogy.
Explains tools, resources, and prompts with business examples.
Includes a short history section with citation-friendly TODOs or links to official sources.
Includes a safety section covering least privilege, read-only-first demos, no real client data, no secrets in notebooks, and human approval for sensitive actions.
Links the docs from the README.
Avoids unsupported claims about industry adoption, governance, or product support unless clearly marked for later citation review.
Non-goals
Do not implement a new MCP server.
Do not change package code.
Do not build a demo website.
Do not add claims/legal workflow code.
Validation
ruff check .
mypy --strict .
pytest -q
Suggested Claude Code review focus
Review for factual accuracy, overselling, unsupported claims, and whether a regular business user can understand the docs without knowing Python.
Objective
Add a small docs primer that explains MCP accurately, simply, and safely for non-technical business users and beginner developers.
Context
The repo needs a durable explanation layer before adding more demos. The primer should summarize what MCP is, why it exists, and how hosts, clients, servers, tools, resources, and prompts fit together. It should also make security/data-handling boundaries clear from the start.
Scope
Create or update docs such as:
Exact filenames can differ if the final structure is cleaner.
Acceptance criteria
Non-goals
Validation
Suggested Claude Code review focus
Review for factual accuracy, overselling, unsupported claims, and whether a regular business user can understand the docs without knowing Python.