linkedin-content-engine
MCP server for managing LinkedIn content workflows. It generates images via OpenAI, stores assets in Cloudinary, and queues drafts through Buffer with mandatory human approval.
README
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 post
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.md
Quick 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-poster
Environment 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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.