Vinkius
Substack logo
Vinkius
Vinkius runs on CrewAI

How to Use the Substack MCP in CrewAI

Orchestrate complex Substack strategies using crewai's team agents.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Substack MCP on Cursor AI Code Editor MCP Client Substack MCP on Claude Desktop App MCP Integration Substack MCP on OpenAI Agents SDK MCP Compatible Substack MCP on Visual Studio Code MCP Extension Client Substack MCP on GitHub Copilot AI Agent MCP Integration Substack MCP on Google Gemini AI MCP Integration Substack MCP on Lovable AI Development MCP Client Substack MCP on Mistral AI Agents MCP Compatible Substack MCP on Amazon AWS Bedrock MCP Support
MCP Servers — Included with Plan
Vinkius runs on CrewAI

Connect Substack MCP to CrewAI

Create your Vinkius account to connect Substack to CrewAI — we handle the hosting, security, and runtime updates so you don't have to. No server setup required.

GDPR Included with Plan

Key Capabilities

Coordinated Content Analysis

You can assign roles: a 'Researcher Agent' calls `list_posts` to gather titles, and an 'Analyst Agent' then uses those IDs to call `get_post_stats`. This collaboration allows the team to build a full report on content performance without manual stitching. The shared memory keeps all the data flowing between them.

Complex Substack Metadata Gathering

Need a deep dive? One agent calls `get_publication_info` to establish context, while another uses that info to call `get_leaderboard`. This multi-step, role-based execution ensures all necessary data points are gathered sequentially and reliably.

Full Subscriber Team Reporting

The team can handle subscriber management by having one agent run `list_subscribers` to get the raw list. A second specialized agent then processes that list, maybe counting specific segments or checking for patterns in the data.

Setup guide

Set up Substack MCP in CrewAI

Prerequisites

  • Python 3.10+ installed
  • crewai package (pip install crewai)
  • Active Vinkius subscription with a valid endpoint token
  1. 1

    Install CrewAI

    Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.

  2. 2

    Add the MCP URL to your agent

    Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.

  3. 3

    Kick off your crew

    Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Substack tools as needed.

crew.py
from crewai import Agent, Task, Crew

agent = Agent(
    role="Substack Analyst",
    goal="Access and analyze Substack data via MCP.",
    backstory="Expert analyst with direct Substack access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Substack transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Substack MCP in CrewAI

Define roles. Make one agent responsible for getting raw data (like `list_posts`), and a second agent responsible for analyzing that output, like checking stats using `get_post_stats`.
Yes. You can build an entire operational pipeline: Researcher Agent pulls posts; Analyst Agent checks their stats and writes a summary report, all without human intervention.
The framework's shared memory is the key. When one agent gets data—say from `get_publication_info`—it makes that context available for every other agent to use.
It handles subscriber metadata when calling the list tools. You get identifiers, not private correspondence. The MCP Server keeps access restricted to these defined operations.
Definitely. You can simulate a full marketing campaign: Agent 1 gets post data; Agent 2 reviews the leaderboard; Agent 3 compiles the findings into actionable insights.

Start using the Substack MCP today

We host it, we monitor it, we maintain it. You just paste one token.

Built & Managed by Vinkius 30s setup 6 tools

We've already built the connector for Substack. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 6 tools are live and waiting. You're up and running in seconds.

Vinkius runs on Claude Claude
Vinkius runs on ChatGPT ChatGPT
Vinkius runs on Cursor Cursor
Vinkius runs on Gemini Gemini
Vinkius runs on Windsurf Windsurf
Vinkius runs on VS Code VS Code
Vinkius runs on JetBrains JetBrains
Vinkius runs on Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.