Get startedCLIAPIMCPWebDesktopAgentsSupportBillingChangelog
MCP · Reference

Server card

Static JSON catalog of every MCP tool Dock exposes, published at a well-known path. For tool-discovery pipelines (LangChain, CrewAI, custom orchestrators) that prefer pulling a static file over live-scanning the MCP endpoint.

URL

https://trydock.ai/.well-known/mcp/server-card.json

Public, no auth required, cached at the edge for 5 minutes. Re-published whenever the tool catalog changes (new tool, removed tool, signature change).

Shape

{
  "name": "Dock",
  "url": "https://trydock.ai",
  "mcp": {
    "endpoint": "https://trydock.ai/api/mcp",
    "auth": {
      "type": "oauth",
      "discovery": "https://trydock.ai/.well-known/oauth-authorization-server"
    }
  },
  "tools": [
    {
      "name": "list_workspaces",
      "description": "List every workspace the caller can access.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "archived": { "type": "boolean", "default": false }
        }
      }
    },
    ...
  ],
  "version": "2026-04-30",
  "publishedAt": "2026-04-30T22:14:00.000Z"
}

Why a static catalog instead of MCP discovery

  • No auth required to look. Tool-discovery pipelines can plan integrations without first signing users in.
  • Cacheable. CDN-cached. No backend hit per discovery request.
  • Diff-friendly. Two versions of the file are easy to diff for "what changed in MCP today" tooling.
  • Standard location. /.well-known/mcp/server-card.json mirrors the OAuth + Web App Manifest patterns most discovery tools already crawl.

Freshness

The static card lags the live MCP endpoint by at most 5 minutes (CDN cache). For tools that need exact freshness, use tools/list on the live endpoint instead.

The full agent-fetchable set

Dock publishes four agent-readable artifacts at well- known paths. The server card is one of them: