A Model Context Protocol (MCP) Server for Substack.
This MCP Server enables LLM clients to interact with Substack's API for automations like creating posts, managing drafts, and more. It supports various installation methods, including NPX and Docker. Users need to provide Substack tokens and other credentials to configure the server properly.
Follow the installation instructions for NPX or Docker as outlined in the documentation.
Chain API calls across services in natural language
Example
Fetch GitHub issues, create Jira tickets, post summary to Slack—all in one conversation
Automate cross-platform workflows without writing integration code
Keep data in sync across multiple platforms
Example
Sync CRM contacts to email marketing tool, update inventory across e-commerce platforms
Eliminate manual data entry and sync errors
Learn and test APIs conversationally
Example
Explore Stripe API endpoints, test with sample data, debug authentication
Reduce API integration development time by 50%
Share your MCP server with the developer community
Substack MCP Server has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Substack MCP Server is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Substack MCP Server is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Substack MCP Server is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
We wired Substack MCP Server into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
We wired Substack MCP Server into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Substack MCP Server is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
According to our notes, Substack MCP Server benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
We wired Substack MCP Server into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
We wired Substack MCP Server into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
showing 1-10 of 64
Substack MCP Server A Model Context Protocol (MCP) Server for Substack enabling LLM clients to interact with Substack's API for automations like creating posts, managing drafts, and more.
Docker Pulls npm downloads
🛠 Available Tools create_draft_post - Create a draft post 📋 Requirements Substack tokens, follow my guide to obtain them: Session token Publication URL User ID An LLM client that supports Model Context Protocol (MCP), such as Claude Desktop, Cursors, or GitHub Copilot Docker 🔌 Installation Introduction The installation process is standardized across all MCP clients. It involves manually adding a configuration object to your client's MCP configuration JSON file.
If you're unsure how to configure an MCP with your client, please refer to your MCP client's official documentation.
🧩 Engines Option 1: Using NPX This option requires Node.js to be installed on your system.
Add the following to your MCP configuration file: { "mcpServers": { "substack-api": { "command": "npx", "args": ["-y", "substack-mcp@latest"], "env": { "SUBSTACK_PUBLICATION_URL": "<YOUR_PUBLICATION_URL>", "SUBSTACK_SESSION_TOKEN": "<YOUR_SESSION_TOKEN>", "SUBSTACK_USER_ID": "<YOUR_USER_ID>" } } } } Replace <SUBSTACK_PUBLICATION_URL>, <YOUR_SESSION_TOKEN> and <YOUR_USER_ID> with your credentials. Option 2: Using Docker This option requires Docker to be installed on your system.
Add the following to your MCP configuration file: { "mcpServers": { "substack-api": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "SUBSTACK_PUBLICATION_URL", "-e", "SUBSTACK_SESSION_TOKEN", "-e", "SUBSTACK_USER_ID", "marcomoauro/substack-mcp:latest" ], "env": { "SUBSTACK_PUBLICATION_URL": "<YOUR_PUBLICATION_URL>", "SUBSTACK_SESSION_TOKEN": "<YOUR_SESSION_TOKEN>", "SUBSTACK_USER_ID": "<YOUR_USER_ID>" } } } } Replace <SUBSTACK_PUBLICATION_URL>, <YOUR_SESSION_TOKEN> and <YOUR_USER_ID> with your credentials. 💻 Popular Clients that supports MCPs For a complete list of MCP clients and their feature support, visit the official MCP clients page.
Client Description Claude Desktop Desktop application for Claude AI Cursor AI-first code editor Cline for VS Code VS Code extension for AI assistance GitHub Copilot MCP VS Code extension for GitHub Copilot MCP integration Windsurf AI-powered code editor and development environment 🆘 Support For issues with this MCP Server: Open an issue on GitHub
Monitor API endpoints and trigger actions
Example
Check website uptime, monitor API rate limits, alert on service errors
Catch issues before customers do
Prerequisites
Time Estimate
20-45 minutes per API integration
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
MCP server wraps external APIs, handles authentication, rate limiting, and error handling, exposing clean interface to Claude.
Protocols
Compatibility
✓ Use when
Use for multi-service workflows, data synchronization, API testing, and when building no-code integrations. Best for connecting 2+ services conversationally.
✗ Avoid when
Avoid for high-frequency real-time integrations (use native webhooks), when API latency is critical, or for complex transaction logic requiring guaranteed consistency.
