
OAuth2 CLI and MCP server for the API.
Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
npx -y [email protected]Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
LINKEDCTL_ACCESS_TOKEN=<secret> LINKEDCTL_CLIENT_ID=<value> LINKEDCTL_CLIENT_SECRET=<secret> claude mcp add io.github.alexey-pelykh-linkedctl -- npx -y linkedctl@0.5.0รันในเทอร์มินัล
{ "mcpServers": { "io.github.alexey-pelykh-linkedctl": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "LINKEDCTL_ACCESS_TOKEN": "<secret>", "LINKEDCTL_CLIENT_ID": "<value>", "LINKEDCTL_CLIENT_SECRET": "<secret>" } } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดnpm install -g linkedctl
Or run directly:
npx linkedctl --help
linkedctl auth login --client-id YOUR_CLIENT_ID --client-secret YOUR_CLIENT_SECRET
linkedctl post "Hello from LinkedCtl!"
See the OAuth Setup Guide for detailed step-by-step instructions.
Add to your Claude Desktop configuration (claude_desktop_config.json):
{
"mcpServers": {
"linkedctl": {
"command": "npx",
"args": ["linkedctl", "mcp"]
}
}
}
claude mcp add linkedctl -- npx linkedctl mcp
Add to .cursor/mcp.json in your project root:
{
"mcpServers": {
"linkedctl": {
"command": "npx",
"args": ["linkedctl", "mcp"]
}
}
}
Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"linkedctl": {
"command": "npx",
"args": ["linkedctl", "mcp"]
}
}
}
All tools accept an optional profile parameter to select a configuration profile.
post_create supports rich content types:
LinkedCtl stores configuration in YAML files. Each file represents a single profile:
api-version: "202601"
oauth:
client-id: "YOUR_CLIENT_ID"
client-secret: "YOUR_CLIENT_SECRET"
access-token: "YOUR_ACCESS_TOKEN"
refresh-token: "YOUR_REFRESH_TOKEN"
token-expires-at: "2026-05-03T12:00:00.000Z"
Available keys:
Config files are written with 0600 permissions (owner read/write only).
Without a profile, LinkedCtl searches for config files in this order:
.linkedctl.yaml in the current working directory~/.linkedctl.yaml in the home directoryThe first file found is used. When writing (e.g. after auth login), LinkedCtl writes to the CWD file if it exists, otherwise to the home directory file.
Profiles let you manage multiple LinkedIn accounts or configurations. Each profile is stored as a separate YAML file under ~/.linkedctl/:
Use the --profile flag with any command:
linkedctl --profile work auth login --client-id ID --client-secret SECRET
linkedctl --profile work post "Hello from my work account!"
Manage profiles with the profile command:
linkedctl profile create work --access-token YOUR_TOKEN --api-version 202601
linkedctl profile list
linkedctl profile show work
linkedctl profile delete work
LinkedCtl supports OAuth 2.0 with your own LinkedIn Developer App:
linkedctl auth login --client-id YOUR_CLIENT_ID --client-secret YOUR_CLIENT_SECRET
If you already have an access token from another application:
linkedctl auth token --access-token YOUR_TOKEN
Environment variables take precedence over config file values.
When using a named profile, LinkedCtl also reads profile-prefixed environment variables. The profile name is uppercased with hyphens converted to underscores:
The same pattern applies to CLIENT_ID, CLIENT_SECRET, and API_VERSION.
Configuration values are resolved in this order (highest priority first):
auth — Manage Authenticationauth login options:
auth token options:
post — Manage LinkedIn Posts# Shorthand: pass text as an argument
linkedctl post "Hello from LinkedCtl!"
# Explicit subcommand
linkedctl post create --text "Hello from LinkedCtl!"
# Pipe content from stdin
echo "Hello from LinkedCtl!" | linkedctl post create
post create options:
post list options:
comment — Manage Commentscomment create options:
reaction — Manage Reactionsreaction create options:
org — Manage Organizationsmedia — Upload MediaAll media commands accept --as-org <id> and --format json|table.
stats — View AnalyticsCommon options:
profile — Manage Configuration Profilesprofile create options:
whoami — Show Current Userlinkedctl whoami
linkedctl whoami --format json
completion — Shell Completionslinkedctl completion bash
linkedctl completion zsh
--force is passedThis is an independent project and is not affiliated with, endorsed by, or associated with LinkedIn Corporation. LinkedIn is a trademark of LinkedIn Corporation.
Using LinkedCtl as a CLI tool or MCP server: No license obligations — use freely.
Using @linkedctl/core as a library in your project: Your combined work must be licensed under AGPL-3.0 (or a compatible license).
{ "mcpServers": { "io.github.alexey-pelykh-linkedctl": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "LINKEDCTL_ACCESS_TOKEN": "<secret>", "LINKEDCTL_CLIENT_ID": "<value>", "LINKEDCTL_CLIENT_SECRET": "<secret>" } } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ผู้เผยแพร่ระบุตัวแปรสภาพแวดล้อมเหล่านี้: LINKEDCTL_ACCESS_TOKEN, LINKEDCTL_CLIENT_ID, LINKEDCTL_CLIENT_SECRET
Linkedctl ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-09 CLI and MCP server for the LinkedIn API