Wire linkedin-mcp-scheduler to ~/.mcp.json for Penny social posting #203

New issue

Open

opened 2026-03-28 06:03:50 +00:00 by forgejo_admin · 0 comments

forgejo_admin commented

2026-03-28 06:03:50 +00:00

Contributor

Type

Task

Lineage

Follow-up from spike #133 (Penny MCP inventory). Labels: story:superuser-manage, arch:mcp-tools.

Scope

Wire the existing linkedin-mcp-scheduler server into ~/.mcp.json so Penny can schedule LinkedIn posts. The repo (forgejo_admin/linkedin-mcp-scheduler) and credentials (~/secrets/linkedin/credentials.env) already exist -- only the plumbing is missing.

Steps:

Add linkedin-mcp-scheduler entry to ~/.mcp.json with env vars LINKEDIN_ACCESS_TOKEN and LINKEDIN_PERSON_ID from ~/secrets/linkedin/credentials.env
Restart Claude Code session and verify mcp__linkedin__* tools appear
Update agents/penny.md: add linkedin to mcpServers frontmatter, add tools to table, remove from "Not Yet Wired" section

The server reads credentials from OS keychain first, falling back to env vars. Env var approach is simpler for local dev.

Acceptance Criteria

~/.mcp.json has linkedin entry with env vars
mcp__linkedin__* tools visible in Claude Code session
agents/penny.md updated to reflect linkedin as deployed

Spike: forgejo_admin/claude-custom#133
Repo: forgejo_admin/linkedin-mcp-scheduler
SDK: forgejo_admin/linkedin-sdk
Credentials: ~/secrets/linkedin/credentials.env

### Type Task ### Lineage Follow-up from spike #133 (Penny MCP inventory). Labels: `story:superuser-manage`, `arch:mcp-tools`. ### Scope Wire the existing linkedin-mcp-scheduler server into `~/.mcp.json` so Penny can schedule LinkedIn posts. The repo (`forgejo_admin/linkedin-mcp-scheduler`) and credentials (`~/secrets/linkedin/credentials.env`) already exist -- only the plumbing is missing. Steps: 1. Add linkedin-mcp-scheduler entry to `~/.mcp.json` with env vars `LINKEDIN_ACCESS_TOKEN` and `LINKEDIN_PERSON_ID` from `~/secrets/linkedin/credentials.env` 2. Restart Claude Code session and verify `mcp__linkedin__*` tools appear 3. Update `agents/penny.md`: add `linkedin` to mcpServers frontmatter, add tools to table, remove from "Not Yet Wired" section The server reads credentials from OS keychain first, falling back to env vars. Env var approach is simpler for local dev. ### Acceptance Criteria - [ ] `~/.mcp.json` has linkedin entry with env vars - [ ] `mcp__linkedin__*` tools visible in Claude Code session - [ ] `agents/penny.md` updated to reflect linkedin as deployed ### Related - Spike: forgejo_admin/claude-custom#133 - Repo: `forgejo_admin/linkedin-mcp-scheduler` - SDK: `forgejo_admin/linkedin-sdk` - Credentials: `~/secrets/linkedin/credentials.env`