Spronta

Integrations

One OS, many doors

Spronta connects outward through channels, plugins, and MCP, and inward through open-source SDKs and a plain REST API. Wherever you work, the workspace is reachable.

Two ways in

M
Claude / Cursor (MCP)
// spronta-mcp: operate the Marketing OS from any MCP client.
// Private beta: scoped keys issued at onboarding.

> "What campaigns are live right now?"
// reads return instantly, scoped to your workspace

> "Draft a launch post and schedule the email"
// mutations never execute directly:
// they land as proposals in your Spronta Inbox
// you approve; then it ships
N
Your site (Next.js)
// Spronta's asset pipeline serves your site's images
// next.config.ts
const nextConfig = {
  images: {
    remotePatterns: [{ hostname: "cdn.spronta.com" }],
  },
};

// In your component
import Image from "next/image";

<Image
  src={`https://cdn.spronta.com/${projectId}/${imageId}`}
  width={800}
  height={600}
  alt="Product photo"
/>

Agent doors

Channels

Plugins

Asset pipeline SDKs

Works with your stack

N

Next.js

App Router & Pages Router

R

React

Hooks, components, SSR

V

Vue

Vue 3 & Nuxt

S

Svelte

SvelteKit support

A

Astro

Static & hybrid sites

V

Vercel

First-class hosting target

SDKs optional. Lock-in impossible.

Our official SDKs make development faster, but they're not required. The API is standard REST and the asset CDN is a plain URL. If you can make an HTTP request and load an image, you can use Spronta.

# Any language, any framework
curl https://cdn.spronta.com/{projectId}/{imageId}?w=800&f=webp

Don't see your stack?

If it can make an HTTP request, it can talk to Spronta. Check the docs or reach out.