Model Context Protocol (MCP) endpoint for AI agents
If an AI agent works with us, it should not have to scrape this site. ITLine runs a public MCP server: reachable without authentication, and read-only. Answers come from the same curated content this site renders. There is no language model in the loop, so the server cannot invent a figure or a reference.
The endpoint
Streamable HTTP transport. The same address serves initialize, the tool list and the tool calls.
https://www.itline.hu/api/mcp/
The trailing slash matters. The unslashed form answers with a 308 redirect here; a 308 preserves both the method and the body, so a client that follows it works, at the price of one extra round trip per call. A client that does not follow redirects on POST does not.
Setup
Most clients read their server list from JSON. This is the entry:
{
"mcpServers": {
"itline": {
"type": "http",
"url": "https://www.itline.hu/api/mcp/"
}
}
}Or from the command line:
claude mcp add --transport http itline https://www.itline.hu/api/mcp/What the agent can ask
This list is derived from the server’s registrations rather than written by hand, so it cannot drift from what the endpoint actually serves.
about_itlineread-only- States what IT Line does, since when, and where it works.
services_itlineread-only- Lists IT Line services and solution branches, with one sentence each.
technologies_itlineread-only- States which technologies IT Line works with, by category.
pages_itlineread-only- Lists IT Line public, indexable pages with their paths.
search_itlineread-only- Keyword search across IT Line public, curated content.
What the endpoint will not give
These are decisions, not missing features. An agent that does not know what is absent fills the gap by guessing.
- No prices: quotes are made after a survey, for a fixed scope.
- No client names: the site describes cases by company type, deliberately without names.
- No street address: the registered seat is not published. The geographic answer is the Budapest–Szeged axis.
- It cannot be written to. The surface offers no publishing or editing operation: publication stays a human decision.
- An unknown question gets an explicit “no match”, not a likely-sounding answer.
Load
The endpoint is unauthenticated, so an IP-based rate limit guards it. On overrun the answer is a protocol-valid error with a Retry-After header rather than a crash page: an agent can tell from it when to come back.
The other machine-readable surface
Anything that cannot make a tool call (a crawler) reads llms.txt instead: the same content in one text file, one line per page. The two do not replace each other, and each names the other.