MCP Tools

Vertesia agents can use tools provided by external MCP (Model Context Protocol) servers. MCP servers are configured in application manifests and their tools become available to agents alongside built-in and custom tools.

How It Works

An application manifest declares one or more MCP servers in its tool_collections array.
When the application is installed on a project, the MCP tools are discovered and made available to agents.
Tool names are prefixed with the configured namespace to avoid collisions (e.g., a tool named search with namespace crm becomes crm_search).

OAuth Authentication

Many MCP servers require OAuth 2.0 authentication. Each user must connect their account before an agent can use the MCP tools on their behalf.

Connecting

Users connect from the new agent form in the Agent Runner interface. The form displays connect actions for any MCP tools that require authentication. Users must connect before starting the agent.

Tokens are stored securely and refreshed automatically. If a refresh token expires or is revoked, the user will need to reconnect.

Configuration

MCP servers are configured in application manifests, not in the Agent Runner directly. See MCP Servers for the full configuration reference including:

Required and optional fields
OAuth setup with dynamic client registration or pre-configured credentials
Namespace configuration
Complete manifest examples