MCP tools

Rowsend runs an MCP server on your computer, so an AI agent such as Claude Code, Codex, Gemini CLI, Cursor or Claude Desktop can set up projects, write campaigns and check results for you. The server only listens on your own computer, and each agent gets its own token, which you can revoke.

Connect an agent

The quickest way is to let the agent do it. Copy the prompt from Onboard your agent on rowsend.com and paste it to your agent. It follows the setup guide, runs the pairing command and waits while you click Allow in Rowsend. The command writes the token into the agent’s settings itself, so it never appears in your conversation.

To connect one yourself, open Settings → MCP, click Add a client, name it and choose the app. Rowsend shows a command to run (Claude Code) or JSON to add to the app’s MCP settings (Cursor, Claude Desktop).

Settings → MCP lists every connected client with when it last worked. Revoke cuts one off. Turn on MCP server turns the whole server off.

What agents can do

Area	Tools
Projects	list_projects, create_project
Database	prepare_database_setup, complete_database_setup, open_database_setup, get_pending_setup, list_database_fields, set_contact_fields, get_data_source_status, sync_contacts, set_sync_interval
Sending setup	open_sender_setup, get_sender, verify_sender, setup_ses_bounce, setup_postmark_webhook
Contacts	list_contacts, list_segments, create_segment, preview_audience, add_suppression
Topics	list_topics, create_topic
Content	get_brand, list_templates, get_template, create_template, update_template, list_images, upload_image, preview_email
Campaigns	list_campaigns, get_campaign, create_campaign, update_campaign, duplicate_campaign, send_test, get_campaign_stats, pause_campaign, resume_campaign, cancel_campaign, retry_failures

Agents receive each tool’s full description over MCP, so they know the details. A typical session: the agent connects your database, drafts a campaign in your brand, previews it, sends you a test and tells you it’s ready.

What only you can do

Some actions stay with you, whatever the agent asks:

• Sending and scheduling. Agents draft campaigns and send tests. You click Send.
• Keys and passwords. Sender keys never pass through MCP. open_sender_setup opens the Sending page with the non-secret fields filled in, and you type the key. On platforms where you bring a database login, open_database_setup opens the connect dialog for you to paste it; the agent only sees tables, fields and SQL that hold no password.
• Editing segments. Editing a segment changes who gets every unsent campaign, so agents can create segments but not change them.
• Turning off the unsubscribe footer or the mailing address. An agent can’t, and any edit an agent makes to a campaign turns both back on.
• Undoing an unsubscribe. An agent can unsubscribe a contact with add_suppression. Only you can resubscribe them.
• Sending while your computer is off.

Keeping track of agents

Campaigns and templates an agent changed show an Edited by badge with the agent’s name until you save them yourself. Project settings → Agent activity lists every change agents made to that project, newest first. Rowsend’s windows update as soon as an agent changes something.

Apps that only speak stdio

Rowsend’s server uses Streamable HTTP. For an MCP app that can only start a command, use Rowsend itself as a bridge:

/Applications/Rowsend.app/Contents/MacOS/Rowsend --mcp-stdio

The pairing command with --client print prints a config that does this.