GlytosGlytosdocs

MCP servers

The Model Context Protocol is how a system describes its tools to a model. If the software you want an agent to reach already speaks MCP - or you can put a small MCP server in front of it - that is the shortest path from your systems to a conversation, and it is the one the rest of the industry has converged on.

A tool of kind MCP calls one tool on one server. Add several to give an agent several.

Connecting one

  1. Under Tools, create a tool and choose MCP.
  2. Paste the server URL (streamable HTTP) and press Discover.
  3. Pick a tool from the list. Its name, description, argument schema and argument mapping are all filled in from what the server published.
  4. Add the tool to your agent.

Discovery is the point. A server describes its own tools, so nothing here should be transcribed out of a README - a schema copied by hand is a schema that will be subtly wrong on the one field nobody tested.

If the server needs authentication, put it in the headers field before pressing Discover; the same headers are used for discovery and for every later call.

Arguments

The arguments field maps what the server expects to what the model fills in:

{
  "order_id": "{{order_id}}"
}

{{order_id}} is replaced with the model's argument of that name at call time. Discovery writes this mapping for you, one entry per field in the server's schema. You can also pin a value by typing it directly instead of a placeholder.

What is allowed to be reached

An MCP server URL is treated like any other outbound target: it is resolved and checked before the connection, and the connection is pinned to the address that was checked. Private, loopback, link-local and cloud-metadata addresses are refused, so a server URL cannot be pointed at something inside the network boundary. An operator can allowlist a specific internal host if you genuinely run one.

A tool call is a network round trip inside a conversation, and the caller is waiting through it. Keep MCP tools fast, and prefer a server close to the agent's region.

MCP in the other direction

Glytos is also available as an MCP server, so an MCP client can drive your agents rather than the other way round. That is a separate surface; see the API reference.

MCP servers · Glytos Docs