---

name: substack-mcp-connector description: "MCP connector for Substack – enables AI-powered newsletter authoring, subscriber management, and content planning through Claude" license: Proprietary/API tags: ["writing","newsletter","mcp","substack","publishing"] difficulty: intermediate time_to_master: "4-8 weeks" version: "1.0.0"

Substack MCP Connector

Overview

This skill enables Claude to interact with Substack through the Model Context Protocol (MCP). It provides a bridge between Claude's AI capabilities and Substack's Web API, allowing natural language control of Substack operations, intelligent automation, and AI-powered assistance for Substack workflows.

When to Use This Skill

• Newsletter draft creation and editing
• Subscriber analytics and segmentation
• Content calendar planning
• Cross-promotion and recommendation management
• Revenue and subscription reporting

Architecture

┌─────────────┐     ┌─────────────────┐     ┌──────────────────┐
│   Claude     │────▶│   MCP Server    │────▶│   Substack         │
│   (Client)   │◀────│   (TypeScript)  │◀────│   (Web API       )│
└─────────────┘     └─────────────────┘     └──────────────────┘

Core Concepts

MCP Server Setup

The connector implements an MCP server that exposes Substack operations as tools Claude can invoke. The server translates natural language intentions into Web API calls.

Key Endpoints/Interfaces

publish API, subscriber management, analytics, draft management, settings

Implementation

// Substack MCP Server Implementation
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
import { z } from "zod";

const server = new McpServer({
  name: "substack-mcp-connector",
  version: "1.0.0",
});

// Tool: List/Query Resources
server.tool(
  "list_resources",
  "List and query Substack resources with optional filters",
  {
    query: z.string().optional().describe("Search query or filter"),
    limit: z.number().optional().describe("Max results to return"),
  },
  async ({ query, limit }) => {
    // Call Substack Web API
    const response = await fetch(`${BASE_URL}publish API`, {
      headers: { "Authorization": `Bearer ${API_KEY}` },
    });
    const data = await response.json();
    return {
      content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
    };
  }
);

// Tool: Create Resource
server.tool(
  "create_resource",
  "Create a new resource in Substack",
  {
    name: z.string().describe("Resource name"),
    config: z.object({}).passthrough().optional().describe("Resource configuration"),
  },
  async ({ name, config }) => {
    const response = await fetch(`${BASE_URL}publish API`, {
      method: "POST",
      headers: {
        "Authorization": `Bearer ${API_KEY}`,
        "Content-Type": "application/json",
      },
      body: JSON.stringify({ name, ...config }),
    });
    const data = await response.json();
    return {
      content: [{ type: "text", text: `Created: ${JSON.stringify(data)}` }],
    };
  }
);

// Tool: Analyze/Report
server.tool(
  "analyze",
  "AI-powered analysis of Substack data",
  {
    type: z.string().describe("Analysis type"),
    timeframe: z.string().optional().describe("Time range for analysis"),
  },
  async ({ type, timeframe }) => {
    // Fetch data and provide AI analysis
    const response = await fetch(`${BASE_URL}publish API`, {
      headers: { "Authorization": `Bearer ${API_KEY}` },
    });
    const data = await response.json();
    return {
      content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
    };
  }
);

// Start server
const transport = new StdioServerTransport();
await server.connect(transport);

Claude Desktop Configuration

{
  "mcpServers": {
    "substack-mcp-connector": {
      "command": "node",
      "args": ["path/to/substack-mcp-connector/index.js"],
      "env": {
        "SUBSTACK_API_KEY": "your-api-key",
        "SUBSTACK_BASE_URL": "https://your-instance-url"
      }
    }
  }
}

Best Practices

1. Authentication: Store API keys securely using environment variables; never hardcode credentials
2. Rate Limiting: Implement request throttling to respect Substack API rate limits
3. Error Handling: Provide clear, actionable error messages for common failure scenarios
4. Pagination: Handle paginated responses for large datasets efficiently
5. Caching: Cache frequently accessed read-only data to reduce API calls
6. Security: Validate all inputs before passing to the Substack API; sanitize outputs
7. Logging: Log all API interactions for debugging and audit purposes

Example Prompts

"Draft a newsletter post on the latest industry trends with key takeaways and discussion prompts"

Security Considerations

• All API credentials must be stored as environment variables
• Implement input validation and sanitization for all tool parameters
• Use HTTPS for all API communications
• Follow the principle of least privilege for API token permissions
• Audit log all write operations for compliance tracking

Resources

• Substack Official Documentation
• MCP SDK Documentation: https://modelcontextprotocol.io
• MCP Server Examples: https://github.com/modelcontextprotocol/servers
• SkillGalaxy Repository: https://github.com/Sandeeprdy1729/skill_galaxy

Changelog

Version	Date	Changes
1.0.0	2026-04-01	Initial MCP connector skill

---

Part of SkillGalaxy - 10,000+ comprehensive skills for AI-assisted development.