Trengo connection settings

Configure authentication, check the connection and explore available tools.

MCP Connect by Apideck

Host setup required

Add https://mcp.trengo.com/mcp as a remote MCP server, choose OAuth and complete Trengo sign-in and consent. A Trengo account is required; no API key or pre-created administrator app is needed. The assistant registers when connecting. Review actions that send messages or change data. Account permissions and tool execution have not been runtime-tested by API Tracker.

Publisher setup documentation →

2 sources

Claude connector directory · Claude tier: community · 2026-11-01
API Tracker · publisher documentation · 2026-11-01

Source-declared authentication: oauth2. Publisher affiliation and successful connection are not inferred.

MCP Connect by ApideckYour setup · 0 selected ↓

Choose your connections

Search the cloud catalog across registries.

Catalog coverage

Search MCPsSourcePublisher

Searching the cloud catalog…

Your agent’s setup

0 servers selected

Build your tool stack

Add servers from the catalog. Your configuration appears here.

Choose your editor

VS Code.vscode/mcp.json

{
  "servers": {}
}

Merge this configuration into .vscode/mcp.json.
Open VS Code and start each server from its MCP settings.
Complete the publisher’s authentication flow if prompted.

Selection does not connect an account. Authentication and tool execution happen in your client. Some servers require additional setup from their publisher.

VS Code setup guide ↗

Connection guides: setup fields, authentication and publisher evidence →