Two kinds of integration appear here. Through the MCP means an AI host can reach it in a conversation. In Stensul means the connector lives in the Stensul app, configured by an admin, and people use it from the editor. An email built through the MCP lands in Stensul as a draft, so everything in the second group still applies to it once you open the draft.
Status labels: Available generally available · Beta labeled beta by Stensul · Not yet not supported today. Nothing here is listed as “coming soon” without a published source.
Connect the Adobe Workfront MCP server to the same host. The brief must live in Workfront fields, not an attached document, and you name the project and field in your prompt
Available
Other project tools with their own MCP server
Connect both servers to your host and ask it to read the brief
Not documented by Stensul yet
An admin chooses the brief source Stensul works with in Stensul > Admin > Settings > General > Brief Source Tool. Set it up there before asking your assistant to read briefs from that tool.
ESPs and marketing automation (in Stensul)
Completed emails are uploaded to these from Stensul. The MCP doesn’t upload or send: see Handing off to your ESP.
Platform
Status
Salesforce Marketing Cloud (email, dynamic content authoring, native forms for landing pages)
Bring your own LLM (OpenAI, Anthropic or Google models via major cloud providers)
Beta
Server-to-server APIs
The MCP server always acts as a signed-in person. For automation with no person in the loop, Stensul also has a REST API that uses OAuth client credentials:
API
What it covers
Reference
Stensul REST API
Libraries, emails (create, read, copy, update content and settings, render as HTML, PDF or PNG), images, modules