Last updated: 16 August 2026
Shanth Content Publisher is a personal command-line tool that publishes its author's own posts to that author's own LinkedIn profile. It runs locally on a single machine. It has one user, the author. It is not a service, it has no server, and it is not offered to anyone else.
Everything is stored in plain files on the local machine, under
~/.linkedin-mcp/:
| File | Contents |
|---|---|
linkedin_token.json |
The OAuth access token issued by LinkedIn, its expiry, and the author's own LinkedIn member id. Created with 0600 permissions — readable only by the operating-system account that created it. |
linkedin_mcp.db |
A SQLite database of post drafts: the draft text, its state, when it was created, and — once published — the post's URN and publication time. |
Nothing else is stored. No other LinkedIn member's data is stored, because none is ever requested.
The tool holds three OAuth scopes, all granted by the author for the author's own account:
openidandprofile— used once, to read the author's own member id, which LinkedIn's Posts API requires in order to attribute a post to its author.w_member_social— permits publishing posts as the author. This scope is write-only: it confers no ability to read anything from LinkedIn.
The tool therefore cannot read the author's feed, connections, messages, or any
other member's information, and it does not attempt to. It contacts only
LinkedIn's own documented endpoints (linkedin.com/oauth/v2/*,
api.linkedin.com/v2/userinfo, api.linkedin.com/rest/posts).
The only data transmitted to LinkedIn is the text of a post that the author has explicitly approved for publication, plus the OAuth token that authorises it.
No data is sent to any third party. There is no analytics, no telemetry, no error reporting, no advertising, and no cloud component of any kind.
If future versions fetch publicly available articles or repositories from sources the author configures, those requests are ordinary anonymous reads of public web pages: no personal data, credentials, or LinkedIn data are included in them.
Data is kept until the author deletes it. To remove everything the tool holds:
rm -rf ~/.linkedin-mcp/
The OAuth token can additionally be revoked at any time from LinkedIn's permitted-services settings, which invalidates it regardless of any local copy.
Shanth Kumar Bugudi — b.shanthkumar@gmail.com