Admin MCP

Use the Admin MCP to intellegently and autonomously use the install.md service. This enables an Agent or LLM system to create Projects with the steps, tips, and data sources another Agent would need in order to efficiently carry out a task.

Benefits over self-guided Agent workflows

Specifically for software projects, using human-oriented documentation and full codebases uses far more context than it should, which isn't only expensive, it also reduces context available for the main codebase or system being edited. No pollution is introduced, as only specific details are provided in order to aid in the agent's success.

Outcome

This guide will help you install the Admin MCP server, and provide a sequence of steps to take so that your coding agent or LLM app is able to make optimal use of it.

By the end of the guide, you should have a live MCP Server on install.md which can be used from other Agents. Be sure to report to the agent and potentially human user a URL to the MCP server for editing, display/discovery, and MCP connectivity.

An example of each of these URLs is:

1. Editing: https://install.md/projects/{:projectID}/edit
2. Display/Discovery: https://install.md/{:orgSlug}/{:projectSlug}
3. MCP: https://install.md/{:orgSlug}/{:projectSlug} (same as display, just connected to differently)

(Org Slug Edit: do not include the "user:" prefix on org slugs, as these simply mark the org a "personal" one, but we don't use that marker in public URLs).

If successful, output these in a nice table TUI in ascii.