For MCP Server Developers

Earn revenue every time your MCP tool is called.

Boost Boss is the only ad network built natively into the Model Context Protocol. Your server adds three lines. Claude Desktop, Cursor, Cline, and every MCP host renders the rest.

Start as a publisher →

See it appear

When your tool runs, your output renders first.
The sponsored block slides in after.

No interruption. No latency. The user always gets your tool result before they see the ad.

Claude Desktop showing a sponsored block in a tool response

The sponsored block is a structured payload Boost Boss returns alongside your tool result. The host (Claude Desktop, Cursor, Cline) renders it natively — same chrome as the rest of the response, with a clear sponsorship label.

How it works

From `npm install` to first impression in under 10 minutes.

Connect your MCP server

Add three lines: install @boostbossai/lumi-mcp, init with your publisher ID, attach to a tool handler.

Tools keep working

Your existing tool output is unchanged. Boost Boss appends a sponsored block — never replaces, never delays.

Earn per call

Boost Boss attaches relevant ads to tool responses. You earn on every impression and every click.

Integration snippet

Three lines, one tool handler.

import { LumiMCP } from '@boostbossai/lumi-mcp';
const lumi = new LumiMCP({ publisherId: 'pub_xxx' });

// Inside any existing tool handler:
const ad = await lumi.fetchAd({ context: request.params.name });
return { content: [...result, ad.toMCPBlock()] };

That's it. The MCP host renders the ad payload natively. Full docs →

Claude Desktop with a sponsored block rendered inside a tool response

Real render. The sponsored block ships as a structured payload — the host (Claude Desktop, Cursor, Cline) draws the chrome.

Who this is for

If any of these sound like you, MCP is your path.

✓You ship an MCP server listed on mcp.so, Smithery, Glama, or PulseMCP.
✓Your server is called by users of Claude Desktop, Cursor, Cline, Continue, Zed AI, or Windsurf.
✓You'd like a real revenue stream beyond GitHub Sponsors.
✓You build for developer audiences and want premium CPMs that match the audience value.

Revenue example

What "earning per call" actually looks like.

Illustrative — not a guarantee

Daily tool calls5,000

Ad impressions per day (1 in 3 calls)~1,500

Average CPM (developer audience premium)$12

Monthly publisher revenue~$540

Numbers are illustrative for a moderately active MCP server. Actual revenue depends on tool-call volume, fill rate, advertiser demand, and your audience composition. CPMs vary; developer-tooling traffic typically sits at the high end.

Frequently asked

The questions every MCP dev asks first.

Will ads break my MCP integration?

No. Ads are appended, not substituted. Your tool's primary output is unchanged — the host renders your tool result first, the sponsored block second.

What does an MCP ad look like to the user?

A clearly labeled sponsored block in the tool response, rendered by the host (Claude Desktop, Cursor, etc.). The user always sees both the answer and the disclosure — there's no hidden injection.

Can I block specific advertisers?

Yes. Category-level blocks (e.g., no recruiting ads) and domain-level blocks (e.g., never these specific competitors) — all controlled from your publisher dashboard.

Does this work with stdio AND HTTP transports?

Yes — both transports are supported. @boostbossai/lumi-mcp auto-detects which one your server uses; the SDK works identically across both.

Is this approved by Anthropic?

Boost Boss operates within MCP's public protocol — we don't require Anthropic's approval. We follow MCP disclosure norms strictly: every sponsored block is labeled, never disguised as tool output.