Spronta
Get started

spronta-mcp · private beta

Your Marketing OS,
operated from anywhere

spronta-mcp connects Claude, Cursor, or any MCP client to your Spronta workspace. Agents read your campaigns, audience, and content with scoped keys. Anything they want to change lands as a proposal in your Inbox, never as a silent write.

Request beta accessHow approvals work

The operator contract

Scoped keys

Every connection authenticates with an API key scoped to a workspace and to specific permissions. Reads require read scopes; nothing gets blanket access.

Mutations become proposals

Creating a campaign, drafting content, scheduling a send: every write is parked as a proposal in your Spronta Inbox. You review and approve before anything ships.

Everything on the ledger

MCP activity is attributed like any other agent work: what was requested, by which token, and what you decided.

What is spronta-mcp?

spronta-mcp is Spronta's operator server for the Model Context Protocol. It exposes the Marketing OS to any MCP-compatible agent: list and inspect your records, segments, campaigns, and content, then propose new work that you approve in the Inbox.

Audience

  • spronta.list_recordsList people, companies, and custom records
  • spronta.get_recordFetch one record with its attributes
  • spronta.create_recordPropose a new record
  • spronta.update_recordPropose a record update

Segments

  • spronta.list_segmentsList saved audience segments
  • spronta.preview_segmentPreview exactly who a segment reaches
  • spronta.create_segmentPropose a new segment

Campaigns

  • spronta.list_campaignsList campaigns in the workspace
  • spronta.get_campaignFetch one campaign and its pieces
  • spronta.create_campaignPropose a new campaign

Content

  • spronta.list_content_entriesList CMS entries
  • spronta.draft_content_entryPropose a content draft

Shipping

  • spronta.schedule_publishPropose a publish slot
  • spronta.schedule_email_sendPropose an email send

What can you ask?

From Claude, Cursor, or wherever your agent lives. Reads come back instantly; the rest arrives in your Inbox for one-tap approval.

>What campaigns are live in my workspace right now?
>Draft a launch post for the dark mode release, in our voice
>Build a segment of contacts who signed up in the last 30 days, and show me who's in it
>Create a campaign for the v2 launch: site post, email, and social
>Schedule the pricing page update to publish Monday morning
>Queue the newsletter send to the active-users segment for review

Frequently asked questions

What is MCP (Model Context Protocol)?

MCP is an open standard that lets AI assistants connect to external tools and data sources. It's supported by Claude, Cursor, Windsurf, and a growing set of agent clients. spronta-mcp uses it to expose your Spronta workspace as a set of tools.

Can an agent publish or send email through MCP without me?

No. Reads are available to scoped keys, but every mutation, from creating a campaign to scheduling an email send, is parked as a proposal in your Spronta Inbox. Nothing executes until you approve it.

Which AI clients work with spronta-mcp?

Any MCP-compatible client: Claude Code, Claude Desktop, Cursor, Windsurf, and others. During the private beta we issue connection details and scoped keys when we onboard you.

How is this different from the agent inside Spronta?

Same OS, different door. The built-in agent lives in the workspace; spronta-mcp lets agents you already use, like Claude or Cursor, operate the same workspace under the same approval rules.

How do I get access?

spronta-mcp is in private beta. Sign up for Spronta and ask for MCP access, or reach us at hello@spronta.com, and we'll set you up with a scoped key as we onboard beta users.

Bring your own agent. Keep the receipts.

spronta-mcp is in private beta. Get on the list and we'll reach out as we onboard.

Request beta accessTalk to us