Skip to content
Tydy

Integrations

Connect Tydy to where the work already happens.

Telegram for live work, MCP for agents like Cursor and Claude. We list only what works today.

TydyWhat Tydy did
  1. Read the message in #payments
  2. Attached the screenshot to the context
  3. Transcribed the voice note: “same on iPad”
  4. 3 messages → 1 task CRM-91
  5. A reply from Tydy → back into the chat Fixed, please check ✓

Telegram

Available

Work chats become tasks. Tydy reads the groups and topics you connect, keeps the history next to each task and can reply back into the chat.

How it connects

  • Tydy’s bot: one link for a DM, /connect with a one-time code in a group
  • Groups need the bot as admin so Telegram delivers messages
  • Or your own bot from BotFather on paid plans; its token is stored encrypted

What flows through

  • Messages, replies and forum topics
  • Screenshots, documents and voice notes
  • Replies from Tydy back into the chat

Permissions & privacy

  • Only connected chats are processed, not your whole Telegram
  • AI processing can be switched per chat and topic
  • Sending to Telegram requires a permission

Telegram Business

Early access

Personal chats with clients, handled in Tydy and answered from your own account.

Client’s personal chatTydy · Chats and a task✓✓ Reply from your account

How it connects
In Telegram: Settings → Telegram Business → Chatbots → add Tydy’s bot. Then choose which chats to add to the workspace.
What flows through
Messages of the chats you added; replies go out from your personal account.
Permissions & privacy
Chats you haven’t added never reach the workspace. Who may reply on your behalf is up to you. Enabled per workspace.

MCP

Available

An MCP server that gives AI agents controlled access to one workspace.

Tydy: tasks, chats, filesMCP: scopes ∩ role ∩ planAI agent

How it connects
Endpoint https://tydy.dev/mcp (Streamable HTTP) with OAuth or a personal token.
What flows through
Tasks, projects, task conversations, Telegram chats, attachments and AI Inbox.
Permissions & privacy
Access = token scopes ∩ your role ∩ plan. One workspace per connection; revocation is immediate.
Connect via MCP

Cursor & MCP clients

Available

Use Tydy from Cursor, Claude or any client that supports remote MCP servers.

Cursor / Claudemcp.json or OAuthhttps://tydy.dev/mcp

How it connects
Add a custom MCP server with the endpoint and your token, or sign in through OAuth where the client supports it.
What flows through
Whatever the granted scopes allow: reading tasks and chats, updating tasks, replying in Telegram.
Permissions & privacy
The client never sees your password; you choose scopes and can revoke the token at any time.
Connect via MCP

More integrations will appear here when they actually work. Not before.

Connect Telegram in about two minutes

Connect via MCP