Connectors
Connect apps and MCP servers, choose which agents may use them, set each action to allowed, ask first or off, and review every tool call.
Connectors let agents work in your other tools: read a GitHub repository, post to Slack, update a CRM, call your own MCP server. You decide which agents may use each connection and what each action may do. Nothing is shared by default.
Connect an app
You need the Manage connections permission (tools:manage_connections).
- Open Connectors and choose an app from the catalog.
- Pick a sign-in method the app supports: sign in with the provider, an API key, or an MCP server address.
- Choose the identity: your personal account, or a shared account for the organization.
- Choose which agents may use the connection: all agents, or selected ones.
- Complete sign-in. Provider sign-in opens in a separate window and returns you to the setup.
Save & exit keeps an unfinished setup; Finish setup on the app returns to it.
Your own MCP server
Choose Connect with a link, paste the server's URL, and follow the sign-in or key prompt the server asks for.
Action permissions
Each connection lists its actions (tools). For every action choose:
| Setting | Effect |
|---|---|
| Allowed | Agents with access may call it. |
| Ask first | Each call waits for a person to review the exact arguments and approve or decline. |
| Off | Agents cannot call it. |
New actions that appear when an app changes start quarantined until you review them.
Review a request
When an agent calls an Ask first action, a review appears in the task and in Connectors › Review. It shows the redacted arguments. Choose Approve & run (this call), Always allow (change the setting for this scope), or Decline. Declining declines that call only; it does not change the setting.
Test an action
On the connection's Permissions tab, use the test control to run an action as a chosen actor with your inputs and see the real result. Use it to confirm access before you rely on it.
Activity
Every tool call is recorded: who called it, from which task, with what result, and any provider error. Open the connection's Activity tab, or Observability › Connector calls for all connections at once.
Tasks that need a connection
When an agent needs a connection it does not have, it asks for one in the task. The person named in the request sets it up from the task; when access works, the agent continues.
From the API
See Connectors, Connection requests and MCP gateway in the API reference. To let an outside assistant use Veyra itself over MCP, see MCP.