adrmrn/tidio-mcp
If you are the rightful owner of tidio-mcp and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.
The Tidio MCP Server is a Model Context Protocol server that integrates with the Tidio customer service platform, providing a seamless interface for LLM clients like Claude Desktop.
Tidio MCP Server
A Model Context Protocol (MCP) server that integrates with the Tidio customer service platform.
It acts as a layer over the Tidio OpenAPI (REST API), making Tidio functionality available directly in LLM clients such as Claude Desktop.
Requirements
- Tidio Account — Tidio Plus plan (or higher)
- API Credentials — Client ID and Client Secret (see the authorization guide)
- Environment — Docker, or Python 3.13+ with uv
Setup
Option 1: Non-Technical Users (Claude Desktop + Docker)
You can quickly get started using the ready-to-use Docker image adrmrn/tidio-mcp
from Docker Hub.
-
Install and run Docker Desktop
-
Install and open Claude Desktop
-
In Claude Desktop, go to Settings → Developer → Edit Config, and open the
claude_desktop_config.json
file in a text editor -
Add the following configuration, replacing the placeholders with your Tidio credentials:
{ "mcpServers": { "Tidio": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "TIDIO_CLIENT_ID", "-e", "TIDIO_CLIENT_SECRET", "adrmrn/tidio-mcp:latest" ], "env": { "TIDIO_CLIENT_ID": "PASTE_YOUR_CLIENT_ID_HERE", "TIDIO_CLIENT_SECRET": "PASTE_YOUR_CLIENT_SECRET_HERE" } } } }
-
Save the file and restart Claude Desktop
Option 2: Technical Users (Python)
-
Clone this repository
-
Install dependencies with
uv sync
-
Copy
.env.example
to.env
and set your Tidio credentials -
Add the following configuration to your MCP client:
{ "mcpServers": { "Tidio": { "command": "uv", "args": [ "--directory", "/absolute/path/tidio-mcp", "run", "server.py" ] } } }
-
Restart your MCP client to apply the configuration
Available Tools
- Get Departments
- Get Operators
- Get Contacts
- Get Contact Details
- Delete Contact
- Get Tickets
- Get Ticket Details
- Create Ticket
- Update Ticket
- Delete Ticket
- Unassign Ticket
- Reply to Ticket
- Add Internal Note to Ticket
Planned Features / Missing Endpoints
- Pagination
- Filtering
The following endpoints are not yet implemented but are planned for future updates:
- Create contact (
POST /contacts
) - Create multiple contacts (
POST /contacts/batch
) - Update multiple contacts (
PATCH /contacts/batch
) - Update contact properties (
PATCH /contacts/{contact_id}
) - Get viewed pages history (
GET /contacts/{contact_id}/viewed-pages
) - Get contact properties (
GET /contact-properties
) - Get contact messages (
POST /contacts/{contact_id}/messages
) - Upsert products (
PUT /products/batch
) - Delete product (
DELETE /products/{product_id}
)
Contributing
Contributions are welcome!
If you’d like to improve this project, feel free to open an issue or submit a PR.
For development, the repository includes a Makefile
with handy commands to build, debug, and test the project.