Medium MCP API Server

What is Medium MCP API Server?

Medium MCP API Server is a Model Context Protocol (MCP) server that integrates with Medium’s API to enable seamless content publishing and user account management from external applications. It bridges AI assistants and the Medium publishing platform, handling authentication, draft management, scheduling, and media uploads.

How to use Medium MCP API Server?

Install it via Docker Compose or manually. Create a .env file with your Medium API credentials, JWT secret, and MongoDB URI. Start the server, then use the provided REST endpoints to register, log in, connect a Medium account, create drafts, publish posts, upload images, and schedule publications. For example, send a POST /api/posts with a title and markdown content, then publish with POST /api/posts/:postId/publish.

Key features of Medium MCP API Server

• Secure Medium OAuth integration with JWT-based authentication
• Markdown and HTML content format support
• Draft creation, management, and scheduled publishing
• Publication, tag, and category support
• Image upload and content formatting utilities
• Redis caching, job scheduling, error handling, and rate limiting

Use cases of Medium MCP API Server

• Publish Medium articles directly from an AI assistant or chatbot
• Manage drafts and schedule posts for future publication
• Upload and format images for Medium content
• Build custom publishing workflows that integrate Medium with other tools

FAQ from Medium MCP API Server

What dependencies does the server require?

The server needs Node.js 16+, MongoDB, and optionally Redis (for scheduled publishing). Medium API credentials and a JWT secret are also required.

How does authentication work?

Users register or log in via email, receiving a JWT token. A separate OAuth flow connects the user’s Medium account using a client ID and secret.

Where is my data stored?

Published content is sent to Medium and stored there. Drafts, user profiles, and unpublished data are stored in your own MongoDB database.

Are there any rate limits or transport restrictions?

The server implements rate limiting. All communication is over HTTP using JWT tokens in the Authorization header.

Can I schedule posts to publish later?

Yes, include a scheduledAt ISO timestamp when creating or updating a post. The server will automatically publish at that time if Redis is configured.