LinkedIn Publisher
Muse drafts — you approve — LinkedIn publishes
- What
- Muse drafts — you approve — LinkedIn publishes
- Cost
- Free
- Needs
- A LinkedIn account and a LinkedIn developer app (OAuth client ID/secret — free to create).
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Free and open source under Apache 2.0. LinkedIn Publisher is a stateless MCP connector that lets Muse publish explicitly approved text posts to your LinkedIn profile. It has no database, no scheduler, and only two tools. Drafting happens in Muse. Publishing stays behind an explicit approval step. For an approved Muse connector, the intended experience is simple: connect your LinkedIn account, authorize access, and publish. Developers who want to run or self host the open source version can follow the GitHub setup instructions, which include Python 3.12, a LinkedIn Developer app, OAuth configuration, and MCP setup. Independent open source project. Not affiliated with, sponsored by, or endorsed by LinkedIn or Meta.
Version:
Quick answer
LinkedIn Publisher is a free Muse skill that lets Muse publish explicitly approved text posts to your LinkedIn profile, following a simple rule: Muse drafts, you approve, LinkedIn publishes. It is a stateless MCP connector with no database, no scheduler and only two tools, so drafting happens in Muse and publishing stays behind an explicit approval step.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 79b9725Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: A LinkedIn account and a LinkedIn developer app (OAuth client ID/secret — free to create). No GitHub account needed unless listed here. Install "LinkedIn Publisher" for me. A Python connector that publishes posts to LinkedIn via OAuth. Repository: https://github.com/NeerajMohanty/LinkedIn-publisher Pinned version: install the code at commit 79b97252ca4acc36c2e790e27db0a0c5a366d3f4 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone the repo into a temporary folder (public HTTPS clone — no account needed) and look inside. 2. Safety check: briefly review any scripts for anything suspicious (network calls to unexpected hosts, shell commands, credential harvesting). If you see a red flag, stop and tell me before going further. 3. Set up everything you can: install dependencies and configure the non-secret parts. Then give me the exact remaining manual steps (usually: I create the account myself, deploy, and provide keys through my secure credential flow — never ask me to paste secrets into chat). 4. Verify without network calls: everything doable locally is done; clearly list what's left for me. 5. Report: what you installed, where, and anything still left for me to do myself (or confirm there's nothing left). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it (e.g. authenticated clone); otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 79b9725 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026 · Observed during the install test: files.pythonhosted.org, pypi.org
- Creator identity
- Not verified
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.