substack-mcp
by navidmoazzez
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUBSTACK_USER_ID | No | Your numeric user id. Optional; resolved automatically when absent. | |
| SUBSTACK_MCP_HOME | No | Where session and queue live. | ~/.substack-mcp |
| SUBSTACK_MCP_HOST | No | HTTP bind address. | 127.0.0.1 |
| SUBSTACK_MCP_PORT | No | HTTP port. | 8788 |
| SUBSTACK_AUDIT_LOG | No | Append-only log of attempted writes, e.g. /path/to/audit.log | |
| SUBSTACK_MCP_TOKEN | No | Bearer token for HTTP. | |
| SUBSTACK_READ_ONLY | No | Disable every write. Set to '1' to expose only read tools. | 0 |
| SUBSTACK_USER_AGENT | No | Override the browser signature. | Chrome |
| SUBSTACK_MAX_RETRIES | No | Retries on 429 and 5xx. | 3 |
| SUBSTACK_PUBLICATIONS | No | JSON array for several publications, e.g. [{"publication_url":"one.substack.com","session_token":"..."},{"publication_url":"two.substack.com","session_token":"..."}] | |
| SUBSTACK_SESSION_TOKEN | No | The connect.sid cookie value | |
| SUBSTACK_PUBLICATION_URL | No | Your publication, e.g. example.substack.com | |
| SUBSTACK_ALLOW_DESTRUCTIVE | No | Allow publish and delete. Set to '0' to disallow destructive tools. | 1 |
| SUBSTACK_REQUEST_TIMEOUT_MS | No | Per-request deadline in milliseconds. | 30000 |
| SUBSTACK_MCP_ALLOWED_ORIGINS | No | Extra origins beyond localhost. | |
| SUBSTACK_MIN_REQUEST_INTERVAL_MS | No | Minimum spacing between requests in milliseconds. | 350 |
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 |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/navidmoazzez/substack-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server