Substack MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUBSTACK_API_KEY | Yes | Your Substack API key (connect.sid cookie value from substack.com) | |
| SUBSTACK_HOSTNAME | Yes | Your Substack hostname (e.g., yourname.substack.com) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_own_profileB | Get your own Substack profile information |
| get_profile_postsC | Get your recent Substack posts |
| create_noteC | Create a new Substack note (short-form post) |
| create_note_with_linkC | Create a new Substack note with a link attachment |
| get_postB | Get a specific Substack post by ID with full content |
| get_post_commentsB | Get comments for a specific Substack post |
| get_notesC | Get your recent Substack notes (short-form posts) |
| create_postC | Create and publish a full Substack blog post with optional cover image |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools are clearly distinct, focusing on specific resources like notes, posts, profiles, and comments. However, there is some potential overlap between 'create_note' and 'create_note_with_link', as the latter could be seen as a variant of the former, which might cause minor confusion in selection.
All tool names follow a consistent verb_noun pattern using snake_case, such as 'create_note', 'get_notes', and 'get_post_comments'. This predictability makes it easy for agents to understand and use the tool set without naming confusion.
With 8 tools, the server is well-scoped for managing Substack content, covering creation and retrieval of notes, posts, profiles, and comments. This count is appropriate, providing essential operations without being overwhelming or too sparse for the domain.
The tool set offers good coverage for core Substack operations, including CRUD-like actions for notes and posts, and retrieval of profiles and comments. A minor gap is the lack of update or delete tools for posts and notes, which agents might need to work around, but the surface supports key workflows effectively.