Integrations

MCP Integrations

Connect outbound to external MCP servers and use their tools in agents.

MCP Integrations connect your workspace outbound to an external Model Context Protocol server (Streamable HTTP). On save or test, Vettero syncs and caches the remote tool catalog so agents can call those tools.

This is the opposite of MCP Servers, which host workspace resources for external clients. Integrations consume someone else’s MCP endpoint.

When to use

Give agents tools from a third-party or self-hosted MCP server
Re-sync when the remote tool list changes
Reach OAuth-protected MCP endpoints

Add an MCP integration

Open Integrations → MCP Integrations and choose Add Integration. A wizard opens on the same page.

Enter the Server URL (for example https://example.com/mcp).
Choose Auth (None, Token, or OAuth).
Confirm Name and Description (filled from the remote server when the connection works).
Review the tools, then Create. The integration detail page opens.

The detail page is read-only. Edit on the name card changes the display name and description. Edit on Connection opens a dialog for server URL, enabled, and auth. Activity shows outbound tool calls when agents or MCP use this integration. Changing the integration is also recorded in the workspace audit log.

OAuth is authorized from the details card after create (Authorize). Use Test connection to refresh Cached tools.

Setting	What it does
Name	Required display name
Description	Optional notes
Server URL	MCP endpoint (for example `https://example.com/mcp`)
Enabled	When off, agents cannot use the integration’s tools
Auth	None, Token (Bearer), or OAuth

Prefer storing bearer tokens in environment variables when the UI allows env.* bindings.

Tools are synced when you Create, save Connection, or Test connection. Agents use that snapshot until you save connection or test again.

Limits

Protocol expected: Streamable HTTP MCP (as shown in the product UI).
OAuth integrations must be created before authorize; sync after OAuth succeeds.
Disabling or deleting the integration removes those tools from agent discovery.

Details and activity

Open an integration from the list to see Setup and Activity.

Tab	What you see
Setup	Name, description, server URL, auth type (not secret values), enabled, last sync, and the cached tool list. Name/description and connection (URL, enabled, auth) each have their own Edit dialog.
Activity	Outbound tool calls (tool name, status). Arguments and credentials are not stored. Create/update/delete stays in the audit log.

Where MCP integrations are used

Place	How
Agents	Tools under MCP
MCP Servers	Optional re-export as `mcpIntegrations`

APIs

Import OpenAPI schemas so agents and MCP can call REST operations.

Chat Integrations

Embed agents and chat workflows on the web, or expose them as in-app sidebar chat.