I already have an agent
Connect an MCP client, read answers and receive follow up tasks.
Pages, forms, bookings, chat and optional meeting memory, through one tool registry, a REST API and an MCP connection.
Connect an MCP client, read answers and receive follow up tasks.
Use API keys with specific scopes on your backend, and keep secrets on the server.
A hosted pilot reads authorized results and prepares drafts, with activation and credits.
A link tool, a form tool and a calendar tool, each with its own auth, its own errors and its own idea of permissions.
Your agent ends up with too much access or not enough tools.
The same tools appear in MCP, the REST API and the in app agent, with strict inputs and errors that say what to do next.
“Connect to instanceof.ai and list what you can do here.”
Connected over MCP with a scoped key
Found the installed apps
Listed the tools this key may use
One connection reaches every installed product, within the scopes you grant.
An unknown field is an error, never silently dropped.
Agents request apps and permissions; owners approve them.
It depends on the client's version and configuration. Read the guide before connecting.
In the developer guide, llms.txt for agents, and an OpenAPI description of every endpoint.
No. MCP connects tools to an agent that is running. It does not start one.
Yes, with scoped API keys kept on the server.