Diagnostic CLI

Check selected adapter configuration and validate a publish request locally without contacting social platforms or mutating social accounts.

The social-sdk CLI never contacts a social platform. It never authenticates an account, opens a browser, uploads media or publishes content. Its only network request is one anonymous usage event per command, which you can turn off; see CLI telemetry. The package includes the executable after building or installing a packed build.

social-sdk adapters --json
social-sdk doctor --adapter zernio --json
social-sdk capabilities --adapter youtube --json
social-sdk examples --json
social-sdk validate --adapter mock --file request.json --json
social-sdk mcp --adapter youtube
social-sdk version --json
social-sdk telemetry disable --json

doctor checks the presence of environment variables for the selected adapter only. It prints their names when missing, never their values. Success means that configuration is present, not that credentials authenticate or that a platform has approved your app.

capabilities reads the actual adapter manifest. Permission, account eligibility and live behavior remain separate checks. examples returns a complete mock publish request. Save its data.request object as request.json to validate it.

validate accepts a JSON file up to 1 MiB. It runs local preparation and returns issue codes and target indexes without echoing content, URLs or account IDs. Attachment sources in the CLI must be HTTPS URLs. Thumbnails accept HTTPS URLs or existing media references. Use the TypeScript SDK to validate Blob, stream and existing media-reference attachment sources. TikTok source-domain approval cannot be inferred from a JSON URL; validate that configuration through your server’s adapter.

Validation checks declared media byte limits, item counts, MIME types, aspect ratios, and duration limits against the metadata in the request. Missing remote metadata stays unknown: the command never fetches media or stages local files.

mcp serves social_capabilities, social_doctor, social_validate and social_plan_publish to an MCP client over stdio until stdin closes. Stdout then carries protocol messages only. The tools stay offline like the other commands; see MCP server to serve read and write tools from your own application.

version prints the installed package version, which is the first thing to include in a bug report. social-sdk --version is the same command.

telemetry status, telemetry enable and telemetry disable show or change the CLI’s anonymous usage events. SOCIAL_SDK_TELEMETRY_DISABLED=1 and DO_NOT_TRACK=1 also turn them off, and they are always off in CI. CLI telemetry lists every field sent.

Every command except mcp accepts --json. The envelope contains schemaVersion: 1, command, ok, and data. Exit code 0 means the diagnostic passed; 1 means a configuration or preparation check failed; 2 means invalid arguments or input. Unknown commands and options fail rather than enabling a provider operation.