> ## Documentation Index
> Fetch the complete documentation index at: https://explore.airia.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Airia Deployed Agents

Airia Deployed Agents is different from the rest of the catalogue: instead of connecting to an outside app, it connects to your own tenant. It turns agents you've built in Airia Studio into individual MCP tools, so anything that speaks MCP, another Airia agent, Claude Desktop, Cursor, or any other MCP client, can call them directly.

Airia Deployed Agents is a Featured catalogue server, so it's pinned near the top of the server picker when you're building a Gateway or Deployment. Like any catalogue server, an admin can still restrict or remove it for your organization through [Server Management](/mcps/admin-controls/server-management).

## Prerequisites

* At least one agent with an **Active version** published.
* That agent's **Tool & MCP** interface turned on. See [Tool & MCP Interface](/building-and-deploying-agents/interface-options/tool-interface) for how to set that up, including naming your tool, writing a description, and optionally defining input and output schemas.

An agent that doesn't have the Tool & MCP interface enabled simply won't show up as a tool through this server. You don't need to touch anything on the Gateway or Deployment side to add or remove an agent; it's picked up automatically as soon as you enable or disable the interface on the agent itself.

## Connecting Airia Deployed Agents

Add it to a Gateway or Deployment the same way as any other server (see [Gateway/Deployment Creation](/mcps/admin-controls/gateway-deployment-creation)), then choose one of two authentication options:

* **Passthrough (recommended):** Airia forwards your own sign-in to the server, so tool calls run as you, with your existing permissions. There's nothing else to configure.
* **API key:** Generate a key from **API Keys** in your account settings and paste it in during setup.

<Note>
  Whichever method you use, the agents that show up as tools depend on the access level behind that connection. Two people connecting through the same Gateway with passthrough auth may see different tools if their permissions differ.
</Note>

## What You Can Do With Airia Deployed Agents

Once connected, any agent you've exposed through the Tool & MCP interface becomes a callable tool with:

* A name and description you defined, so callers know what it does and when to use it.
* An input schema, either the default single-input format or a custom one you defined, so callers know exactly what to send.
* Automatic version management: calling the tool always runs the agent's latest published version, so republishing an agent updates the tool immediately without touching your Gateway or Deployment configuration.

This works in both directions. Point an external MCP client like Claude Desktop or Cursor at a Gateway that includes this server, and your deployed agents show up as tools it can call. Or add it to a Deployment and use one Airia agent as a tool inside another, without leaving the platform.

## Conversation Memory and MCP Sessions

If an agent you're calling this way uses conversation-scoped memory (for example, to remember a chat ID or thread across turns), that continuity is tied to the MCP connection itself rather than anything you have to pass in. As long as the calling client keeps the same session open, repeated tool calls share the same conversation memory.

<Warning>
  If the calling client disconnects and reconnects, that counts as a new session, so conversation-scoped memory starts fresh. This is expected: it mirrors how a new chat session in Airia itself wouldn't carry over memory from a previous one either.
</Warning>

If you need memory that survives reconnects, use **User-specific** or **Global** scoping instead of Conversation-scoped. See [Memory](/building-and-deploying-agents/agent-basics/memory) for the full breakdown of scoping options.

## Learn More

* [Tool & MCP Interface](/building-and-deploying-agents/interface-options/tool-interface)
* [Managing Agent Interfaces](/building-and-deploying-agents/interface-options/managing-interfaces)
* [Gateway/Deployment Creation](/mcps/admin-controls/gateway-deployment-creation)
* [Memory](/building-and-deploying-agents/agent-basics/memory)