LinkedIn from Claude Code and the terminal

Claude Code, in one command

claude mcp add --transport http blabigo https://studio.blabigo.ai/api/mcp/linkedin

Claude Code runs OAuth discovery against the endpoint and opens a browser for you to approve. No key to create, copy or leave in a dotfile.

The CLI, for everything that should not need a conversation

Reporting, release automation and anything on a schedule are deterministic. They belong in a script.

Install and authenticate

npm install -g @blabigo/cli
blabigo auth login --key mcp_live_your_key_here

Stored at ~/.config/blabigo/config.json with owner-only permissions. In CI, skip the login and set BLABIGO_API_KEY as a secret instead.

Queue from a release job

blabigo posts create --account wla_123 \
  --at "$WHEN" \
  --file release-notes.md \
  --idempotency-key "release-$GITHUB_SHA"

The idempotency key is the important part. A posts create that times out and gets retried is the realistic way to double-post; a repeat with the same key returns the original post instead of creating a second one.

Pipe content in

cat announcement.md | blabigo posts create --account wla_123 --draft -

Exit codes

Distinct enough that a CI job can tell a bad argument from an expired credential without parsing output.

0

Success.

1

Request or server error.

2

Usage error — a malformed or missing argument.

3

Auth error: missing, invalid or insufficiently scoped credential. On a scope failure the CLI names the scope you are missing.

Every command accepts --json for machine-readable output, which also suppresses the confirmation prompt on posts cancel.

Frequently asked questions

How do I use LinkedIn from Claude Code?

Run one command to add Blabigo's MCP server over HTTP transport, approve the OAuth flow in your browser, and the LinkedIn tools become available in your Claude Code session. From there you can ask it to read analytics, draft posts from the code you just wrote, and queue them.

Can I schedule LinkedIn posts from the terminal?

Yes, with the Blabigo CLI. Install it, authenticate once with an API key, and posts create, reschedule, cancel and the analytics commands are all available. Every command takes --json for machine-readable output, which also suppresses the confirmation prompt on cancel.

Can I post to LinkedIn from CI?

Yes. Skip the login step and set BLABIGO_API_KEY as a secret in the CI environment. Pass a stable --idempotency-key so a retried job returns the original post rather than queueing the same content twice — a timed-out request you retry is the realistic way to double-post, and the key is what prevents it.

Where does the CLI store my API key?

In a config file under XDG_CONFIG_HOME, defaulting to ~/.config/blabigo/config.json, written with owner-only permissions. auth status prints only the key's 18-character prefix, never the whole key. In CI, use the environment variable instead of writing a file.

Does the CLI use MCP or its own API?

Both, depending on how you invoke it. Normal commands call Blabigo's HTTP API. Running blabigo mcp turns the same binary into an MCP server that speaks the protocol on stdin and stdout, which is how clients that cannot reach a remote server or do not implement OAuth still get the full tool set.

Can a script publish to LinkedIn immediately?

No, and this is deliberate rather than an oversight. posts create requires either --at or --draft, with no default, and the minimum scheduling lead time is 60 seconds. The limits apply to the CLI exactly as they apply to agents and the web app — a runaway script and a runaway agent do the same damage, so they meet the same wall.