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:

Frequently asked questions

What is Dock's MCP server card?
A static JSON file at `https://trydock.ai/.well-known/mcp/server-card.json` that catalogs every MCP tool Dock exposes (name, description, JSON Schema input). MCP indexers (Smithery, mcp.so, Glama, PulseMCP) crawl this without authenticating.
Where do I find Dock's MCP server card?
`https://trydock.ai/.well-known/mcp/server-card.json`. Standard well-known location per MCP spec. Returned with `application/json` content type, cacheable, no auth required.
Why does Dock publish a server card?
MCP indexer + listicle crawlers ingest server cards to surface your MCP server in their directories without requiring an account. Without a server card, you're invisible to that whole discovery surface; with one, you appear in every well-behaved indexer automatically.
Is Dock's server card the same as the runtime tools/list response?
Yes, byte-for-byte (modulo wrapper). Both come from the canonical `src/lib/mcp-tools.ts` registry. The card is static (good for crawlers); `tools/list` is dynamic over MCP. They cannot drift.
Can I see Dock's MCP server card without authenticating?
Yes. Server cards are unauthenticated by design (they're a discovery surface). Anyone hitting `/.well-known/mcp/server-card.json` gets the full tool catalog. Authentication is required at the actual `/api/mcp` endpoint.
What MCP indexers list Dock?
Live: Official MCP Registry (ai.trydock/dock), Glama (auto-ingested), Smithery (public), PulseMCP (weekly refresh). Queued: mcp.so (manual submission). DNS TXT on trydock.ai owns the ai.trydock namespace.
How often does Dock's MCP server card update?
On every deploy. The card is static-rendered from `src/lib/mcp-tools.ts` at build time; ships with the same Next.js build that ships the runtime MCP server. New tools appear in the card the moment they ship at `/api/mcp`.
Does the Dock server card include OAuth metadata?
Indirectly. The OAuth 2.1 + DCR endpoints live at `/.well-known/oauth-authorization-server` (the OAuth-spec well-known). The MCP server card focuses on tool catalog; OAuth discovery is a separate well-known per OAuth + MCP authorization spec. Learn more →
Can I get a list of Dock's MCP tools as plain text instead of JSON?
Yes, two options. `https://trydock.ai/llms.txt` lists every Dock tool concisely (~2KB, agent-friendly). `https://trydock.ai/llms-full.txt` is the full primer (~50KB) including system-prompt guidance. Both are crawler-safe. Learn more →
Why is Dock's MCP server card at well-known instead of /api/mcp/card?
Per MCP spec convention: server-card lives at the well-known path so crawlers know where to look without per-server configuration. Same convention as `/.well-known/oauth-authorization-server` for OAuth or `/.well-known/security.txt` for security policies.
Updated