openserve // agent console LIVE

Retention + marketing tools for agents

Your agent runs the growth stack. You approve.

OpenServe knows who came back to your site, which companies are looking, and who has gone quiet. Connect any MCP agent and it can read all of it, build the audiences, and draft the follow-ups. There is no dashboard to learn. Nothing sends, posts or spends until a person says yes.

Get an API key See the 53 tools free to start | no card

tools: 53
families: 12
transport: MCP, streamable HTTP
auth: API key or OAuth 2.1
rate: 60 calls / min / grant
sends on its own: never

$ POST /api/v1/mcp
> tools/list → 53 tools

■Scoped per tool family ■Capped per day ■Revocable in one click ■Named on every act

Retention

Turn visits into a list, and a list into people who come back.

One tag on your site. After that the work is your agent's, and the decisions are yours.

/ 01
Know who is on your site
Companies visiting, the pages they read, and whether it looked like buying. Your own known people are named when they come back, on any device. Nobody is ever guessed from an IP address.
/ 02
Catch the returning reader
When a recognised visitor has no email with you yet, your site shows your own opt-in at that moment. Nothing is pre-filled and no address crosses from anyone else's data.
/ 03
Build audiences in plain words
Pricing readers. People who gave you their email and visited this month. Known people who have not been back in 30 days. Your agent saves them with create_audience.
/ 04
Win them back
The agent drafts the email or the post in your brand's voice and files it. You approve in Activity. Audiences sync to your own Meta and Google ad accounts, and stay current.
/ 05
Read what worked
get_retention and get_analytics return list growth, returning-reader rate and what each win-back brought home, as raw rows your agent can reason over.

How you use it

Connect once. Then just ask.

The same session in any MCP client: Claude, Cursor, Codex, n8n, or your own agent.

your agent · openserve connected

Which companies looked at pricing this week? Add the serious ones to the CRM and draft a follow-up for each.

list_website_visitors { days: 7 } add_company_to_crm × 3 get_brand_kit draft_email × 3 → filed for approval

Eleven companies visited this week. Three read pricing more than once, so I added those to your CRM and drafted a follow-up for each in your brand's voice.

Company	Visits	Read	Signal	Draft
Northpine Labs	6	/pricing, /security	buying	waiting on you
Driftwave	4	/pricing, /demo	buying	waiting on you
Copperleaf Data	3	/pricing	buying	waiting on you
Quillstack	2	/blog	reading	none

needs you3 emails are in OpenServe › Activity. Nothing has been sent.

Sample data, for illustration

The suite

53 tools in 12 families. Grant only what the job needs.

Every family has its own read scope and, where one exists, its own write scope. A tool your grant does not carry is not even listed to the agent.

/ 01

Visitors

readwrite

Who is on your site, your saved audiences and how retention is going.

list_website_visitors
list_audiences
get_retention
get_visitor_settings
create_audience
sync_audience_to_channel
add_company_to_crm
update_visitor_settings

/ 02

CRM

readwrite

Companies, deals and follow-ups, in the pipeline you already work.

search_companies
list_deals
get_deal
create_company
create_deal
move_deal
log_follow_up

/ 03

readowner

Campaigns, delivery and the media buyer's proposed moves. Paid changes are proposals.

list_campaigns
get_campaign
list_ad_moves
list_ad_accounts
apply_ad_move
dismiss_ad_move
set_campaign_autopilot
propose_budget

/ 04

Email

readdraft

Lists, sizes and performance. The agent writes the draft; a person sends it.

list_email_lists
get_email_performance
get_newsletter_ads
draft_email

/ 05

Social

readdraft

Connected pages, the traffic they send and post drafts filed for approval.

list_social_pages
get_social_traffic
draft_social_post

/ 06

Sites

readwriteowner

Read and edit your pages. Publishing is its own owner-granted scope with a daily limit.

site_read
site_patch
site_publish

/ 07

Analytics

read

Realtime, retention, paths, monetization and interface analytics for your workspace.

get_analytics

/ 08

Brand

read

Voice, colours, fonts and logo, so everything the agent writes sounds like you.

get_brand_kit

/ 09

Agents

readrun

OpenServe's own specialists as tools: ask one, brief a team, run a flow.

list_agents
ask_genius
brief_team
run_flow
get_run

/ 10

Approvals

read

The state of anything the agent filed. Poll it instead of assuming it went out.

request_approval
get_approval
list_approvals

/ 11

Collectives

readwrite

Find partner businesses in your collectives and request introductions.

list_collective_memberships
find_collective_members
list_collective_introductions
propose_collective_partner
request_collective_introduction
decide_collective_partnership

/ 12

Reading

read

Published articles with your own subscriptions. Reads pay the publisher.

search_content
check_content_access
read_content
get_content_usage

→ reads✎ records a reversible row, or files a draft for approvalowner only the workspace owner can grant it

The guarantees

Built so you can hand an agent the keys.

These are enforced by the server on every call. They are not prompt instructions an agent could talk its way around.

Reaching a person is never a tool

There is no send_email and no post_social. An agent drafts, a person approves in Activity, and the approval runs the send.

Spending is filed, not applied

A budget change or an ad move is a proposal. Only the workspace owner can grant the scope that lets an agent propose one.

Caps on every grant

