io.github.pooriaarab/agentic-account

Official registry Marketing and sales

Set up and track brand social accounts and their connections.

What can you do with io.github.pooriaarab/agentic-account?

  • A launch agent tracks ten platform accounts for one brand and shows you exactly which step blocks each one.
  • An ops script generates per-platform setup checklists instead of keeping them in a doc.
  • A team vault keeps real credentials; the registry stores only env: and vault:// references.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package agentic-account
Claude Code
claude mcp add agentic-account -- npx -y agentic-account@0.1.0 mcp
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "agentic-account": {
            "command": "npx",
            "args": [
                "-y",
                "agentic-account@0.1.0",
                "mcp"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. agentic-account
  2. Install
  3. Track your first account
  4. CLI
  5. Library
  6. MCP server
  7. Use cases
  8. Alternatives and related tools
  9. Safety
  10. Limits
  11. License

agentic-account

npm package · CLI · Library · Safety · Limits

agentic-account is a local-first TypeScript library, CLI, and MCP server that plans and tracks brand social-account setup across ten platforms. It guides the workflow — checklist, state machine, warmup plan — and routes every verification gate to a human instead of bypassing it.

Install

npm install agentic-account

Two runtime dependencies: the MCP SDK and zod.

Track your first account

agentic-account account create --platform instagram --handle acme --email-ref BRAND_EMAIL
agentic-account account checklist --id <id>
agentic-account account advance --id <id> --state needs-human
agentic-account account connect --id <id> --provider direct --credential-ref vault://team/instagram
agentic-account account warmup --id <id>

advance moves the account through planned → creating → verifying → profile → connecting → warming → active, with paused and needs-human wherever a platform demands proof a person is present.

CLI

agentic-account account create --platform <name> --handle <handle> [--email-ref <ref>] [--phone-ref <ref>]
agentic-account account list
agentic-account account show --id <id>
agentic-account account checklist --id <id>
agentic-account account advance --id <id> --state <state>
agentic-account account connect --id <id> --provider <provider> --credential-ref <ref>
agentic-account account warmup --id <id>
agentic-account costs
agentic-account mcp

Library

import { AccountRegistry, platformRequirements } from "agentic-account";

const registry = new AccountRegistry();
const account = registry.create({ platform: "instagram", handle: "acme", emailRef: "BRAND_EMAIL" });
registry.advance(account.id);                    // planned -> creating
registry.advance(account.id, "needs-human");     // CAPTCHA / SMS / identity check

platformRequirements covers Instagram, TikTok, X, LinkedIn, Facebook, Reddit, Threads, Bluesky, YouTube, and Pinterest — each platform's checklist, verification steps, and warmup guidance.

MCP server

agentic-account mcp (or npx agentic-account-mcp) serves the registry on stdio: account_create, account_list, account_show, account_checklist, account_advance, account_connect, account_warmup, and get_cost_report.

Use cases

  • A launch agent tracks ten platform accounts for one brand and shows you exactly which step blocks each one.
  • An ops script generates per-platform setup checklists instead of keeping them in a doc.
  • A team vault keeps real credentials; the registry stores only env: and vault:// references.
  • Social schedulers (Buffer, Hootsuite, Later) publish to accounts you already own; this pack tracks the work of getting those accounts created, verified, and connected.
  • Password managers store credentials; agentic-account references them without storing secrets.

Safety

  • It does not create accounts, and does not bypass platform checks — CAPTCHA, SMS codes, and identity verification always resolve to needs-human.
  • Credential fields accept only references such as BRAND_EMAIL, env:BRAND_EMAIL, or vault://team/social; raw secrets are rejected.
  • Respect each platform's terms of service; some prohibit automated account creation entirely.

Limits

  • The in-process CLI registry suits guided sessions; use the library to persist records in your own storage.
  • Checklists describe requirements as of the recorded platform version — platforms change their flows without notice.

License

MIT

Frequently asked questions

What is io.github.pooriaarab/agentic-account?

Set up and track brand social accounts and their connections.

How do I install io.github.pooriaarab/agentic-account?

It runs on your machine. In Claude Code: claude mcp add agentic-account -- npx -y agentic-account@0.1.0 mcp. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.pooriaarab/agentic-account need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is io.github.pooriaarab/agentic-account open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains io.github.pooriaarab/agentic-account?

It is published by pooriaarab. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.