SetSmart
io.github.setsmart-gitPublished by GitHub account setsmart-gitv0.1.2Updated Oct 25, 2026
Instagram, WhatsApp and Messenger DMs through official Meta Business APIs.
Overview
SetSmart connects an assistant to Instagram, WhatsApp and Messenger business messaging through official Meta APIs, letting it read conversations and send or tag
- What you can do
- Send text, images, video, audio, templates and reactions on Instagram, WhatsApp or Messenger conversations. List, search and read conversations, tag them and write internal notes. Find, read, import and tag contacts. Pause or resume the AI assistant per conversation or per channel. List Instagram posts and comment triggers, list and cancel scheduled messages, list templates and read conversation stats.
- When to use it
- Useful when a team runs customer conversations on Instagram, WhatsApp or Messenger through a SetSmart workspace and wants an assistant to draft, send and organize replies, hand conversations to humans, or pull basic messaging stats.
- Requirements
- Either the remote endpoint with interactive OAuth, or the npm package setsmart-mcp run locally with Node.js 18 or newer. A SetSmart workspace with at least one connected channel and a workspace API key supplied as SETSMART_API_KEY; an optional SETSMART_MCP_URL overrides the upstream endpoint.
Installation
In SourceWeft
- Open SetSmart in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.setsmart-git%2Finstagram-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"setsmart": {
"type": "http",
"url": "https://setsmart.io/api/mcp"
}
}
}README
Instagram MCP Server (also WhatsApp and Messenger)
An MCP server that lets Claude, Cursor, Claude Code and any other MCP client read and reply to Instagram DMs, WhatsApp messages and Facebook Messenger conversations, through the official Meta Business APIs.
Ask your assistant to "find the lead who asked about pricing on Instagram and send them the booking template", and it happens on the real account.
Why this one is different
Most Instagram and WhatsApp MCP servers drive a personal account: a browser automation session, an unofficial bridge, or a reverse engineered mobile API. They break when Meta changes something, and they put the account at risk of being disabled.
This one talks to the official Instagram Messaging API, WhatsApp Cloud API and Messenger Platform, through SetSmart's Meta-approved Business app. Messaging Instagram, WhatsApp or Messenger programmatically is not possible without an approved app, which is why this bridge requires a SetSmart workspace rather than your Instagram password.
That is the tradeoff, stated plainly: it is not self-hostable against your own account, and it needs a SetSmart API key.
Requirements
- Node.js 18 or newer
- A SetSmart workspace with at least one channel connected (Instagram, WhatsApp or Messenger)
- Your workspace API key, from Settings then Integrations
Quick start
Claude Desktop / Claude Code
Add this to your MCP config (claude_desktop_config.json, or .mcp.json for Claude Code):
Cursor
Same block, in ~/.cursor/mcp.json.
Remote MCP, without this bridge
The SetSmart MCP server is also reachable directly over Streamable HTTP with OAuth, so clients that support remote MCP can skip this package entirely:
Use this bridge when your client only speaks stdio, or when you would rather authenticate with a static API key than an interactive OAuth consent.
Tools
30 tools, grouped by what they touch.
Messaging
Conversations
Contacts
AI control
Scheduling, templates and stats
What it deliberately cannot do
An API key is a long lived static secret, so it gets a restricted surface. These are reachable through interactive OAuth on the remote server, never through this bridge:
- billing and subscription changes
- workspace settings
- connecting or disconnecting a channel
- creating or rewriting AI assistants
- bulk deletion, blacklists, blocked countries
Rotating the key in your SetSmart settings revokes access immediately, on the next request.
Configuration
How it works
This package contains no messaging logic. It is a stdio to Streamable HTTP pipe: your client speaks MCP over stdin and stdout, the bridge forwards each request to the hosted SetSmart MCP server with your key in the Authorization header, and streams the answer back. Around 150 lines, in src/index.js, so you can read all of it before trusting it with an account.
Links
License
MIT
Source: README.md at commit d41fd7f
Tools
0Version history
1- v0.1.2LatestSep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts