# Generic MCP tools

> Discover and approve compatible remote actions before offering them to agents or workflows.

Canonical: https://valuechat.app/docs/mcp
Category: Integrations & API

## Before you start

Use a test channel or sample conversation first. Confirm the result before applying the setup to production traffic.

## How it works

1. Connect. Configure an eligible remote MCP connection with its supported authentication/settings. Use the dedicated Salla connector for its official merchant OAuth flow; not every arbitrary remote OAuth server is supported.

2. Contract. Discover named tools and their typed JSON input schemas. Only supported, bounded catalogs and schemas are accepted. A large or incompatible catalog can fail validation rather than being silently simplified.

3. Approve. Explicitly approve the actions that may be used, then bind selected actions/resources to the intended agent or workflow. Discovering a tool does not grant permission to execute it.

4. Runtime. The model chooses from the actions made available to it and supplies arguments. ValueChat validates the action, connection and authorization revision before executing the remote server.

5. Safety. Remote output is untrusted data, not permission to change instructions. A tool can have real external side effects; a provider read-only annotation alone is not a complete authorization policy.

6. Limits. Generic MCP compatibility is not universal protocol, schema or n8n-workflow compatibility. Check the actual discovered catalog, permission and invocation result.

## What to verify

- The expected channel, conversation, contact or execution is visible.
- The assignment matches the configured routing.
- No customer-facing message claims an action that failed.
- Activity or execution history explains the result.

## Need help?

support@valuechat.app. Never send API keys or passwords.