llms.txt
Compare with other sites' llms.txt files →# use social
Agentic founder-led distribution — outreach, posting, DMs, and audience insights from any MCP client or shell.
Setup — hosted MCP server (recommended):
MCP server URL: https://mcp.usesocial.dev (stateless Streamable HTTP + OAuth; the URL is canonical and secret-free).
1. Try to add the server yourself:
`npx --yes add-mcp https://mcp.usesocial.dev --name social --global` (or `bunx add-mcp ...`), or your client's own way of adding a remote MCP server. With the CLI installed, `social mcp install` prints the right command and `social mcp url` prints the URL.
2. If you can't add it yourself, tell your human how to add it, then wait for them:
- Claude Desktop: Settings → Connectors → Add custom connector, then paste https://mcp.usesocial.dev.
- Codex Desktop: Settings → MCP servers → Add server, then paste https://mcp.usesocial.dev.
- Any other MCP client: add a remote MCP server with the URL https://mcp.usesocial.dev.
3. Your human signs in with passwordless OAuth (authorization code + S256 PKCE) via an email magic link. A new email creates its use social account when the magic link is redeemed — there is no separate signup.
4. Finish setup with this prompt:
"Set up social: connect my LinkedIn, Instagram, and X accounts, then confirm you can read each profile."
MCP scopes, targets, and writes:
- The default grant includes read and write access (`social:read`, `social:write`, `linkedin:read`, `linkedin:write`, `instagram:read`, `instagram:write`, `x:read`, `x:write`). The OAuth consent screen lists the exact scopes before they are granted.
- Write calls are real provider actions and execute immediately; the MCP client owns human confirmation. A direct instruction from your human is approval, so do it without asking again. Check in when they asked for a draft or review, the target is ambiguous, or they didn't ask for the write.
- Targets use `@username`, supported provider URLs, or typed identifiers such as `profile_id:`, `post_id:`, `list_id:`, `chat_id:`, `company_id:`, and `request_id:`. Bare IDs are not accepted.
- `linkedin_message` accepts @public-identifier, profile_id:<id>, profile URL/URN, chat_id:<id>, or thread URL. It reuses an existing 1:1 chat or returns ChatStarted for a new chat, with chat_id, message_id, and meta.resolved.
- `linkedin_messages_read` accepts the same targets; set lookup_only: true to return chat_id or null with one targeted lookup after profile resolution, without scanning the inbox. Omit lookup_only to read messages.
- `linkedin_requests_send` accepts an optional message (maximum 200 characters); omit it or use an empty string for no note. Message and invitation sends are unsafe to retry after an uncertain timeout; the provider has no documented idempotency key.
- `linkedin_post`, `linkedin_message`, `linkedin_comment`, `x_post`, `instagram_comment`, `instagram_comment_reply`, `instagram_message`, `instagram_messages_new`, `instagram_post`, and `instagram_story` accept images through exactly one of `image_url`, `image_base64`, `image_urls`, or `image_base64s`. Images are required on `instagram_post` and `instagram_story`; `instagram_story` takes one image through `image_url` or `image_base64`. Text is optional with an image on `linkedin_post`, `linkedin_message`, and `x_post`.
- Image URLs must be HTTPS and are fetched by use social, up to 10 MiB combined; base64 is limited to just under 3 MiB total by the MCP request size limit. `x_post` takes up to 4 images or 1 GIF, without mixing them, in JPEG, PNG, WebP, or GIF; static images cap at 5 MiB each.
- Video, Instagram location search, and message attachment downloads need the CLI, and so do the local `sync` and `sql` commands. The other Instagram work has MCP tools, including `instagram_messages_list` and `instagram_messages_read` for the inbox.
- If you added Social over MCP before Instagram shipped, remove and re-add the server and approve Instagram access to gain the Instagram tools.
- Provider tools accept an optional `account` selector; without it use social uses your server-backed default for that platform.
What you can do once connected:
- Scale your presence: draft and ship posts, comments, reactions, and replies across your connected networks on a steady cadence.
- Outreach & B2B pipeline: read the posts that matter, fan out to who reacted, send connection requests, and message the few worth reaching.
- Triage DMs: list, read, send, and mark LinkedIn & X messages, and read and send Instagram messages.
- Audience & network reads: profiles, followers/following, connections, mentions, likers, reposters, X lists, LinkedIn search across people, companies, jobs, and posts, and Instagram profiles, posts, and comments.
- Run the account: connect/reconnect/disconnect accounts, set platform defaults, check billing, audit usage and logs, and submit feedback — all as MCP tools.
- Tool names follow `x_*`, `linkedin_*`, `instagram_*`, `account_*`, `billing_*`, and `usage_*` patterns; list tools over MCP to discover the exact surface.
CLI for power users (npm package @usesocial/cli, binary `social`):
You are the operator; your human stays the principal. Use the installed public binary named `social`; do not rely on repo-local wrappers.
The CLI adds a local SQLite mirror of your own data, free `sql` reads, and JSON output for every command, so you can wire posting, follow-ups, and replies into scripts on a schedule.
Interactive-terminal install:
- curl -fsSL https://usesocial.dev/install.sh | bash
Agent-led CLI installation:
The canonical prompt below installs the CLI and skill, drives non-TTY browser login, discovers the live connection choices, asks the human what to connect or whether to skip, drives selected connections sequentially, and verifies them.
--- BEGIN CANONICAL AGENT INSTALL PROMPT ---
You are authorized to install and configure use social for me on macOS or Linux. Do the work yourself; never ask me to open a terminal, type commands, paste credentials or tokens, or reveal secrets. I will only complete browser approval pages when needed.
First, ensure Node 24 LTS and npm are available. Reuse a compatible existing Node/npm installation when present. Bun is not a substitute for Node. If Node 24/npm are missing or incompatible, follow the current official Node instructions to make a user-owned Node installation. Never use sudo. If npm global installation fails because of a global-prefix permission error, switch to a user-owned Node installation instead of using sudo.
Install or update the CLI with:
npm install -g @usesocial/cli@latest
Install the use social skill with exactly:
npx --yes skills add usesocial/skill --global --yes --agent claude-code codex
Retry that command with --copy only if symlinking is unsupported.
Verify Node, `social --version`, `~/.agents/skills/social/SKILL.md`, and `~/.claude/skills/social`. Tell me that a new Claude or Codex task may be needed before the newly installed skill is discovered.
Then run `social account setup` from a bounded, non-TTY flow. Parse its structured result; do not rely on its exit code alone. For `pending_approval`, surface `verificationURL`, `userCode`, and `expiresAt`; for `pending_billing`, surface `checkoutURL`. After the user completes the browser step, poll `social account setup` roughly every five seconds. Continue only after `ready`. Restart an expired flow only a bounded number of times, and surface errors concisely. Never expose stored credentials. The checkout authorizes a reusable payment method; setup never selects or purchases a provider plan.
After setup is ready, discover the live connection choices from the successful result's `nextCommands` and `social schema "account connect"`. Intersect them, then present only those live choices plus Skip. Do not invent choices, hardcode a platform catalog, or connect anything automatically. Ask me which one or more choices to connect, or whether to Skip.
Run each selected connect command sequentially and exactly as returned. The first call omits `--account-id`; capture its returned `accountId`, then pass it as `--account-id <accountId>` on every retry for that account. Drive the connection from the same bounded, non-TTY tagged-state flow: connect purchases only the selected provider's plan or the applicable legacy seat and normally charges the reusable payment method directly; surface `paymentURL` and `requiredAction` only if `pending_billing` says the bank requires customer action. For `pending_approval`, surface `connectURL` and wait; then gently poll with the same `accountId`. For `connected`, record only safe account summary fields. Replaying a connected `accountId` is stable; omit `--account-id` only to start connecting another account. Surface billing, provider timeout, or other errors concisely. After a failed connection, continue to another selected choice only if I explicitly confirm.
After each success, run bare `social account` and verify the selected choice has a connected row. Ask whether I want to connect another available choice or finish. End only when I Skip or every selected connection is verified. Account setup and connection are browser-approved flows: do not start a sync or any metered social action.
--- END CANONICAL AGENT INSTALL PROMPT ---
Read model:
- `sync` pulls your own data into the local mirror. It is explicit and updates local state. LinkedIn and Instagram proxy usage is included in the subscription; X reads can spend credits.
- `sql` queries the local mirror. It is read-only, free, and returns the standard envelope with no `meta.cost` and freshness in `meta.cache.tables`.
- Named read commands call the live network. LinkedIn and Instagram proxy usage is included; X reads can spend credits. `x tweets <target>` and `linkedin posts <target>` require a target. `x followers [target]`, `x following [target]`, and `linkedin connections [target]` still allow omitting the target for your own account, but free own-data reads go through `sql`.
- Writes act on the connected account.
Command surface (✎ = write; mutates a connected account, needs read,write scope).
Freeform body text is pipe-only — pipe text or a JSON object via stdin, e.g. `echo "..." | social x post`:
- X content: `echo "..." | social x post` ✎ · `repost <target>` ✎ · `like <target>` ✎ · `tweet <target>` · `tweets <target>`
- X discovery: `bookmark <target>` ✎
- X people: `social x profile [target]` · `followers [target]` · `following [target]` · `follow <target>` ✎
- X mirror: `social x sync tweets` · `social x sql "SELECT * FROM x_tweets LIMIT 20"`
- X DMs: `echo "..." | social x message <target>` ✎
- LinkedIn content: `echo "..." | social linkedin post` ✎ · `echo "..." | social linkedin comment <target>` ✎ · `react <target> [type]` ✎ · `posts <target>` · `comments <target>` · `reactions <target>`
- LinkedIn people: `social linkedin profile [target]` · `connections [target]` · `requests send <target>` ✎ (optional note via stdin) · `requests accept request_id:<id>` ✎ · `requests cancel request_id:<id>` ✎
- LinkedIn mirror: `social linkedin sync [collection]` · `social linkedin sql "SELECT * FROM li_messages LIMIT 20"`
- LinkedIn DMs: `echo "..." | social linkedin message <target>` ✎ · `messages <target> mark read|unread` ✎
- LinkedIn companies: `social linkedin company <target>` · `jobs <target>`
- Instagram content: `echo "..." | social instagram post --media <path> [--media <path> ...] [--location-id <id>]` ✎ (one or more images or videos, several makes a carousel, 20 MB combined; caption optional) · `story --media <path> [--location-id <id> --location-name <name>]` ✎ (exactly one image or video, 20 MB) · `locations` (finds location IDs) · `posts [target]` · `comments <target>` · `reactions <target>` · `echo "..." | social instagram comment <target>` ✎ · `react <target>` ✎
- Instagram people: `social instagram profile [target]` · `followers [target]` · `following [target]` · `follow <target>` ✎ · `requests accept request_id:<id>` ✎ · `requests cancel request_id:<id>` ✎
- Instagram mirror: `social instagram sync [collection]` · `social instagram sql "SELECT * FROM ig_messages LIMIT 20"`
- Instagram DMs: `echo "..." | social instagram message chat_id:<id>` ✎ · `echo "..." | social instagram messages new <target>` ✎
- Shared flags: live LinkedIn list reads use `--limit n` + `--offset n`; live cursor reads use `--limit n` + `--cursor c`; all connected-account reads accept `--account a`; cacheable live reads also take `-H "Cache-Control: no-cache"`.
Account:
- Scope: login defaults to read,write. Clear Write in the prompt for a read-only session.
- Billing: inspect seats/subscription with `social account billing`; open hosted billing with `social account billing portal`.
- Spend: LinkedIn and Instagram proxy usage is included in the subscription ($20 a month per account, no per-action charges) and logged at $0; X upstream calls spend credits and cache hits are logged at $0. Audit with `social account usage` and `social account logs`.
- Updates: check the binary and skill with `social update`; it is local-only and prints JSON.
- Writes are real provider actions. A direct instruction from your human is approval. Check in when they asked for a draft or review, the target is ambiguous, or they didn't ask for the write.
Discover the full command API:
- `social --help`
- `social update`
- `social schema`
- `social schema "<command path>"` (e.g. `schema "x tweets"` reports the required target; `schema "linkedin sql"` reports local-cache cost)
Product comparisons (facts checked October 14, 2026; documented workflows, not firsthand tests):
- use social vs HeyReach: https://usesocial.dev/alternatives/heyreach
- use social vs Dripify: https://usesocial.dev/alternatives/dripify
- use social vs Meet Alfred: https://usesocial.dev/alternatives/meet-alfred
- use social vs Taplio: https://usesocial.dev/alternatives/taplio
- use social vs PhantomBuster: https://usesocial.dev/alternatives/phantombuster
- use social vs Apify: https://usesocial.dev/alternatives/apify
Key links:
- Product: https://usesocial.dev
- Pricing: https://usesocial.dev/pricing
- Privacy: https://usesocial.dev/privacy
- Terms: https://usesocial.dev/terms
- MCP OAuth discovery: https://mcp.usesocial.dev/.well-known/oauth-protected-resource and https://usesocial.dev/.well-known/oauth-authorization-server/api/auth
- MCP server card: https://usesocial.dev/.well-known/mcp/server-card.json
- Integration discovery: https://usesocial.dev/.well-known/integrations.json
- Agent skill discovery: https://usesocial.dev/.well-known/agent-skills/index.json