We've been building out a workflow using your MCP connector to bring Claude into our customer support process, and we've hit a wall worth raising as a formal feature request.
Right now the MCP integration gives solid read access to contacts, purchase history, invoices, payments, tags, notes, and the general activity log. That's great for pulling context on a customer. But it doesn't touch the Inbox at all. There's no way for Claude to read an incoming customer email, see the actual conversation thread, or send or reply to a message. The tools we have access to are entirely CRM lookup tools, nothing for two-way communication.
That's the piece we actually need most. Other CRMs and customer communication platforms have moved a lot faster here. Their AI integrations let an assistant read what just came in, pull up the customer's history, draft or send a reply, and flag anything that needs a human. We want to do exactly that with Claude and Ontraport: triage incoming inquiries, help draft and, maybe eventually, send responses, and escalate what needs a real person.
Without Inbox access in the MCP, we can only use Claude for research on a customer after the fact. It can't actually participate in handling the conversation, which is where most of the time savings would come from.
Is Inbox support (reading messages and threads, plus sending or replying) on your roadmap for the MCP connector? Even read-only access to incoming messages and thread history would be a big step forward if send capability needs more guardrails built first.
Great to hear that you are enjoying the mCP access! So are we.
Your request is right on target. We intentionally launched with a limited set of features to make sure everything was kosher but definitely plan on expanding it just the way you envision. Stay tuned!
Please sign in to leave a comment.