Featured Server Submission: POST_PILOT - LinkedIn Automation with Claude

[saksham-gagneja-indxx]

Server Overview

POST_PILOT is a production-ready MCP server that brings LinkedIn social media automation to Claude through conversation.

Registry Details

• Registry Name: io.github.saksham-gagneja-indxx/post-pilot
• npm Package: @sakshamgagneja/post-pilot-mcp
• GitHub Repository: https://github.com/saksham-gagneja-indxx/postpilot
• Version: 0.0.1
• Status: Production Ready ✅

Key Features

✅ Google Drive Integration — Upload videos directly from shared Google Drive links without downloading
✅ AI-Powered Composition — Multi-turn conversation with Claude for caption generation
✅ Schedule & Publish — Queue posts for specific times or publish immediately
✅ Server-Side Processing — No file size limits; videos processed on backend
✅ Two-Factor Security — GitHub OAuth + bearer token authentication
✅ Zero Setup — Works immediately after GitHub authorization

Use Case

Users can automate their LinkedIn posting entirely through Claude conversation:

"Upload my Q4 demo from Google Drive and schedule it for tomorrow at 9am with a product-focused caption"

Claude handles: link conversion → upload → caption generation → scheduling → confirmation

Documentation

Complete documentation available:

• Installation: https://github.com/saksham-gagneja-indxx/postpilot/blob/main/mcp-server/INSTALLATION.md
• System Design: https://github.com/saksham-gagneja-indxx/linkedin-posting-system-design
• README: https://github.com/saksham-gagneja-indxx/postpilot/blob/main/mcp-server/README.md
• Setup Guide: https://github.com/saksham-gagneja-indxx/postpilot/blob/main/mcp-server/SETUP.md

Technical Stack

• MCP Server: TypeScript on Cloudflare Workers (always-on, free tier)
• Backend: Python Flask on Render
• Database: Supabase PostgreSQL
• Storage: AWS S3
• Authentication: GitHub OAuth 2.0

Why Featured?

1. Solves Real Problem — LinkedIn automation is complex; POST_PILOT simplifies it via Claude conversation
2. Production Quality — Battle-tested, deployed, with comprehensive documentation
3. Seamless Integration — Google Drive connector requires no authentication; just public links
4. Active Development — Regularly maintained with new features coming (multi-account support, scheduling optimization)
5. Community Value — Demonstrates MCP's power for social media automation; replicable pattern for other platforms

Installation (For Users)

# Claude Desktop
Add to claude_desktop_config.json:
{
  "mcpServers": {
    "post-pilot": {
      "command": "npx",
      "args": ["@sakshamgagneja/post-pilot-mcp"]
    }
  }
}

# Or via CLI
npx @sakshamgagneja/post-pilot-mcp

Example Workflow

User: "List my reels"
Claude: [Shows all uploaded videos]

User: "Upload my Q4 presentation from Google Drive"
Claude: [Converts link, uploads, shows success]

User: "Draft a post about our new feature"
Claude: [Generates 3 caption options]

User: "Schedule for tomorrow at 9am"
Claude: [Queues post, confirms scheduling]

Availability

• ✅ Claude Desktop
• ✅ Claude Web (claude.ai)
• ✅ Claude Code
• ✅ Team Plans

POST_PILOT demonstrates MCP's potential for enterprise productivity automation and would be valuable to feature in the official registry.

[saksham-gagneja-indxx]

Following up since this was closed as "completed" with no comment — wanted to check what that meant, and to update the details since the project has moved on a bit since I filed this:

• The project has been rebranded to Aphelion (formerly Post Pilot)
• GitHub repo: https://github.com/saksham-gagneja-indxx/aphelion (renamed from postpilot)
• Registry entry: io.github.saksham-gagneja-indxx/aphelion (the old post-pilot entry has been marked deprecated, pointing here)
• All 11 MCP tools now carry proper tool annotations (readOnlyHint, destructiveHint, idempotentHint) for safety review
• Cloudflare Worker, OAuth flow, and connector are live and verified end-to-end

Two questions:

1. Did the "completed" close mean this was actioned toward featured/community status, or was it closed as out-of-scope for this repo? Happy to redirect this ask to the right place if this registry repo isn't where that's decided.
2. If there's a separate process for Claude's in-app connector directory (Community/Featured tags), could you point me to it?

Thanks for maintaining this!