Developer Tools

synkro.sh

Searches and queries Synkro documentation, code examples, and API references.

1 endpoint2 known toolsFirst detected May 11, 2026Last detected May 30, 2026

ENDPOINT 1

https://synkro.sh/docs/mcp

No auth detected

Known tools 2

search_synkro

Search across the Synkro knowledge base to find relevant information, code examples, API references, and guides.

Inferred read-only

query_docs_filesystem_synkro

Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the Synkro documentation pages and OpenAPI specs.

Potential side effects

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.synkro-sh]
url = "https://synkro.sh/docs/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "synkro-sh": {
      "type": "http",
      "url": "https://synkro.sh/docs/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: synkro-sh
Remote MCP URL: https://synkro.sh/docs/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": {
    "synkro-sh": {
      "url": "https://synkro.sh/docs/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "synkro-sh": {
      "type": "http",
      "url": "https://synkro.sh/docs/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "synkro-sh",
  "transport": "streamable-http",
  "url": "https://synkro.sh/docs/mcp"
}

MCP Inspector

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

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for synkro.sh was fetched 2026-08-04T21:01:09.198Z and is being refreshed.

Trust status Neutral

synkro.sh is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

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