← Registry

Learning Resources

zato.io

Provides tools to search, list sections, and retrieve content from Zato documentation.

1 endpoint3 known toolsFirst detected September 16, 2026Last detected September 16, 2026

ENDPOINT 1

https://zato.io/mcp

No auth detected

MCP server metadata

Name
Zato Docs
Version
4.1
Capabilities
loggingprompts.listChangedresources.listChangedtools.listChanged

Known tools 3

search_documentation

Search the Zato documentation using a text query.

Inferred read-only
get_document_content

Get the content of a specific documentation page.

Inferred read-only
list_documentation_sections

List all available documentation pages with their titles.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.zato-docs]
url = "https://zato.io/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "zato-docs": {
      "type": "http",
      "url": "https://zato.io/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: zato-docs
Remote MCP URL: https://zato.io/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "zato-docs": {
      "url": "https://zato.io/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "zato-docs": {
      "type": "http",
      "url": "https://zato.io/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "zato-docs",
  "transport": "streamable-http",
  "url": "https://zato.io/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.