Objective
Rework the repository landing experience so a first-time, non-technical business user can understand what MCP is, why it matters, and what they can safely try in this repo.
Context
The repo already has setup steps, CLI examples, notebook references, screenshots, a glossary, and common issues. The next improvement should be positioning: make the README feel like a clear learning product instead of a developer scratchpad.
Scope
- Update
README.md.
- Add
docs/00-start-here.md if it helps keep the README concise.
- Fix obviously incorrect or placeholder MCP links in
AGENTS.md.
- Preserve the existing Python package, CLI examples, notebook references, and sample-data workflow.
Acceptance criteria
Non-goals
- Do not add a web app.
- Do not add MCPB packaging.
- Do not add claims automation code.
- Do not introduce new runtime dependencies.
Validation
Run the existing quality gate even though this should be docs-focused:
ruff check .
mypy --strict .
pytest -q
Suggested Codex /goal summary
Improve the README and beginner entry docs so regular business users understand MCP, while preserving the existing CLI/package/test behavior.
Objective
Rework the repository landing experience so a first-time, non-technical business user can understand what MCP is, why it matters, and what they can safely try in this repo.
Context
The repo already has setup steps, CLI examples, notebook references, screenshots, a glossary, and common issues. The next improvement should be positioning: make the README feel like a clear learning product instead of a developer scratchpad.
Scope
README.md.docs/00-start-here.mdif it helps keep the README concise.AGENTS.md.Acceptance criteria
Business Question -> AI Host -> MCP Client -> MCP Server -> Tool/Data -> Answer.Non-goals
Validation
Run the existing quality gate even though this should be docs-focused:
Suggested Codex
/goalsummaryImprove the README and beginner entry docs so regular business users understand MCP, while preserving the existing CLI/package/test behavior.