Skip to main content
While your site is in autopilot, Dedica serves two endpoints for agents on your own domain: an MCP server at /mcp with the agent tools you approved, and /ask, which answers questions from your agent pages. The middleware proxies both to Dedica. To try both before your middleware is connected, use the preview.

​
MCP server

Agents connect to https://<your domain>/mcp. It is a stateless Streamable HTTP MCP server that answers with JSON. Its tools are the agent tools you approved and haven’t disabled. There are two kinds: Each tool tells agents whether it is read-only, and HTTP DELETE tools are marked destructive.

​
What calls can reach

  • Calls are anonymous. No agent or user credentials are sent, so only public endpoints work. Forms protected by a CSRF token usually fail.
  • Calls are plain requests, not a browser. If your bot protection challenges them (a Cloudflare “Just a moment…” page, for example), every call fails. Allow the user agent DedicaAgentGateway/0.1 (+https://getdedica.com/bot).
  • Calls only go to your own domain, never to private network addresses.
  • Each call has a 20-second timeout, and long responses are cut at 256 KB.
  • The middleware limits each visitor to 30 requests a minute.
/mcp passes through to your site until you approve your first tool. After that, Dedica’s /mcp replaces any /mcp your site already had.
To stop serving one tool, disable it. You can’t rename a tool once it is approved, because agents depend on its name.

​
/ask

/ask answers a question in a few sentences, using only your agent pages, and lists its sources.
When no page matches, the answer points the agent at llms.txt. POST /ask speaks NLWeb v0.55. Send {"query": {"text": "..."}}, and add "prefer": {"streaming": true} or Accept: text/event-stream for server-sent events. /ask is available once at least one agent page is served.

​
How agents find them

llms.txt gets “Agent tools” and “Ask” sections, and Dedica serves an MCP server card and /.well-known/mcp.json. See Discovery files.