Integrations

Connect mssgs with the tools you already use

GitHub, UniFi Protect and App Store Connect post finished cards the moment you paste a URL. Claude, Cursor and Codex connect to the desktop app in one click. Everything else talks to mssgs through a webhook, a slash command or the Game SDK.

Connect an AI tool Developer docs

Native integrations

Paste a URL, get a proper card

mssgs recognises these three services by themselves. Create a webhook in Manage Server → Webhooks, paste its URL into the service, and every event arrives as a finished card with the verified tick. There is no payload to write and nothing to host.

GitHub

Available

Get notifications of commits, pull requests, issues, and releases directly in your mssgs channels. A burst of changes to one issue or pull request arrives as a single card.

  • Push notifications
  • PR reviews and comments
  • Issue updates
  • Release alerts
Set up

In your repository, open Settings → Webhooks. Paste the URL, set the content type to application/json and put the webhook's Webhook Secret in Secret.

UniFi Protect

Available

Doorbell rings, motion, and the people, vehicles and packages your cameras detect, with the snapshot and a link to the event in Protect.

  • Doorbell rings
  • Motion
  • People and vehicles
  • Packages
Set up

In UniFi Protect, open Alarm Manager, create an alarm and give it a webhook action with the URL.

App Store Connect

Available

Builds that finish processing, App Review and TestFlight states, tester feedback and crash reports, each with a coloured status.

  • Build processing
  • App Review
  • TestFlight
  • Feedback and crashes
Set up

Point an App Store Connect webhook at the URL. Add an API key under Apple Webhook API in the webhook's settings and every card names the app, the version and the build.

What each service posts, in the webhook docs

AI assistants (MCP)

Claude, Cursor or Codex, connected in one click

Let Claude, Cursor and other AI tools read and act in your chats through the MCP server built into the desktop app.

Open Settings → MCP, switch on the local server and press Install next to your AI tool: mssgs adds itself to that tool's configuration, with a token of its own. Claude Code, Claude Desktop, Cursor, Codex CLI and Kimi Code CLI are supported; where one click is not possible, you copy a ready-made configuration instead.

  • Only the channels you pickYou choose which channels and DMs an AI tool can see. Everything else does not exist for it.
  • Read-only until you allow moreSending, server management, agent steering, File Drop and watch parties each have their own switch.
  • Runs on your own computer, revocable at any timeThe server only listens on 127.0.0.1 while mssgs is open, and every AI tool gets a token you can revoke.
MCP docs Step by step in the help desk

More than 120 tools, each group behind its own switch

With the server on, an AI tool can read the channels you picked. Everything that writes stays off until you switch it on under Permissions:

  • Allow sending messagesPost, reply, react, edit and pin as you.
    Off
  • Allow server managementCreate channels, webhooks and triggers in communities you manage.
    Off
  • Allow agent steeringChange how a channel's agents work and steer their tasks.
    Off
  • Allow File DropSee who is nearby, send files and follow the drops.
    Off
  • Allow watch partiesStart, join and control watch parties.
    Off

Things to ask it

What a connected AI tool does with mssgs, in your own words. Each prompt shows the tools it calls and the switch it needs.

What did I miss in #general since yesterday?

Uses
read_channellist_mentions
Needs
Nothing extra: reading is on with the server

Create a webhook for #deploys and give me the URL.

Uses
create_webhookget_webhook_url
Needs
Allow server management

Send the 120 MB build to Sam on the Mac next to me.

Uses
list_file_drop_nearbysend_file_drop
Needs
Allow File Drop

Which tasks are still open in #website? Tell Builder to add a test.

Uses
list_agent_taskssteer_agent_task
Needs
Allow agent steeringAllow sending messages

For developers

Build your own integration

Anything that can send an HTTP request can post into a channel, and your own service can answer when a member types a command. It is JSON over HTTPS, so there is no SDK to install.

Webhooks

Post into a channel from anything

Your shop, a cron job, a form or a monitoring check: one signed POST and the message appears, as text or as a card with fields, files and buttons. The answer carries a callback URL to update or delete it for 30 minutes.

Documentation
The button carries its own step, so a press changes the card for everyone without a server of your own.
Slash commands

Give your community its own /commands

A member types /ticket and mssgs sends the message to your service. The JSON it answers within 5 seconds becomes a card; a slow job answers with a loader first and finishes through the callback URL.

Documentation
Every request says who asked and which roles they have, so your service decides who may do what.
ButtonsOpen a link, change the card on a tap, or call your service and learn who pressed what. Live updatesShow progress on one card, swap in the result, and hear replies, reactions and presses as they happen. Message cardsTitles, markdown, fields, images, a status pill and a loader, with a live builder to try them in. Bot accountsA bot as a member of its own, with a BOT label, posting cards and hearing every press over its own connection. Part of Premium.

In the desktop app

Agents, games and files

Three integrations that run on your own computer, right next to your chats.

AI agents in a channel

Offer your computer as an agent. People mention it with a task, it runs a Claude Code or Codex session in the project's folder on your machine, and everyone follows along on its card, up to the pull request.

Premium · runs on your computer

Documentation

Game SDK

Your game shows Playing under a player's name, with a Join now button for their friends. Desktop games use the app's local bridge; browser and phone games go through your own backend.

Local bridge · linked backends

Documentation

File Drop

Hand files straight to a desktop on the same network, up to 20 GB, without uploading them anywhere. An AI tool can send a drop too: it is announced in your DM, and the other side's AI tool can take it.

Sending is Premium · receiving is free

File Drop in the help desk

Missing an integration?

Let us know which integrations you need. We listen to our users.

Send suggestion

Try the integrations yourself

Make a community, add a webhook and watch the first card arrive. The developer docs walk you through every step.

Download Developer docs