---
title: "Discussion on \"A Substack MCP Should Show You More Than Just Drafts\" | Hashnode"
description: "Discussion on \"A Substack MCP Should Show You More Than Just Drafts\". Part 5 of 9\nI didn’t want this to be a write-only Substack MCP.\nIf I’m using a tool to publish, I also want it to help me understand what’s happening inside the publication.\nSo I added:\n\nget_post_analytics\nget_sections\nget_subscriber_count\n\nThat made..."
url: "https://hashnode.com/posts/a-substack-mcp-should-show-you-more-than-just-drafts/69c6da41cfdaf8a7fea4a1b4"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [A Substack MCP Should Show You More Than Just Drafts](https://abanoubashraf.hashnode.dev/a-substack-mcp-should-show-you-more-than-just-drafts?utm_source=hashnode&utm_medium=feed)

Part 5 of 9 I didn’t want this to be a write-only Substack MCP. If I’m using a tool to publish, I also want it to help me understand what’s happening inside the publication. So I added: get\_post\_analytics get\_sections get\_subscriber\_count That made...

Mar 27 · 1 min read · abanoubashraf.hashnode.dev  
Read the article

-   [#ai](https://hashnode.com/tag/ai)

## Written by

[Abanoub Ashraf](https://hashnode.com/@abanoubashraf)

@abanoubashraf · Cairo, Egypt

  
[View profile](https://hashnode.com/@abanoubashraf)

Software Engineer at Motorgy

Software Engineer at Motorgy & building on the side

## Responses 1

Markdown supported · ⌘↵ to post

[Aamer Mehaisi](https://hashnode.com/@mehaisi)

[Mar 27](https://hashnode.com/posts/a-substack-mcp-should-show-you-more-than-just-drafts/69c6da41cfdaf8a7fea4a1b4/comment/69c6faf5af2e2202e389f41e)

The read/write asymmetry in MCP servers is a real pattern. Most integrations start as write-only because thats minimum viable. But read capabilities are what make agents genuinely useful.

Three observations:

1.  **State surface area**: Write operations have clear boundaries. Read operations need to expose platform state at the right granularity. Substack has sections, subscriber counts, analytics - all state that informs writing decisions.
    
2.  **Caching semantics**: Read operations enable caching strategies. Write-only MCPs require optimistic actions. Read-capable MCPs let agents cache state and make informed decisions.
    
3.  **Permission boundaries**: Write operations are high-stakes. Read operations expose platform internals. The choice: expose everything for flexibility, or curate for safety.
    

The shift from what can I create to what do I know about the system is the difference between an automation tool and a genuine agent assistant.