Overview

Ad Computer is a marketing operating system for AI agents.

Meta Ads is the live wedge today. Over time, Ad Computer expands toward analytics, reporting, and other marketing tooling while keeping one consistent operating path for agents.

It combines three surfaces:

• ad.computer is the public marketing site.
• app.ad.computer is the browser control plane for sign-in, workspace context, and Meta connection.
• adcom is the local CLI for workflow, verification, and MCP bridging.

There is also a hosted Ad Computer MCP surface behind the product flow:

• https://mcp.ad.computer/mcp

How the pieces fit together

The browser app owns identity and workspace context. Once a workspace is connected to Meta, Ad Computer can issue the credentials needed for downstream clients.

The default flow is:

1. Open the app and sign in.
2. Connect the active workspace to Meta.
3. Use the CLI or an MCP-capable client against the hosted surface.

This keeps the Meta OAuth step in one place while still letting local tooling and clients work against a stable hosted endpoint.

Product surfaces

App

The app is the source of truth for authentication and workspace setup. It is where users connect Meta and generate the access flow used by the rest of the product.

CLI

The CLI is intended for local workflow. It can authenticate through the app, inspect the current workspace, verify connectivity, and expose the hosted MCP worker over local stdio.

MCP

The hosted MCP worker provides the execution surface for Meta Ads operations. Once a workspace is authenticated and connected, MCP clients can call the hosted server directly.

Next reads

• Start with Getting started for the basic setup flow.
• Read CLI for installation and day-to-day commands.