ACAd Computer
Open App

Getting Started

The basic flow from public site to app sign-in, Meta connection, and first client usage.

Ad Computer
docsgetting-started

This is the shortest path through Ad Computer.

1. Open the app

Go to app.ad.computer and sign in.

The app is the browser control plane for:

  • user authentication
  • workspace identity
  • Meta OAuth kickoff
  • MCP configuration handoff

2. Connect Meta

After signing in, open the Meta connector inside the app and complete the workspace connection flow.

That step attaches the Meta account to the active workspace so downstream tools can use it safely.

3. Choose how you want to work

Once the workspace is connected, you have two immediate paths:

  • use the hosted MCP surface from a client
  • authenticate the local CLI and work through adcom

If you want the CLI path, continue with CLI.

4. Verify the workspace

The quickest local verification flow is:

code
adcom login
adcom whoami
adcom doctor

That confirms:

  • the CLI can authenticate against the control plane
  • the current workspace is known
  • the hosted MCP surface is reachable
  • the Meta connection is usable

5. Bridge MCP locally when needed

If a local client expects stdio MCP instead of direct HTTP, run:

code
adcom mcp serve

This exposes the hosted Meta MCP worker through a local bridge while keeping the remote execution surface unchanged.

Related docs