What it is
The MCP server exposes Social Champ to AI assistants (Claude, Switch and others) as tools: list channels, create text and image posts, schedule and bulk-schedule, manage labels and queues, read calendar and metrics. Every tool resolves the caller's workspace and role on the server, so an assistant can never do more than the person it acts for.
The n8n community node (npm, source on GitHub) and the Make custom app wrap the public REST API with API-key and OAuth2 credentials, channel pickers and post creation, so marketers can automate publishing without code.
What I built
Role-scoped tool surface
Tool handlers for channels, posts, scheduling, labels, queues, calendar and metrics, with permissions derived from current workspace membership and empty channel options treated as absent.
Community node on npm
Resources for channels and posts, credential test, scheduling for a specific time, published as @socialchampio/n8n-nodes-socialchamp with a help guide and screenshots.
40-module custom app
Generated from the public API routes: OAuth2 connection, RPC-backed channel dropdowns, post creation with image and video URLs and dateTime. Learned the hard way that Make caches the app definition per session.
Public API and keys
API keys issued from the auth app's Developer settings, scoped per account; the same keys power n8n, Make and MCP.
Retries and idempotency
Tested double submits, retries after timeouts and scheduling edge cases so an automation that retries never publishes twice.
Flow docs with real screenshots
Walkthrough PDFs built from the running app for support and customers.
What changed
Assistants that ship
Claude and Switch can schedule and manage posts through the same guarded API.
No-code automation
n8n and Make users publish from their own workflows.
Least privilege
Every tool call is scoped to the caller's workspace and role.
Safe retries
Duplicate submits do not become duplicate posts.
Want the rest of the work?
Switch, analytics, sentiment, Brand Dashboard, MCP and n8n.