Agent access

Cheers exposes a minimal bearer-token API for agents. Sign in, open /me, then use Agent access to Reveal or Copy your token. Use Regenerate token there to rotate it; this invalidates the old token everywhere. Keep it private and treat it like a password.

Environment:

export CHEERS_TOKEN="your-dashboard-token"
export CHEERS_API_BASE="https://cheers.fedeponte.com" # optional; this is the default

MCP client config:

{
  "mcpServers": {
    "cheers": {
      "command": "deno",
      "args": ["run", "-A", "https://cheers.fedeponte.com/mcp.ts"],
      "env": {
        "CHEERS_TOKEN": "your-dashboard-token",
        "CHEERS_API_BASE": "https://cheers.fedeponte.com"
      }
    }
  }
}

The MCP command is deno run -A https://cheers.fedeponte.com/mcp.ts. CHEERS_API_BASE is optional and defaults to https://cheers.fedeponte.com.

MCP tools:

• cheers_get_profile
• cheers_update_profile
• cheers_list_connections
• cheers_get_connection
• cheers_save_connection
• cheers_update_connection
• cheers_remove_connection
• cheers_search_connections

MCP and CLI agent access use the HTTP /api endpoints and do not need --unstable-kv.

Optional power-user CLI:

deno run -A https://cheers.fedeponte.com/cli.ts whoami
deno run -A https://cheers.fedeponte.com/cli.ts profile
deno run -A https://cheers.fedeponte.com/cli.ts profile set --bio "Building agent CRM." --tags ai,crm
deno run -A https://cheers.fedeponte.com/cli.ts connections
deno run -A https://cheers.fedeponte.com/cli.ts connection <ownerSlug>
deno run -A https://cheers.fedeponte.com/cli.ts connections --json