MadeWithStack publishes a hosted MCP server at /mcp. It exposes the directory as a small, stable tool surface for agent runtimes that support native MCP tool calling.
Endpoint
- MCP endpoint:
https://www.madewithstack.com/mcp - Transport: Streamable HTTP
- Protocol version:
2025-11-25 - Discovery manifest:
/.well-known/agents.json
Supported capabilities
This v1 server is intentionally narrow:
- tools only
- no prompts
- no resources
- no sampling
- no elicitation
- no session management
- no SSE stream endpoint
GET /mcp and DELETE /mcp return 405. Use POST /mcp for MCP JSON-RPC requests.
Initialization flow
- Send
initializewith protocol version2025-11-25. - Send
notifications/initialized. - Call
tools/listortools/call. - Include the
MCP-Protocol-Version: 2025-11-25header on post-initialization requests.
Tool inventory
The hosted MCP server currently exposes these tools:
list_toolssearchlist_productsget_productsubmit_product
Those tools stay parallel to the public REST API. Input names and structured outputs are intentionally close to the existing /api/v1 contracts so clients can move between REST and MCP without rewriting business logic.
Error model
- MCP protocol errors are reserved for malformed JSON-RPC requests, unsupported methods, and bad protocol negotiation.
- Tool failures return normal tool results with
isError: true. - Structured error payloads include
error_code,message, andretry_after_secondswhen applicable.
Rate limits and trust model
- Read tools inherit the current anonymous catalog and search limits.
submit_productinherits the public submission limits and duplicate protection rules.- Accepted submissions enter manual editorial review. MCP submission does not bypass curation or publish instantly.
Security notes
- HTTP requests with invalid
Originvalues are rejected. - Pending review status remains gated by submitter email on
get_product. - Treat the directory as a trust-first system: a listing is reviewed before publication, and tool access does not weaken editorial control.