Back to browse
Inbox – An API and MCP server for managing DMs programmatically

Inbox – An API and MCP server for managing DMs programmatically

by kevinpicchi·Mar 10, 2026·1 point·1 comment

AI Analysis

●●SolidSolve My ProblemSlick

Unified DM API with MCP server support, though only X works today.

Strengths
  • MCP server integration enables AI agents to manage conversations directly.
  • Unified API abstracts fragmented social platform endpoints into one.
Weaknesses
  • Instagram and LinkedIn support delayed until Q2 2026.
  • Competes with official platform APIs and established social tools.
Target Audience

Developers building chatbots, sales teams, support teams

Similar To

Sprout Social · Hootsuite · Twitter API v2

Post Description

Hey HN,

I'm Kevin, and I've been building Inbox (https://inboxapp.com) — A CRM and an API for sending and managing DM conversations across messaging platforms. Right now we support X (Twitter) DMs. Instagram and LinkedIn are next on the roadmap. The idea is simple: DMs are becoming a primary communication channel for sales, support, partnerships, creator outreach — but there's no good programmatic layer for them. You either copy-paste manually or hack together brittle scrapers. Inbox gives you a REST API with full thread and message management, a webhook system for real-time events (new messages, thread updates, status changes), and an MCP server so AI agents can manage your DMs directly. Your team also gets a shared inbox UI to handle conversations that need a human touch.

What you can do with the API:

- Send and receive DMs programmatically - Manage threads (assign, tag, set pipeline stages) - Sync conversation data to your CRM or internal tools - Get real-time webhook events when anything changes - Let AI agents handle DMs via our MCP server (works with Claude, Cursor, etc.)

We built this because i was doing support for my product over X DMs and realized the tooling just doesn't exist. X's own API for DMs is painful, rate-limited, and requires jumping through hoops. Most teams doing DM-based outreach or support end up with some combination of manual copy-paste, spreadsheets, and prayer. The MCP server is the part I'm most excited about. You can point Claude or any MCP-compatible agent at your Inbox and it can read conversations, send replies, tag threads, update prospect info — basically run your DM workflows autonomously. We use it internally and it's become the thing i didn't know i needed.

Honest status: X support is solid and battle-tested. Instagram and LinkedIn are coming Q2 2026. We're a small team, so I'd genuinely love feedback on what platforms and integrations to prioritize.

API docs: https://docs.inboxapp.com MCP server setup: https://docs.inboxapp.com/mcp-server

I'll be in the comments all day. Would love to hear: what DM-based workflows are you hacking together right now? What would you build if you had a clean API for this?

Similar Projects

Developer Tools●●Solid

InboxAPP – All Your DMs in One API / MCP

Single API that maps DMs into a team inbox and developer primitives (threads, webhooks, tags) is a pragmatic, useful play — the docs even get you sending your first request with a token and curl in minutes. It’s not reinventing the space (Twilio/Conversations, messaging platforms and CRMs already compete here), so success will depend on real platform coverage, rate limits, compliance and pricing rather than the docs alone.

Solve My ProblemSlick
kevinpicchi
104mo ago
AI/ML●●Solid

Email for AI Agents

Solves the agent email gap with a simple API, competing directly with Resend and SendGrid.

Ship ItSolve My Problem
johnjoubert
111mo ago
AI/ML●●Solid

TermHub – Open-source terminal control gateway built for AI Agents

AI-native terminal control for agents when tmux wasn't built for LLM workflows.

Solve My ProblemNiche Gem
duo121
542mo ago