MCP Client (User-Hosted MCP Server)

MCP Client is available on the ENTERPRISE subscription tier only (the dashboard and API both enforce this).

Voxe configures the workflow’s MCP Client connection to call a server you operate (HTTPS endpoint). This is not a Voxe-hosted MCP product.

Requirements

• ENTERPRISE plan
• A workflow that is fully provisioned for MCP connections (only eligible workflows appear in the picker)
• A reachable MCP endpoint URL (http:// or https://)

Setup

• Dashboard → Integrations → Add Integration → MCP Client
• Select workflow — MCP is applied to that workflow only
• Endpoint — e.g. https://your-mcp-server.example.com/mcp
• Authentication (pick one):
• None
• Bearer Auth — bearer token
• Header Auth — header name + value
• MCP OAuth2 — client ID + client secret (full OAuth flows depend on your MCP server; ensure your server supports what you configure)
• Multiple Headers Auth — headers payload as configured in the UI
• Test when available, then Save

On save, Voxe creates or reuses a secure credential for auth, attaches it to the workflow’s MCP Client connection, and stores integration metadata in your account.

Security behavior

• After saving, secret fields are masked as __REDACTED__ in the UI and API responses
• Re-saving without changing masked fields keeps the previous secrets
• Deleting the integration removes workflow configuration and deletes its stored MCP credential

Use Business Data Integrations for native WooCommerce, Shopify, HubSpot, Salesforce, and Pipedrive tools; use MCP Client when you need custom tools exposed via your own MCP server (for example, your own n8n MCP Trigger endpoint).