Skip to main content

​
Mintlify Docs MCP

Mintlify exposes a read-only documentation MCP endpoint at:
Use this MCP when a private tool 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 tools 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 private ontology guidance layer.
  • It is not a source-pack upload channel.
  • It is not a runtime admin endpoint.
  • It cannot grant write access or bypass TattooAPI actor mapping.
  • It must not be used as the canonical source for unpublished internal PRDs.

​
Relationship To Private Ontology Guidance

TattooAPI has two different guidance concepts: The Mintlify MCP helps tools understand what the docs say. Private ontology guidance helps internal acquisition/refinery tools map data to TattooAPI ontology contracts.

​
Tool Instruction

When using this MCP, private tools 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 private worker routes as public product surfaces.
  • Do not expose secret values, admin keys, approved-storage tokens, or local private network URLs.
  • Prefer https://api.tattooapi.com/api/v1 in examples unless a private integration explicitly requires another host.