Your assistant, connected.
agoramcp speaks the Model Context Protocol over Streamable HTTP. We offer two kind of MCP servers, country-level and specific source-level servers.
Country-level servers group all the available sources for the given country under one roof, whilst source-level servers are dedicated to a single source for more specific questions and research.
Connect your agentAddress shape
A whole country:
/{country}/mcp
Every registry agoramcp mounts for that country, behind one connection: Greece answers at /gr/mcp. Tool names carry the registry that answers them, so diavgeia_get_decision is unambiguous the moment a second source lands beside it.
One source:
/{country}/mcp/{source}
A single registry on its own. For example /gr/mcp/diavgeia is the register every Greek public body publishes its decisions in, and its tools keep their plain names: get_decision. A narrower surface is one a model chooses better within.
How it works
What happens between a client opening the address and an answer landing in the model's context: the same steps on a country server and on a single source.
- 1.
Connect
The address speaks Streamable HTTP and holds no session. Every request stands alone: a fresh server answers it and is gone once the reply is sent, so two clients on one address never see each other.
- 2.
The briefing
On connecting, the model is told what it has reached: the registry, who publishes it, its licence and how to attribute it. The country server adds a map of tool prefixes to registries (diavgeia_* is Diavgeia), so a question is routed without a call spent finding out.
- 3.
The tools
tools/list hands over every tool, each with a typed schema for its arguments and a line on what it answers.
- 4.
The call
tools/call runs the source's own handler against the upstream registry, through a cache whose lifetime the source sets per tool. What comes back is the registry's records, shaped for a model to read, as JSON.
- 5.
When it goes wrong
A bad argument or an upstream that is down comes back inside the tool result, marked as an error, so the model reads it and corrects itself. The protocol envelope stays intact and the turn goes on.
The server is a read-only proxy. It cannot write to a registry, and it returns only what the registry publishes. Where a question falls outside the tools, the model is told to say so rather than guess.