Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.tattoo.dev/llms.txt

Use this file to discover all available pages before exploring further.

​
Mintlify Docs MCP

Mintlify exposes a read-only documentation MCP endpoint at: 
https://docs.tattoo.dev/mcp
Use this MCP when an agent needs to read the public TattooAPI docs, search current API guidance, or ground code generation against published documentation.

​
What It Is For

  • Reading the current public docs.
  • Helping Studio OS, tattoo.co, or integration agents understand the documented API posture.
  • Searching endpoint guides, authentication notes, and surface-map pages.
  • Keeping external coding assistants aligned with docs.tattoo.dev.

​
What It Is Not For

  • It is not the TattooAPI Ontology Guidance MCP.
  • It is not a source-pack upload channel.
  • It is not a Convex, Mastra, or runtime admin endpoint.
  • It cannot grant write access or bypass WorkOS actor mapping.
  • It must not be used as the canonical source for unpublished internal PRDs.

​
Relationship To The Ontology Guidance MCP

TattooAPI has two different MCP concepts:
MCPPurposePublic?
Mintlify Docs MCPRead published docs from docs.tattoo.devPublic docs read surface
Ontology Guidance MCPInternal ontology/source-pack guidance for acquisition and refinement agentsInternal WorkOS-protected surface
The Mintlify MCP helps agents understand what the docs say. The Ontology Guidance MCP helps internal acquisition/refinery agents map data to TattooAPI ontology contracts.

​
Agent Instruction

When using this MCP, agents should treat the docs as current public guidance, then verify sensitive claims against repo verifiers before changing production behavior. Recommended guardrails:
  • Do not infer public writes from archived examples.
  • Do not treat internal source-pack or Mastra routes as public product surfaces.
  • Do not expose WorkOS secrets, Convex admin keys, Sanity tokens, or local Tailscale URLs.
  • Prefer https://api.tattooapi.com/v1 in examples unless a private integration explicitly requires another host.