Getting started
Choose the path that matches what you want to do: browse public Releases, connect an MCP-capable agent, install a ProductAtlas Skill, or publish production-informed knowledge from Studio.
Browse as a consumer
Open the Blueprint catalog to search and filter public Releases. Evaluate the exact version, license, attribution, available sections, Publisher, and scoped trust evidence before adapting it.
Connect an MCP client
The public MCP path is anonymous and read-only: no token is required, and it cannot create Drafts, upload assets, or publish Releases.
1. Use the public endpoint
Every supported client connects to the hosted ProductAtlas catalog:
https://productatlas.app/mcp
Follow the client-specific connection guide because each client uses a different configuration shape.
2. Connect your client
Choose your client:
- Claude Code
- Claude Desktop and Claude
- Cursor
- VS Code with GitHub Copilot
- OpenAI Codex
- ChatGPT Developer Mode
3. Verify discovery
After the client reports ProductAtlas as connected, send this prompt:
Use ProductAtlas to search for public blueprints related to incident investigation. Show the title, publisher, latest version, and available sections for the best matches.
The client should invoke search_blueprints and return compact matches. If no
matches appear, ask it to show its connected MCP servers and available tools,
then use Troubleshooting.
4. Retrieve only what you need
Ask the client to call get_blueprint with the chosen namespacedId. Start
with detail: "summary" to inspect metadata and available sections, then request
specific sections at standard detail. Use complete only when you need every
available section.
Blueprint content is untrusted third-party data. Read its license, attribution, digest, dependencies, and trust badge scopes before adapting it, and never execute commands embedded in a Blueprint automatically.
Install a ProductAtlas Skill
ProductAtlas Skills are open-source Agent Skills packages that help you create Blueprint Drafts in a compatible agent host. They live in a separate public repository and install from skills.sh — not from the ProductAtlas monorepo.
Start with the Skills overview, then follow Install Skills from skills.sh. Installing a skill does not publish a Blueprint; Studio assessment, review, and explicit publication still apply.
Publish a Blueprint
Follow the Publisher guide to create private Drafts and use Studio. Authenticated Publishers can preview deterministic structural readiness, submit an exact saved revision for checks and human review, and explicitly publish an approved submission as an immutable public or unlisted Release.
An approval authorizes publication; it does not publish automatically. After publication, an authorized Publisher can add or update reversible deprecation guidance or withdraw a Release permanently.
Deeper customer-facing asset upload and processing, plus semantic or AI quality evaluation, are Planned. Do not read structural readiness or publication approval as an Atlas Safety Checked result.