CommsConnector
Read and reply to your Instagram DMs, or summarize a thread, from Claude or ChatGPT, through Tulina's own MCP server — the inbox only, never the feed.
Official site: www.instagram.com
What it can do
1 read/2 send
- 01Send
List your DM conversations and read a thread
- 02Send
Send a DM, or reply in an existing thread
- 03Read
Summarize a conversation with someone
Direct messages only. No feed, no stories, nothing published: the scope is deliberately the inbox and nothing else. You act as yourself, under your own account.
The thread that appears to be missing is usually not missing. Instagram keeps message requests in a separate place from accepted conversations, and a pro account's two inboxes are not always served together, so a conversation that does not show up is generally one still waiting to be accepted.
Does Instagram have an MCP server?
We found none as of October 2026. Meta publishes an MCP connector for Meta Ads, which manages ad campaigns, and none for a person's Instagram messages. Most of the results for this search are community servers or aggregators that wrap the Graph API. Tulina's connector takes a different route: it signs in to your account through a hosted flow run by Unipile, our messaging provider, and reads and sends direct messages.
How do you connect Instagram DMs to Claude and ChatGPT?
Through Tulina's MCP server, in three steps:
- Make sure a Unipile subscription key is on the Unipile account connector, either your own key or the platform's, which an admin grants as the hosted messaging option.
- On Tulina's Instagram connector, choose "Connect my Instagram account" and sign in through the hosted flow. There is no cookie to paste and no extension to install.
- Add
https://mcp.tulina.ai/mcpto Claude or ChatGPT and sign in with your Tulina account. The MCP page has the same link.
How does Tulina read and send Instagram messages?
Reading and sending are two separate tools, so allowing reads never allows sending. The read tool lists conversations newest first, one to 100 at a time, group threads included, and opens a thread by its id. Each one-to-one thread carries the other person's name. An attachment comes with a source the agent can file in a project without passing the file through the conversation. The send tool answers in an existing thread, or opens a new one with a contact. It leaves at once, with no draft step.
Why is an Instagram conversation missing?
Usually because it has not been accepted. Instagram holds message requests apart from accepted conversations, and a pro account's two inboxes are not always served together. The agent lists what the account returns. Accept the request in Instagram, then list again, and the thread appears like any other. If a thread is there but a message is blank, the read tool marks it as unavailable when the provider passed it on without text or attachment, rather than guessing at its content.
What you can ask it
"Read my unread Instagram DMs and tell me which need an answer today." The agent lists the latest conversations, opens the latest threads and returns a short ranking with a line on each.
"Summarize my conversation with this handle." The agent finds the thread in the list, reads its messages and summarizes them. Nothing is sent.
"Reply to that thread: yes, Thursday works." The agent shows you the text, and sends it into that thread once you agree, because a sent message cannot be recalled by the connector.
Instagram pairs with WhatsApp and Messenger when customers write on more than one app, and with LinkedIn for the professional side of the same conversation.
What the Instagram connector can't do
- It does not read the feed, stories, comments or insights, and it publishes nothing.
- A conversation still waiting in message requests may not appear until it is accepted in Instagram.
- It does not edit or delete a message after sending.
- A send leaves at once. There is no draft or scheduling step.
- It acts as your own account, so it is not a shared inbox for a team.
- The older send operation on the read tool is deprecated and served until 10 December 2026. Use the send tool.
Why through Tulina
The connection was never the hard part.
Most systems now publish their own way for a model to reach them, and that is good: it is what Tulina connects to. The hard part is deciding who may use it, what it is allowed to return, and what the model knows before it asks.
The keys stay in one place
YouTeamOrganisation
Connect Instagram once. The credential is encrypted in a vault, never held in clear, and never pasted into a chat or a workflow file. A person uses their own key where they have one, their team's where they do not, the organisation's after that, so nobody is blocked and nobody holds more access than they need. Revoke it once and everything running on it stops.
What leaves is filtered before it leaves
fields droppedmasked or hashedpseudonymised
Roles decide who can reach Instagram at all. Beyond that, a policy on the connector itself decides what comes back. The data is minimised at the source rather than after it has already reached a model.
Every call is on the record
whatwhowhen
Runs are logged for the organisation. That is what makes an automated action reviewable after the fact, and it is what a security review asks for first.
The run starts knowing your company
namingkey accountsdecisions
A direct connection gives a model access. It does not tell it how your company names things, which accounts matter, or what was decided last quarter. Tulina carries that across every tool, so the same request against Instagram returns something usable instead of something generic.
Processes that run on Instagram
None published yet.