mcps, in the same place as
tools and kb_ids. Being part of the config means it is frozen at publish like
the rest of it: attaching an integration takes a publish before a call sees
it.
Channel integrations deploy an agent to a messaging channel. Telegram is the
only one. It is never attached to an agent config — you bind it with a
trigger, which points an inbound event at a published
text agent.
Every provider
That is the whole list. There is no way to reach a service that is not on it
except as a custom MCP server. Full detail — setup
fields, defaults, provider keys — is in the catalog.
OAuth providers must be connected from the dashboard, because the flow is a
browser redirect. The other four take their credentials on create through the
API. Both paths are in connecting an integration.
What is frozen and what is live
The attachment is config, so it freezes at publish. The approval is not. Which of a server’s tools an agent may call is the integration’sallowed_tools, and that list is read fresh at the start of every call.
Narrowing it reaches every already-published agent on its next turn — no
republish, no version bump, nothing to redeploy. So does disabling the
integration, which drops its tools out of running agents entirely.
The asymmetry is deliberate: adding capability to a live agent should be a
deliberate publish, and taking it away should be immediate.
Next
Catalog
Every provider, what it needs, and what it gives an agent.
Connecting
OAuth from the dashboard, API keys through the API, and what each status means.
MCP servers
Attaching to an agent, approving tools, and the namespace rules.
Triggers
Binding an inbound Telegram message to a published text agent.