adcom

adcom is the published CLI for Ad Computer.

It is a thin, remote-friendly shim: authenticate with device flow, store a small local session, inspect the hosted MCP surface, and expose that hosted MCP worker to local agents over stdio.

It remains oriented around the hosted Ad Computer product. The repo's first self-hostable OSS target is apps/mcp; this CLI is still the reference client for the hosted control plane flow.

Install

npm install -g adcom

Requirements

• Node.js >=22.12.0

Core Commands

adcom login
adcom whoami
adcom logout
adcom mcp inspect-tools
adcom mcp serve

Typical Flow

Login from any machine

adcom login

By default, adcom login prints a device approval URL and waits for the user to approve it from any browser. Use --open only when the same machine has a local browser available.

Verify identity and inspect the hosted surface

adcom whoami
adcom mcp inspect-tools

Run the local MCP bridge

adcom mcp serve

The bridge proxies the hosted MCP server over stdio. It does not add local workflow helpers on top of the hosted surface.

First Meta Read

Once the bridge is running and Meta is connected, the canonical first read is:

1. Call meta_get_ad_accounts
2. Pick an accessible account_id
3. Call meta_review_account_performance with that explicit account_id

MCP Bridge

The CLI can expose the hosted Ad Computer MCP worker over local stdio:

adcom mcp serve

That is the command local agent clients should generally run when they expect a stdio MCP server but you want execution to happen against the hosted Ad Computer backend.

To inspect the hosted tool surface:

adcom mcp inspect-tools

Direct hosted MCP clients should call:

meta_get_ad_accounts
meta_review_account_performance

and pass an explicit account_id to the review tool.

JSON Mode

Several commands support --json so agents or automation can parse structured output instead of relying on human-readable text.

Common examples:

adcom login --json
adcom whoami --json
adcom logout --json
adcom mcp inspect-tools --json

adcom login --json emits device-flow events such as login_url and login_complete.

Local State

The CLI stores small local state under ~/.adcom/:

• config.json keeps control_plane_url and the latest mcp_url
• session.json keeps the local session token

adcom logout deletes only session.json and leaves the non-secret endpoint config in place.

Compatibility

ad-computer remains available as a compatibility binary alias, but adcom is the canonical command name.

There is no longer any local workspace-context workflow, provider account-selection management, or local review wrapper tool in the CLI.

Control Plane And Hosted MCP

Default product URLs:

• Website: https://ad.computer
• App: https://app.ad.computer
• MCP: https://mcp.ad.computer/mcp

Local Development

From the monorepo root:

vp run adcom#build
vp run adcom#test

The CLI is the only workspace package intended for npm publish. The repo's contracts and provider-meta packages are internal-only.