Connect an AI Assistant (MCP)

MonetizationOS runs a remote MCP server. Your AI assistant connects to it over the internet, so there is nothing to install or run on your machine and no API key to copy. You sign in with your MonetizationOS account and choose which organizations the assistant can use.

Server URL

Every client uses the same URL:

https://app.monetizationos.com/api/mcp

Before you start

• You need a MonetizationOS account that belongs to at least one organization.
• You need an AI client that can connect to remote MCP servers with OAuth. The clients below all can.

How connecting works

The steps are the same in every client. Only where you paste the URL changes.

The assistant can never do more than your own account can. What it sees and changes is limited by your role in each organization.

Set up your client

Claude (claude.ai and Claude Desktop)

1. In Claude, open Customize > Connectors, click + Add, then Add custom connector.
2. Enter a name, for example MonetizationOS, and the URL https://app.monetizationos.com/api/mcp, then click Continue until you reach the sign-in options.
3. Under OAuth client, choose Use Claude's published identity (Recommended).
4. Click Add, then Connect if asked, and sign in.

On a Team or Enterprise plan, an Owner adds the connector once for the whole Claude organization, from Organization settings > Connectors. Each member then clicks Connect and signs in with their own account. See Anthropic's custom connector guide if your menus look different.

Claude Code

Run this in your terminal:

claude mcp add --transport http monetizationos https://app.monetizationos.com/api/mcp

Then start Claude Code, type /mcp, choose monetizationos and select Authenticate.

Add --scope user to use it in every project. To share it with your team through the repository, add it to .mcp.json instead:

{
    "mcpServers": {
        "monetizationos": {
            "type": "http",
            "url": "https://app.monetizationos.com/api/mcp"
        }
    }
}

ChatGPT

1. In the ChatGPT desktop app, open Settings and select MCP servers.
2. Select Add server.
3. Enter a name, choose Streamable HTTP and enter https://app.monetizationos.com/api/mcp.
4. Save, then select Restart.
5. Select Authenticate when prompted, and sign in.

Some ChatGPT plans and workspaces restrict custom MCP servers, and on Business and Enterprise plans an admin may control them. See OpenAI's MCP guide if your menus look different.

Codex

Run these in your terminal:

codex mcp add monetizationos --url https://app.monetizationos.com/api/mcp
codex mcp login monetizationos

Or add it to ~/.codex/config.toml yourself, then run the login command above:

[mcp_servers.monetizationos]
url = "https://app.monetizationos.com/api/mcp"

VS Code (GitHub Copilot)

Create .vscode/mcp.json in your project, or run MCP: Open User Configuration from the Command Palette to use it everywhere:

{
    "servers": {
        "monetizationos": {
            "type": "http",
            "url": "https://app.monetizationos.com/api/mcp"
        }
    }
}

Click Start above the server entry, then sign in when VS Code asks. The tools appear in Copilot Chat's agent mode.

Other clients

Most clients take the same two values: a server name and the URL. If yours asks for a JSON config, this shape is the most common:

{
    "mcpServers": {
        "monetizationos": {
            "url": "https://app.monetizationos.com/api/mcp"
        }
    }
}

Your client must support OAuth with Client ID Metadata Documents, the sign-in method in the current MCP specification. Older clients that only support dynamic client registration can't connect.

Try it

Once connected, ask your assistant something like:

• "Which MonetizationOS organizations can you see?"
• "List the plans in my organization and the features each one grants."
• "Explain how my surfaces and experiences are set up."

The server gives your assistant these tools:

Change or remove access

To change which organizations or access level the assistant has, remove MonetizationOS from your client, add it again and choose differently when you sign in.

Troubleshooting