Agentic Account

io.github.pooriaarabPublished by GitHub account pooriaarabv0.1.0Updated Oct 24, 2026

Set up and track brand social accounts and their connections.

The publisher's own server: agentic.no

Overview

AI-generated overview

Local MCP server that plans and tracks brand social-account setup across ten platforms, with checklists, state tracking and credential references.

What you can do
  • Create and list tracked brand accounts with platform, handle and email or phone references
  • Show one account's details and its per-platform setup checklist
  • Advance an account through planned, creating, verifying, profile, connecting, warming and active states, including paused and needs-human
  • Record a connection provider with a credential reference and generate warmup guidance
  • Report setup costs across tracked accounts
When to use it
Useful when an assistant helps a brand or launch team work through creating, verifying and connecting accounts on platforms such as Instagram, TikTok, X, LinkedIn or YouTube, and you want each blocking step visible. It tracks the work rather than publishing or scheduling posts.
Requirements
Runs locally over stdio via npx from the npm package agentic-account; no authentication, environment variables or headers are declared. The in-process registry is suited to guided sessions, and persisting records requires using the library with your own storage.
Before you install
It does not create accounts or bypass platform checks; CAPTCHA, SMS and identity verification always resolve to needs-human. Credential fields accept only references such as env: or vault:// values and reject raw secrets, so keep real credentials in a vault. Respect each platform's terms of service, since some prohibit automated account creation, and checklists may lag platform changes.

Installation

In SourceWeft

  1. Open Agentic Account in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

agentic-account

[npm version] [npm downloads per month] [license]

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

sh
npm install agentic-account

Two runtime dependencies: the MCP SDK and zod.

Track your first account

sh
agentic-account account create --platform instagram --handle acme --email-ref BRAND_EMAILagentic-account account checklist --id <id>agentic-account account advance --id <id> --state needs-humanagentic-account account connect --id <id> --provider direct --credential-ref vault://team/instagramagentic-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

sh
agentic-account account create --platform <name> --handle <handle> [--email-ref <ref>] [--phone-ref <ref>]agentic-account account listagentic-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 costsagentic-account mcp

Library

ts
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 -> creatingregistry.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.

Alternatives and related tools

  • 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

Source: README.md at commit 32e8a4a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestOct 15, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Agentic integrations