{
  "markdown": "# Liftli — head of content, as an MCP server\n\n<p align=\"center\">\n  <img alt=\"LinkedIn\" src=\"https://cdn.worldvectorlogo.com/logos/linkedin-icon-2.svg\" width=\"32\">\n  &nbsp;&nbsp;\n  <img alt=\"X (Twitter)\" src=\"https://cdn.simpleicons.org/x/000000\" width=\"32\">\n  &nbsp;&nbsp;\n  <img alt=\"Substack\" src=\"https://cdn.simpleicons.org/substack/FF6719\" width=\"32\">\n</p>\n\n<p align=\"center\"><strong>LinkedIn &nbsp;·&nbsp; X (Twitter) &nbsp;·&nbsp; Substack</strong></p>\n\nLiftli is a remote [MCP](https://modelcontextprotocol.io) server that acts as a head of content\nfor **LinkedIn, X (Twitter) and Substack**, inside the AI assistant you already use.\n\nIt extracts your writing voice from your own posts, mines your real work — voice notes, meeting\ntranscripts, GitHub activity, chats, the news — for post ideas, builds and remembers your strategy,\ndrafts in your voice, critiques every draft like a ruthless editor, and schedules or publishes\nthrough the platforms' **official APIs**.\n\n**Nothing publishes without your explicit approval.** No scraping, no browser automation, no bots\nacting on your profile.\n\n- Homepage: <https://liftli.ai>\n- Developer docs: <https://liftli.ai/developers.html>\n- Free skills (no account needed): <https://github.com/liftli-ai/skills>\n\n> **About this repository.** Liftli is a hosted service; this repo is documentation and install\n> instructions for the remote MCP server. The server implementation is not open source. If you are\n> looking for something self-hostable, this is not it — but the connector is free to add and starts\n> with a free usage allowance, no card required.\n\n## Install\n\nThe server is remote — served over HTTPS, using MCP's Streamable HTTP transport. There is nothing\nto run locally.\n\n**Connector URL**\n\n```\nhttps://liftli-strategist-mcp.onrender.com/mcp\n```\n\n**Claude Code**\n\n```bash\nclaude mcp add --scope user --transport http liftli https://liftli-strategist-mcp.onrender.com/mcp\n```\n\n**Claude Desktop** — Customize (briefcase icon) → Connectors → **+ Add custom connector** → paste\nthe URL above into \"Remote MCP Server URL\".\n\n**Other clients** (ChatGPT, Cursor, Codex, Copilot, Gemini) — add it as a custom/remote MCP server\nusing the same URL. Client-specific notes are in [developers.html](https://liftli.ai/developers.html).\n\nIf your client cannot reach a remote server directly, `npx mcp-remote` works as a bridge.\n\n## Tools\n\n54 tools. Some clients expose a reduced set (ChatGPT 53, Cursor 40) to stay within their limits.\n\n**Start here / profile (7)** — `strategist_briefing`, `get_profile`, `save_profile`, `onboard`,\n`extract_voice`, `save_corpus_tags`, `liftli_status`\n\n**Strategy (6)** — `build_strategy`, `save_strategy`, `define_narrative`, `growth_strategy`,\n`plan_calendar`, `content_ideas`\n\n**Writing (7)** — `plan_post`, `generate_hooks`, `critique`, `ready_to_post`, `save_post`,\n`browse_posts`, `rewrite_profile`\n\n**Engagement (4)** — `plan_comment`, `engagement_plan`, `analyze_results`, `log_outcome`\n\n**Substack (9)** — `build_substack_strategy`, `save_substack_strategy`, `plan_newsletter`,\n`score_newsletter`, `newsletter_headlines`, `plan_note`, `notes_from_newsletter`,\n`repurpose_to_substack`, `substack_growth`\n\n**Publishing & scheduling (7)** — `connect_account`, `approve_post`, `publish_post`,\n`schedule_post`, `list_scheduled`, `edit_scheduled`, `send_post_to_telegram`\n\n**Media & visuals (3)** — `generate_visual`, `plan_visual`, `manage_media`\n\n**Memory & seeds (5)** — `remember`, `recall`, `manage_memory`, `extract_seeds`, `news_monitor`\n\n**Channels & account (6)** — `link_telegram`, `link_whatsapp`, `notify`, `contact_support`,\n`upgrade`, `dismiss_suggestion`\n\n## How it differs\n\nLiftli covers the **whole pipeline**: it decides what is worth saying from your real week, drafts\nit in your extracted voice, pressure-tests the draft, and then publishes or schedules it through\nthe platforms' official APIs. You do not need to add a separate scheduler.\n\nThe dividing line against other tools is **where it lives**, not what it does. Schedulers and\ndashboards are surfaces you open and sit inside. Liftli is not a surface — it runs inside the AI\nassistant you already use, so capturing an idea, writing it and shipping it happen in one place,\nincluding from a voice note sent over Telegram or WhatsApp while you are away from a desk.\n\n## Safety model\n\n- Publishing and scheduling run through **official platform APIs**, connected only when you\n  explicitly link an account.\n- Every draft waits for your approval before anything is posted.\n- No browser extension, no scraping, no automated actions on your profile — the category the\n  platforms' terms prohibit.\n\n## Support\n\nOpen an issue here, or use the `contact_support` tool from inside your assistant.\n\n## License\n\nDocumentation in this repository is MIT-licensed. The Liftli service itself is proprietary and\ngoverned by the [terms at liftli.ai](https://liftli.ai/legal.html).\n",
  "bytes": 4919,
  "sha": "99c5aea307b98a9c65c4207754b8b2dc55b51cbaf92b3c7fd27e55c9170bb5fd",
  "repo_slug": "liftli-ai/liftli-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_liftli_ai_liftli_f85a6314/readme"
}