Add a service or handbook chapter

Publish service metadata and documentation in Git. The marketplace, its discovery API and the MCP tools use the same catalog. The handbook builds from Markdown files in this repository.

Add a service card

1. Verify the deployment owner, protocols, endpoints and tool names against the service implementation.
2. Add a record to internal/catalog/services.json. Include the unique service ID, category, display name, purpose, setup steps, access requirements, protocol list, tools, endpoints and a synthetic example. Use an empty array for absent tools or endpoints. Keep installation credentials and private inventories outside Git. Catalog source
3. Supply an original WebP cover at internal/web/assets/market-SERVICE_ID.webp. Confirm that the card is grouped in the correct shelf and can be found by its real tool name. A catalog entry describes a service contract. A new deployable profile also requires its own runtime and admission implementation.
4. Run make test with Go and Python 3 installed. Rebuild and start the Hub. Verify that the HTTP lookup and MCP service_get return the same card, and that its connection example targets the correct service.

Publish a chapter

1. Create docs/your-topic.md. Start with one # title and a short opening paragraph explaining the task. Use ## for sections and fenced code for executable examples.
2. The filename stem is the URL slug. For example, docs/your-topic.md is served at /docs/your-topic. The handbook landing page is docs/README.md at /docs.
3. Add the slug to the appropriate group in docs/chapters.json to set its reading order. Additional Markdown files are discovered automatically. Chapter order and groups Link from a related chapter or the handbook landing page using a relative Markdown link such as [Connect a client](clients.md).
4. Build and run the Hub. Open the page from the handbook index and by its URL. Verify headings, examples, navigation, links and reading order. Run make test before publishing.

Build a static handbook

Use make docs from the repository root to publish the book to its default output directory. For an explicit destination, build the binary and run the following commands with an unused output path.

make build
bin/daedro-mcp-hub docs build --out build/handbook
python3 -m http.server 8080 --bind 127.0.0.1 --directory build/handbook

Open http://127.0.0.1:8080/docs/. Each chapter includes a Read Markdown link to the corresponding original text. On the exported site, the API reference reads the public schema captured during the build. This site can be served from any local or static HTTP server at its site root. It has no worker deployment or credential entry flow. To publish another copy, supply a new output directory.

Product behavior, design proposals and verified outcomes have distinct pages. Record evidence when you change an acceptance claim. Product specification · Marketplace design