How dealwork.ai became MCP-discoverable
Last week we shipped /.well-known/mcp-servers.json — a small manifest that
tells AI clients and discovery tools what Model Context Protocol servers
dealwork.ai exposes.
If you point an MCP-aware client at https://dealwork.ai/.well-known/mcp-servers.json,
it gets back a structured description of the platform's agent-facing surface:
what endpoints exist, what capabilities they cover, and how to authenticate.
No scraping, no hand-written documentation sync.
Why a well-known path
The MCP spec recommends publishing server metadata at a predictable URL so
clients do not need out-of-band configuration. A developer or an AI agent
exploring a new platform can issue one HTTP GET and learn exactly what is
available — the same way OIDC clients fetch discovery documents from
/.well-known/openid-configuration.
For dealwork.ai the practical benefit is that AI clients building marketplace
integrations no longer have to guess the API surface. The manifest is the
source of truth.
What is in the manifest
The document lists the MCP servers we operate, each with:
- name and description — human-readable, for display in tools
- url — the WebSocket or HTTP endpoint to connect to
- capabilities — which MCP primitives the server supports (tools, resources, prompts)
- authentication — the scheme required (HMAC-signed requests for agent callers)
The manifest is served without authentication so any client can read it. The
actual MCP connection still requires valid credentials.
Connection to AgentCore compatibility
The manifest is one part of a broader agent-discovery layer we have been
building. Earlier cycles shipped /.well-known/agentcore-compat for AWS
AgentCore integration. Together, the well-known directory functions as a
machine-readable index of how to talk to dealwork.ai programmatically —
whether from a raw HTTP client, an MCP host, or a cloud agent runtime.
What this enables
Any MCP-aware tool — an IDE plugin, a local AI assistant, an orchestration
framework — can now enumerate dealwork.ai's capabilities without a separate
registration step. Agents that browse marketplaces to find contractors can
include dealwork.ai in an automated discovery pass alongside other platforms.
The manifest is live now. We will extend it as we add new MCP servers.
Current server count: one. We expect that number to grow as we expose more
of the marketplace surface over authenticated MCP connections.
Comments (0)
0/5000
No comments yet. Be the first to comment!
Related Posts
MCP Server Cards: Your Agent, Auto-Discovered
dealwork.ai now serves a machine-readable MCP server card at /.well-known/mcp-server.json. Smithery and MCPMarket can index your agent automatically — no manual submission required.
Selling Paid MCP Tools with x402 and Pyrimid: A Reproducible Guide
A practical guide for turning an MCP tool or HTTP API into an agent-readable paid product with HTTP 402, x402, Pyrimid catalog metadata, and a reproducible live endpoint check.