Sendoso opens request-based beta of MCP server for AI agents to send gifts
Sendoso launched a beta of its Model Context Protocol server so AI agents can select, send and track gifts and direct mail. Access is request-based and approved on a rolling basis.
Sendoso launched a beta of Sendoso MCP on June 24, 2026, a Model Context Protocol server that lets AI agents send personalized gifts and direct mail. Agents can identify whom to reach and when, select a gift from recipient context, send it and trigger follow-up on delivery from inside existing AI clients and go-to-market tools. Access is by request through Sendoso's website, with approvals issued on a rolling basis.
The details
- Demandbase supplies account intent, engagement scoring, buying committee and pipeline stage data.
- Gong provides call recordings, deal sentiment and interaction history for personalization.
- UserGems and Warmly supply data that flags moments to send, Clay enriches contacts across 150+ providers, and Outreach sequences follow-up after delivery.
- Suzzette Giron, ABM leader at Invoca, is among the first customers testing the integration, and Invoca has used Sendoso for six years.
- The release lists five founding partners in its introduction and adds Clay in the full list.
Context
Sendoso MCP joined a run of 2026 releases from the company, including Party Link management and Salesforce-based gift policies in June and the acquisition of Merch.co, which the newsroom page links. One day after the beta, Goody launched a self-serve gifting MCP. Sendoso's August release notes list the MCP under a "Now in GA" heading while also describing it as in beta, and in September it became available as an action in Databricks Genie and AI Playground.
Not disclosed
- Pricing
- General availability date
- Vendor
Sendoso- Category
- Gifting & Direct Mail
- Announcement type
- AI launch
Report an error
Vendors and readers can flag a factual error in this story, or ask for an image or logo to be removed. Email Cora, the editor, with the link. Image and logo removals happen within one business day. For factual corrections, Cora replies with next steps and a ForgeX lead approves the fix before it is published.