Drafts per day, publishes per day and a daily paid budget. A spent cap is a clear tool error the agent can read.

The agent is named

Every row an agent writes shows the grant's name. Activity, change history and Settings all say who did what.

Never more than you

A grant runs as the person who made it, with what their role allows today. Leave the workspace and the grant stops working.

Your workspace only

No tool returns another tenant's data, a pooled email or the network's numbers. Consent, Global Privacy Control and opt-outs are honoured for you.

Connect

One endpoint. Two minutes.

Make a key in OpenServe under Settings › Organization › Connectors & keys › API & agents, tick the families the agent may use, then paste one of these.

claude mcp add --transport http openserve \
  https://www.openserve.com/api/v1/mcp \
  --header "Authorization: Bearer os_sk_YOUR_KEY"

{
  "mcpServers": {
    "openserve": {
      "url": "https://www.openserve.com/api/v1/mcp",
      "headers": { "Authorization": "Bearer os_sk_YOUR_KEY" }
    }
  }
}

curl https://www.openserve.com/api/v1/mcp \
  -H "Authorization: Bearer os_sk_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -H "MCP-Protocol-Version: 2025-06-18" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

# discovery, no key needed
curl https://www.openserve.com/.well-known/openserve.json

# search published content, then read with the person's own access
curl https://www.openserve.com/api/v1/open/search \
  -H "Authorization: Bearer os_sk_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query":"election"}'

Building an agent product for other people? Skip pasted keys. OpenServe speaks OAuth 2.1 with dynamic client registration, so your users land on a consent screen, pick a workspace and the families you may use, and can revoke you any time. A 401 from the endpoint names the metadata your MCP client needs to find the flow on its own.

For publishers

Get paid when agents read you.

Agents are becoming readers. OpenServe makes them paying ones, without a second paywall to maintain.

/ 01
Publish once
Your journal on OpenServe is already readable by agents through the open gateway. Import an archive, syndicate a feed, or write here.
/ 02
Your wall holds
An agent reads with the access of the person behind it: your member, or a paid OpenServe subscriber if you joined the pool. Everyone else gets your free opening and your offer.
/ 03
Earn on usage
Opt your journal into the pool and you share subscription revenue in proportion to paid readers' reads of your members-only posts. One reader counts once per post, however many agents fetched it.
/ 04
See the receipts
Every served read carries a signed source receipt and your canonical link. get_content_usage is your statement of agent reads by post.

Plans

The agent rides your OpenServe plan.

There is no separate API product and no per-call credit to count. An agent's work draws on the same plan the person's own work does.

free

Connect an agent and read your own workspace.

API keys and the MCP server
The site tag and visitor reads
Drafts filed for your approval

Start free

pro most teams

$24.99 / month

For an owner whose agent does the weekly marketing.

Everything in Free
More room for agent runs
Subscriber reading in every OpenServe app

Get Pro

max

$199 / month

For teams running agents all day.

Everything in Pro
The most room for agent runs
Subscriber reading in every OpenServe app

Get Max

Prices in USD, billed monthly; annual billing is cheaper. Ad spend goes to your own connected ad accounts and is never charged by an agent. Current limits for each plan are on openserve.com.

Help

Questions people ask first.

01 /Can the agent email my customers?

No. It can draft an email and file it. A person approves it in OpenServe › Activity, and that approval is what sends. The same holds for social posts and paid changes.

02 /Does it identify anonymous visitors?

It names companies from business networks, and it names people only when they gave your business their email. It does not buy a person's identity from an IP address, and a network-recognised visitor is shown as recognised, never named.

03 /What does my site need?

One script tag. Sites, journals and funnels built on OpenServe carry it already. Consent, Global Privacy Control and opt-outs are handled by the tag.

04 /Which agents work?

Anything that speaks the Model Context Protocol over HTTP: Claude, Cursor, Codex, n8n and custom agents. Protocol versions 2025-06-18, 2025-03-26 and 2024-11-05 are supported. Responses are JSON; there is no streaming transport.

05 /How do I cut an agent off?

Revoke its key or consent in Settings. It stops on the next call. Keys can also carry an expiry date when you make them.

06 /Can an agent buy a subscription for me?

No. When you lack access to an article the agent gets the free opening and the offer links, and shows them to you. Buying is always yours.

07 /I am an agent. Where do I start?

Read /llms.txt on this site for the short version and /llms-full.txt for every tool with its scope. Then call tools/list with the key your person gave you; the server lists only what your grant carries.

openserve // sign upREADY

Give your agent something real to do.

Make a key, tick the families, paste one line. Your first answer about who visited takes about two minutes.

Get an API key Read the tool reference

Your agent runs the growth stack. You approve.

Turn visits into a list, and a list into people who come back.

Know who is on your site

Catch the returning reader

Build audiences in plain words

Win them back

Read what worked

Connect once. Then just ask.

53 tools in 12 families. Grant only what the job needs.

Built so you can hand an agent the keys.

Reaching a person is never a tool

Spending is filed, not applied

Caps on every grant

The agent is named

Never more than you

Your workspace only

One endpoint. Two minutes.

Get paid when agents read you.

Publish once

Your wall holds

Earn on usage

See the receipts

The agent rides your OpenServe plan.

Questions people ask first.

Give your agent something real to do.