Architecture¶

Personal MCP is a small publishing service. Markdown is written once and made available in two ways:

1. as an MCP server for AI clients
2. as a documentation website for people

How It Fits Together¶

flowchart LR
    A[Markdown in src/jsl_mcp/docs] --> B[MCP resources and prompts]
    A --> C[Documentation website]
    B --> D[AI clients]
    C --> E[Human readers]

The running application has two routes:

• /mcp is the MCP endpoint.
• /docs/ is the pre-built documentation site.

The root URL redirects to the website.

Content Types¶

The server publishes three kinds of Markdown content:

• Skills are reusable guidance that clients read as skill:// resources.
• Prompts are parameterized workflows that clients invoke as MCP prompts.
• Documentation is available to clients through resource://docs/... and to people on the website.

FastMCP provides the MCP behavior. FastAPI hosts that server beside the static site, and Zensical builds the site from the same Markdown files.

Source Of Truth¶

All authored content lives under src/jsl_mcp/docs/. The generated src/jsl_mcp/site/ directory is build output and should not be edited by hand.

For exact file formats and URI rules, see the content contracts. For everyday changes, start with the Authoring Guide.