revenueos — Claude Code MCP server: what it does, how to install
An MCP server that audits websites, ad platforms, and mailboxes. It generates concrete revenue actions and waits for approval before touching production.
claude mcp add --env REVENUEOS_ROOT=<REVENUEOS_ROOT> --env ANTHROPIC_API_KEY=<ANTHROPIC_API_KEY> --transport stdio revenueos -- uvx revenueosWhat revenueos does
RevenueOS inspects web pages, Google and Meta ad accounts, lead lists, and email boxes. Internal workers operate strictly in read-only mode, so they never spend budget or publish text on their own. The system identifies issues such as missing meta tags, absent canonical URLs, and missing sitemaps, then structures each finding as an actionable card.
Every modification stops at an approval gate. Even approved tasks fail to deploy to WordPress or a Git repository if that connection lacks an active switch for changes. Once an action runs, the server pulls fresh metrics to record verified before-and-after evidence. The server will not run without an ANTHROPIC_API_KEY supplied in the environment.
A local control panel runs on http://127.0.0.1:8791. You can run an immediate zero-install audit against any URL with uvx revenueos demo.
What it helps with
- discover missing meta descriptions, canonical headers, and sitemaps
- pinpoint wasteful ad campaigns across connected accounts
- gate autonomous production deployments behind manual user review
- track factual before-and-after performance metrics without synthesized data
Example prompts for the agent
- Inspect my site with revenueos and show actionable defects
- Prepare a sitemap generation task and wait for my confirmation
- Audit connected ad channels to highlight campaigns burning cash
How to install revenueos
Platform CLI
claude mcp add --env REVENUEOS_ROOT=<REVENUEOS_ROOT> --env ANTHROPIC_API_KEY=<ANTHROPIC_API_KEY> --transport stdio revenueos -- uvx revenueosReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from revenueos <command>
Platform CLI
codex mcp add revenueos --env REVENUEOS_ROOT=<REVENUEOS_ROOT> --env ANTHROPIC_API_KEY=<ANTHROPIC_API_KEY> -- uvx revenueosReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from revenueos <command>
Config file
{
"mcpServers": {
"revenueos": {
"command": "uvx",
"args": [
"revenueos"
],
"env": {
"REVENUEOS_ROOT": "<REVENUEOS_ROOT>",
"ANTHROPIC_API_KEY": "<ANTHROPIC_API_KEY>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from revenueos <command>
Config file
{
"servers": {
"revenueos": {
"type": "stdio",
"command": "uvx",
"args": [
"revenueos"
],
"env": {
"REVENUEOS_ROOT": "<REVENUEOS_ROOT>",
"ANTHROPIC_API_KEY": "<ANTHROPIC_API_KEY>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from revenueos <command>
Platform CLI
gemini mcp add -e REVENUEOS_ROOT=<REVENUEOS_ROOT> -e ANTHROPIC_API_KEY=<ANTHROPIC_API_KEY> revenueos uvx revenueosReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from revenueos <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about revenueos
How to install revenueos in Claude Code?
Run claude mcp add revenueos -e ANTHROPIC_API_KEY=<ANTHROPIC_API_KEY> -- uvx revenueos. You can also supply --env REVENUEOS_ROOT=<REVENUEOS_ROOT> if you need a dedicated workspace directory.
What does revenueos do?
It reads marketing and website data to identify growth blockers. It turns those insights into proposals and executes them only after you give approval.
Can revenueos publish unwanted edits autonomously?
No, background workers cannot write to external services. Every change requires an explicit approval and a connection configured to permit edits.
