linkedin-content-engine
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@linkedin-content-engineDraft a LinkedIn post announcing our Q3 results"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
LinkedIn Content Engine
A Claude Code plugin + local MCP server scaffold for producing branded LinkedIn posts and carousel documents, storing creative assets in Cloudinary, generating visuals with OpenAI GPT Image 2, and saving/queueing posts through Buffer.
This repository is intentionally structured as a Claude handoff repo: the architecture, interfaces, safety rules, schemas, prompts, and implementation tasks are defined so Claude Code can finish the production implementation without having to infer the system from a video.
Target workflow
User brief / content idea
|
v
Claude skill: linkedin-auto-poster
- selects post type
- writes LinkedIn copy
- creates visual/carousel brief
- requests approval before side effects
|
v
Local MCP server
|-- OpenAI adapter ------> GPT Image 2 ------> generated PNG slides
|-- PDF service ---------> carousel PDF
|-- Cloudinary adapter --> hosted PNG/PDF/thumbnail URLs
`-- Buffer adapter ------> draft / queue / scheduled LinkedIn postRelated MCP server: linkedin-mcp
Design decisions
Claude owns the writing. The skill contains the writing workflow and brand/style references. The MCP server performs deterministic integration work and side effects.
GPT Image 2 is used for visual generation, not for post copy.
Cloudinary is the creative asset store for generated slides, PDFs, thumbnails, and other media.
Buffer is the publishing queue/system of record for multiple prepared posts.
Human approval is mandatory before queueing or scheduling. Generating drafts and assets is allowed; publication is not implicit.
Adapters are replaceable. OpenAI, Cloudinary, and Buffer are isolated behind small interfaces.
Carousel output is a PDF document. Slide images are assembled into a PDF, hosted, then attached to Buffer as a document asset.
Repository layout
.
├── .claude-plugin/plugin.json
├── CLAUDE.md
├── ARCHITECTURE.md
├── IMPLEMENTATION_PLAN.md
├── .env.example
├── package.json
├── tsconfig.json
├── skills/
│ └── linkedin-auto-poster/
│ ├── SKILL.md
│ └── reference/
│ ├── workflow.md
│ ├── writing-guide.md
│ ├── creative-guide.md
│ └── api-contracts.md
├── src/
│ ├── config.ts
│ ├── types.ts
│ ├── adapters/
│ │ ├── openai-image.ts
│ │ ├── cloudinary.ts
│ │ └── buffer.ts
│ ├── services/
│ │ ├── carousel.ts
│ │ └── orchestrator.ts
│ └── mcp/
│ └── server.ts
├── samples/
│ ├── brand-profile.example.json
│ └── post-brief.example.json
├── tests/
│ └── README.md
└── docs/
└── CLAUDE_HANDOFF_PROMPT.mdQuick handoff to Claude Code
Put this folder in a new Git repository.
Open the repository in Claude Code.
Start with
docs/CLAUDE_HANDOFF_PROMPT.md.Ask Claude to work through
IMPLEMENTATION_PLAN.mdin order.Do not add real credentials until the validation/tests are in place.
Once implemented, test the plugin locally with Claude Code's plugin development mode and invoke the skill as:
/linkedin-content-engine:linkedin-auto-posterEnvironment variables
Copy .env.example to .env and add secrets locally. .env must remain gitignored.
Current external API assumptions
These assumptions were checked against current vendor documentation when the scaffold was created (August 2026):
OpenAI exposes
gpt-image-2for image generation/editing.Cloudinary's Node SDK supports server-side uploads and raw-file storage.
Buffer's API is GraphQL at
https://api.buffer.comand supports LinkedIn, drafts, queue/scheduling modes, images, and document assets.Claude Code project/plugin skills use
SKILL.md; plugin skills live underskills/<name>/SKILL.mdand are namespaced by the plugin name.
Before production use, Claude should re-check vendor schemas and SDK package versions rather than assuming this scaffold's examples are frozen forever.
Non-goals
Automating LinkedIn by browser scraping or private LinkedIn endpoints.
Publishing without explicit user approval.
Storing API secrets in repository files.
Hard-coding Full Marks Education branding into application code; branding belongs in a configurable profile.
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Flicense-qualityDmaintenanceMCP server for posting and managing LinkedIn content, supporting personal and company accounts. Deployed on Cloudflare Workers with token management via KV.
- Alicense-qualityCmaintenanceA personal-use remote MCP server that lets you post to LinkedIn, queue/schedule drafts, and pull your own post analytics from Claude.24MIT
- Alicense-qualityCmaintenanceAI-powered LinkedIn automation server for content generation, profile/company data extraction, and connection request automation, integrating with MCP clients like Claude Desktop.MIT
- Alicense-qualityBmaintenanceMCP server that lets AI agents operate a real LinkedIn account in plain English with safety controls and approval queues.24MIT
Related MCP Connectors
Managed LinkedIn MCP server for AI agents: search, connect, message and enrich on accounts you own.
MCP server for LeadDelta — manage LinkedIn connections and CRM data via AI assistants.
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mdbailin/linkedin-content-engine'
If you have feedback or need assistance with the MCP directory API, please join our Discord server