← All integrations

Remarkety MCP server

20 operations0 webhooks

Manage stores and their sync status, create and unsubscribe contacts, build and update email campaigns with their rules and templates, and read products, rules and segments with Remarkety.

Use Remarkety in Claude, ChatGPT, Cursor or another MCP client

Connect Remarkety once in Corsair, then add one MCP address to your agent.

Connect Remarkety
Setup steps for Claude, ChatGPT, Cursor and Claude Code

Building your own app on the Corsair SDK? Get API keys

Try Remarkety with your agent

Connect Remarkety, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Remarkety on my account, then run one read-only example and show me the result.

Runs once, when you ask

Remarkety tools and triggers

Tools are what your agent can do in Remarkety through Corsair's MCP server. Triggers are the Remarkety events a routine can start from.

Campaigns

  • CreateWrite

    Create a campaign from a type and its actions, each an email or an api webhook with the rules that decide when it runs

    campaigns.create

  • DeleteDestructive

    Delete a campaign

    campaigns.delete

  • GetRead-only

    Read one campaign by id

    campaigns.get

  • TypesRead-only

    Read the campaign types the store supports and their options

    campaigns.types

  • UpdateWrite

    Update a campaign, including its mode, which can start or stop real sending

    campaigns.update

Stores

  • CreateWrite

    Create a store with the API key Remarkety will sync it with

    stores.create

  • DeleteDestructive

    Delete a store

    stores.delete

  • GetRead-only

    Read one store by id

    stores.get

  • StatusRead-only

    Read the store sync status, including the last error and the last successful sync

    stores.status

  • UpdateWrite

    Update a store; the id goes in the body because the route is PUT /stores

    stores.update

Contacts

  • CreateWrite

    Create or update a contact in a store; Remarkety emails a double opt-in request unless doubleOptin is false

    contacts.create

  • UnsubscribeWrite

    Unsubscribe one email address from a store

    contacts.unsubscribe

Connect Remarkety to Claude, ChatGPT or Cursor

  1. 1

    Connect Remarkety in Corsair

    Add your Remarkety API key once in Corsair. Corsair stores the credential encrypted and makes the Remarkety API calls for your agent, so it never goes into a prompt or a config file. Connect Remarkety

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Remarkety. On a ChatGPT personal plan, connect Remarkety here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Remarkety's read and write operations run right away and its 2 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/remarkety, add the Remarkety plugin, and connect with an API key. Then call methods like corsair.remarkety.api.campaigns.create() from your app. Corsair keeps each tenant isolated.

Yes. Remarkety requires an API key from your Remarkety account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Remarkety, GitHub, Notion, Stripe, and the rest. Trigger Remarkety from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for manage stores and their sync status, create and unsubscribe contacts, build and update email campaigns with their rules and templates, and read products, rules and segments with Remarkety. Common builds include sync jobs, admin tooling, and agents that call Remarkety APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Remarkety API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/remarkety in the open repo. When Remarkety ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Remarkety data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Remarkety data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Remarkety on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 2 destructive Remarkety operations. You can change a link's mode at hub.corsair.dev/me.