MCP & Agent Discovery
Tanzanite publishes standard, machine-readable descriptors so autonomous agents can discover the platform, understand its capabilities, and act on it without a human writing integration code.
Discovery files
Section titled “Discovery files”| File | Purpose |
|---|---|
/llms.txt | Condensed, link-rich index of the documentation for LLMs |
/llms-full.txt | The full documentation concatenated into one document |
/openapi.json | The REST API contract (OpenAPI) |
/.well-known/mcp.json | MCP server discovery for public integrations |
/.well-known/agents.json | Agent discovery descriptor |
/.well-known/agent.json | Google A2A agent card |
Markdown content negotiation
Section titled “Markdown content negotiation”Every documentation page has a clean Markdown twin. Request any page with an
Accept: text/markdown header and you’ll receive Markdown instead of HTML:
curl -H "Accept: text/markdown" https://docs.tanzanite.dev/connecting/overview/Each HTML page also links its alternate via
<link rel="alternate" type="text/markdown" ...>, so crawlers can find the
Markdown without guessing.
Tanzanite supports the Model Context Protocol so agents and MCP-aware clients
can connect to it as a tool server. The descriptor at
/.well-known/mcp.json advertises the server endpoint
and metadata; point an MCP client at it to enumerate available tools.
A2A (agent-to-agent)
Section titled “A2A (agent-to-agent)”For agent-to-agent interoperability, the A2A agent card at
/.well-known/agent.json describes Tanzanite as an
agent another system can delegate work to.
Next steps
Section titled “Next steps”- Start building with the SDK Quickstart.