Announce your software releases on LinkedIn from Qwen Code

The short answer

You just shipped a release and the changelog is right there in your repo. Qwen Code can read it, pick the changes your users care about, and write a LinkedIn post in plain language. Connected to Finchreach, it can also queue that post on your LinkedIn account; it goes live only after you approve it.

Qwen Code, the command-line coding agent for Qwen models, supports remote MCP servers with a custom header. MCP is a standard plug that lets AI apps use outside tools, and Finchreach is a remote MCP server at https://mcp.finchreach.com/mcp. If you use Qwen Chat on the web, note that as of October 2026 we couldn’t verify custom MCP support there; use Qwen Code or another MCP client.

Why announce releases on LinkedIn?

For open-source maintainers, indie developers and small product teams, LinkedIn is where many users, buyers and future colleagues will actually see a release. But release notes are written for people who read diffs. Turning “refactor auth middleware, add retry to webhook client” into “webhooks now retry automatically when your server is down” is a translation job, and it’s usually the job nobody gets to.

Doing it from the terminal where you cut the release removes the context switch. Qwen Code already has your repository open, so it can read CHANGELOG.md, the tag, or the git log directly. Finchreach adds linkedin_create_post to publish the text and linkedin_get_profile so the post fits your role.

What do you ask Qwen Code after a release?

Point it at the source of truth and the audience:

Ask your assistant“Read CHANGELOG.md for v2.4.0 and the git log since v2.3.0. Write a LinkedIn post for people who use our library in production, not contributors. Lead with the one change they will notice most, list at most three more in plain words, thank outside contributors by first name, and end with the link to the release page. Under 200 words, no emojis.”

Review, then adjust or publish:

Ask your assistant“Drop the line about the internal refactor and mention that the upgrade has no breaking changes. Then publish it to my LinkedIn and give me the action id.”

Qwen Code calls linkedin_create_post, and the post waits at /approvals in the Finchreach dashboard. Approve it when the release is actually live, not before. You can ask Qwen Code to check whether it went out:

Ask your assistant“Check the status of that LinkedIn post action.”

How do you connect Qwen Code to LinkedIn?

1. Create an account at finchreach.com/sign-up, connect your LinkedIn account under Accounts, and create an API key under API keys.
2. Export your key, for example export FINCH_KEY=lk_your_key.
3. Run the command below. It writes to your user settings in ~/.qwen/settings.json; add -s project to store it in the project instead.
4. Restart Qwen Code and run /mcp to see the Finchreach tools.
5. More detail is in the Qwen guide and the docs.

qwen mcp add --transport http finchreach https://mcp.finchreach.com/mcp \
  --header "Authorization: Bearer $FINCH_KEY"

{
  "mcpServers": {
    "finchreach": {
      "httpUrl": "https://mcp.finchreach.com/mcp",
      "headers": { "Authorization": "Bearer lk_your_key" }
    }
  }
}

Use httpUrl, not url, in the settings file: in Qwen Code url means the older SSE transport. If you store the config in a project, keep the key out of version control.

What makes a release post people read?

• One headline change. Readers remember one thing; make it the one that saves them time or money.
• User language. Describe what changed for them, not what changed in the code.
• Credit. Naming contributors is good manners and gives the post reach in their networks.
• A link. The release page or docs, so interested readers can go deeper.
• A steady rhythm. Post for meaningful releases, not every patch.

You can keep a short RELEASE_POST.md in the repo with your tone rules and a past post you liked, and tell Qwen Code to follow it each time.

Should the post come from you or from the project?

Finchreach posts from your personal account, which is often an advantage for release posts: people follow people, and a maintainer explaining why a change matters reads more naturally than a brand announcement. If several maintainers want to post, each one connects their own LinkedIn account and API key, and each approves their own posts.

Ask your assistant“Write a version of the release post from my point of view as maintainer: what was hard about this release and what I learned. Keep the same facts and link.”

Can Qwen Code add screenshots or post as my company?

No. Finchreach posts text as you, from your personal account. It doesn’t attach images or video, post as a company page, schedule posts, or show analytics. If a release needs a screenshot or the company page, post that one yourself on LinkedIn and let Qwen Code draft the text.

Is posting from a CLI agent risky?

Automating a personal LinkedIn account carries risk under LinkedIn’s User Agreement. The approval queue and a human pace lower that risk, but don’t remove it.

There is a coding-agent-specific risk too: an agent that reads files can be influenced by what is in them. A malicious string in a dependency’s changelog could try to steer it. That is one reason Finchreach never publishes without your approval, so read the post before you click approve.

Frequently asked questions

Can I run this in CI after a tag is pushed? If your CI can run Qwen Code with your key, yes, and the post still waits for your approval. Treat CI as the drafting step and approve by hand.

Can Qwen Code reply to comments on the release post? It can read notifications and add comments on a post, each approved first.

Does the same setup work in other CLIs? Yes; see Claude Code or the Qwen integration page.

Where do I start? Sign up and follow the quickstart.