MCP Servers
MCP Servers host an HTTP Model Context Protocol endpoint for your workspace. External clients (for example Cursor) call selected Vettero resources as MCP tools. You choose what to expose and require a request auth token on every call.
This is distinct from MCP Integrations (outbound clients to external MCP URLs) and from Studio MCP under Workspace Settings (Studio builder tools for editing the workspace).
When to use
- Let an external MCP client run workspace agents, APIs, queries, or knowledge-base tools
- Publish a curated, authenticated tool surface instead of sharing full app access
- Prefer secrets in environment variables for the request token
Create an MCP server
Open Configuration → MCP Servers and choose Add MCP Server.
| Setting | What it does |
|---|---|
| Name | Required display name |
| Description | Optional notes |
| Enabled | When off, the endpoint rejects traffic |
| Request token | Bearer / API-key secret clients must send — literal value or env.* |
After create, open the server to copy the endpoint URL and manage exposed tools.
Configure exposed resources
Choose Configure resources and pick tools by category:
| Category | What you expose |
|---|---|
| Blocks / Services | System and connected-service integration blocks |
| WhatsApp Templates | Selected WhatsApp templates |
| Agents | Agents |
| Functions | Functions |
| Workflows | Workflows |
| Api | Operations from API schemas |
| KB | Knowledge base query tools |
| Query | Queries |
| MCP | Tools from MCP Integrations |
Each exposed tool needs a valid MCP tool name: lowercase letters, digits, and underscores; must start with a letter or _; max 64 characters; unique across categories on that server.
Authenticate clients
Clients send the configured request token (Bearer or X-Api-Key, depending on client support). Prefer:
env.MCP_AUTH_TOKEN
over embedding a raw secret in the server record. See Environment Variables.
Limits
- Disabled or deleted servers stop external access immediately.
- Only the resources you explicitly expose are available — nothing else in the workspace is reachable via that endpoint.
Where MCP servers are used
| Place | How |
|---|---|
| External MCP clients | HTTP endpoint + auth token |