Description
Summary We need a senior API/integration developer to finish a LinkedIn-only, read-first integration for Take The Limits Off. Objective Enable our ChatGPT environment to securely analyze the founder’s authorized personal LinkedIn posts and performance data using official LinkedIn APIs and a TTLO-controlled remote MCP service. Current state LinkedIn developer app already created: Coach Mel Content Intelligence Associated with the Take The Limits Off LinkedIn Company Page Company/app verification is not yet complete Community Management API access has not yet been requested Member OAuth, MCP server, and ChatGPT custom app are not yet configured Phase 1 scope Verify the current official LinkedIn API/product/permission path for accessing an authenticated member’s personal post analytics. Complete only the necessary LinkedIn verification and API-access steps. Configure LinkedIn OAuth for the founder’s personal member account. Build and deploy a small, secure READ-ONLY backend + remote MCP under TTLO control. Connect the MCP to ChatGPT as a custom app and demonstrate a bounded real-data read. Transfer all source code, deployment, secrets architecture, and maintenance documentation to TTLO. Important boundaries LinkedIn only. Facebook/Meta is out of scope. Official LinkedIn API/OAuth only. No scraping, browser bots, copied cookies, passwords, or session-token workarounds. Phase 1 is read-only: no posting, commenting, liking, messaging, or connection requests. TTLO must own the repository, infrastructure, credentials, deployment, and production assets. Please include in your proposal Your direct experience with LinkedIn Community Management/member analytics APIs. Which current LinkedIn endpoint(s) and permission(s) you expect to use for authenticated-member post analytics. One example of an MCP server or ChatGPT custom app you have built. Your proposed milestone plan and fixed-price estimate. Any LinkedIn access/approval risk you see before engineering begins. We prefer someone who will prove the official API access path first and tell us if a capability is unavailable rather than substitute scraping or risky automation.