← usefulapi.io

INDIVIDUAL MCP TOOL

trengo_list_tickets

List tickets (conversations) visible to the token's user, newest activity first, with channel and latest message.

usefulapi.ionone authenticationAvailability not checked

LIVE ENDPOINT

https://trengo.usefulapi.io/mcp

No auth detected

Connect to this endpoint to inspect the live schema for trengo_list_tickets and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Potential side effects detected · medium confidence · heuristic, not a guarantee.

  • A tool name, description or schema mentions credentials.
  • A tool name or description suggests sending messages.

Parent server

usefulapi.io

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.trengo-mcp]
url = "https://trengo.usefulapi.io/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "trengo-mcp": {
      "type": "http",
      "url": "https://trengo.usefulapi.io/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: trengo-mcp
Remote MCP URL: https://trengo.usefulapi.io/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "trengo-mcp": {
      "url": "https://trengo.usefulapi.io/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "trengo-mcp": {
      "type": "http",
      "url": "https://trengo.usefulapi.io/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "trengo-mcp",
  "transport": "streamable-http",
  "url": "https://trengo.usefulapi.io/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • trengo_list_ticket_messages — List the messages of one ticket — inbound, outbound and internal notes — with the contact or agent behind each.
  • trengo_get_email_message — Fetch the full email behind one message of a ticket: original HTML body, from, to, subject and Message-ID.
  • trengo_list_contacts — List contacts, or search them by name, email or phone number.
  • trengo_get_contact — Fetch one contact with name, email, phone and custom field data, optionally with notes.
  • trengo_list_contact_groups — List the contact groups in the account — use their ids with trengo_update_contact.
  • trengo_list_users — List the agents (users) in the Trengo account — use their ids to assign tickets or filter.
  • trengo_list_teams — List the teams in the account — use their ids to assign tickets to a team.
  • trengo_list_labels — List the ticket labels (tags) in the account, for filtering tickets and reports.