Plus Tard MCP

Connect your AI assistant (Claude, Cursor, n8n…) to Plus Tard to schedule your Facebook, Instagram, LinkedIn, X/Twitter, TikTok, Threads, Bluesky, and Google My Business posts through simple conversation.

Production endpoint : https://mcp.plus-tard.com/mcp/ User documentation : https://plus-tard.com/api-mcp

30-second demo

You : "Schedule a Facebook post on my Boréales page for tomorrow at 10 AM: 'Hello world!'"

Claude automatically calls:

1. list_accounts → finds the Facebook ID for "Boréales"

2. schedule_post(provider="facebook", page_id="…", planned_at="2026-05-05T10:00:00Z", text="Hello world!")

Plus Tard : ✅ Post #1432 scheduled for 05/05/2026 at 10:00 AM.

Related MCP server: atlas-social-mcp

Tools (5)

Resources (2)

Client-side installation

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS):

{
  "mcpServers": {
    "plus-tard": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.plus-tard.com/mcp/",
        "--header",
        "X-Api-Key:${PLUS_TARD_TOKEN}"
      ],
      "env": {
        "PLUS_TARD_TOKEN": "your_plus_tard_api_key"
      }
    }
  }
}

Claude Code (CLI)

claude mcp add plus-tard \
  --transport http https://mcp.plus-tard.com/mcp/ \
  --header "X-Api-Key: your_plus_tard_api_key"

Claude.ai (web)

Settings → Connectors → Add custom connector — URL https://mcp.plus-tard.com/mcp/, header X-Api-Key: your_key.

Cursor / n8n

Same URL and header. See the full documentation.

Self-host (for developers)

Stack

• Python 3.12 · FastAPI · mcp[fastapi] (Streamable HTTP transport)

• httpx · pydantic v2 · pydantic-settings

• pytest · pytest-asyncio · respx

Architecture

Client (Claude/Cursor/n8n)
   │  Streamable HTTP + X-Api-Key header
   ▼
MCP server (this repo)
   │  X-Api-Key forwarded as-is
   ▼
Plus Tard Symfony API

Each MCP request arrives with X-Api-Key, which is propagated as-is to the Plus Tard API. No session, no server-side storage — each client uses its own key.

Local development

git clone https://github.com/<votre-org>/plus-tard-mcp.git
cd plus-tard-mcp

python3.12 -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"

cp .env.example .env
# Édite .env : PLUS_TARD_BASE_URL=https://plus-tard.com

uvicorn main:app --reload --port 8001

The server listens on http://127.0.0.1:8001/mcp/. Quick test with the MCP Inspector:

npx @modelcontextprotocol/inspector
# Transport: Streamable HTTP
# URL: http://127.0.0.1:8001/mcp/
# Header: X-Api-Key = ta_clef_plus_tard

Tests

pytest
# 24 passed

Docker deployment (production)

The repository provides Dockerfile + docker-compose.yml ready for a VPS with nginx-proxy + acme-companion:

sudo docker compose up -d --build

See deploy/README.md for details (SSE-friendly nginx-proxy snippet, Let's Encrypt TLS management, updates).

Configuration

Authentication is done per request via the X-Api-Key header — no tokens are stored server-side.

Allowed hosts

The MCP SDK enables anti-DNS rebinding protection that only allows whitelisted hosts. The default hosts are:

• mcp.plus-tard.com

• localhost, 127.0.0.1 (for dev)

To add your own domain, edit the list in main.py (TransportSecuritySettings.allowed_hosts).

Project structure

.
├── main.py                # FastAPI + FastMCP + middleware X-Api-Key
├── app/
│   ├── config.py          # Settings via pydantic-settings
│   ├── auth/              # Dependency X-Api-Key (réutilisable hors MCP)
│   ├── models/            # Schémas pydantic v2 (post, account, user)
│   ├── services/          # PlusTardClient async (httpx)
│   └── tools/             # 5 tools métier (str → str)
├── tests/                 # 24 tests pytest-asyncio
├── deploy/
│   ├── README.md          # Guide déploiement VPS
│   ├── vhost.d/           # Snippet nginx-proxy SSE
│   └── twig/              # Template Symfony pour la doc utilisateur
├── docs/index.html        # Doc utilisateur statique (HTML)
├── Dockerfile
├── docker-compose.yml
└── pyproject.toml

Security

• HTTPS only in production (TLS via Let's Encrypt).

• No logging of post content or API tokens.

• Anti-DNS rebinding via TransportSecuritySettings from the MCP SDK.

• Isolated multi-tenancy: each request is processed with its own httpx client, closed at the end of the request (no cross-user pooling).

• If you suspect a key has leaked, revoke it from your Plus Tard space.

Roadmap

• [ ] Structured logging (JSON, without tokens or content)

• [ ] Rate limiting per API key

• [ ] Prometheus metrics

• [ ] OAuth flow for connectors (instead of a copy-paste API key)

• [ ] Support for MCP completion/complete for page_id suggestions (waiting for a Python SDK that exposes ToolReference)

Ideas and contributions are welcome — open an issue or a PR.

Useful links

• User documentation

• Plus Tard API (v1.2)

• MCP Specification

• MCP Inspector

• mcp-remote (stdio↔HTTP bridge for Claude Desktop)

License

MIT © 2026 Plus Tard — Boréales Créations.

Made with ❤️ in France.