Medium Reader MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEDIUM_SID | No | Session cookie value. Override the saved session, for containers or CI. | |
| MEDIUM_UID | No | Session cookie value. Override the saved session, for containers or CI. | |
| MEDIUM_COOKIE | No | A full `Cookie:` header to take `sid` and `uid` from. | |
| MEDIUM_READER_HOME | No | Config directory (default `~/.config/medium-reader`). | ~/.config/medium-reader |
| MEDIUM_BROWSER_PATH | No | A Chromium-based browser for `login`, if Chrome and Edge aren't installed. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| auth_statusA | Check whether a Medium session is configured and still valid, which account it belongs to, and whether it has a Medium membership (needed for member-only posts). |
| get_feedA | The user's home feed. "following" (default) is posts from the authors and publications they follow; "for_you" is Medium's recommendations. Pass nextCursor back as |
| read_postA | Read a Medium post as Markdown. Member-only posts are returned in full when the logged-in account is a Medium member. Works for posts on custom domains too. Long posts are paged: pass |
| get_recent_postsA | Latest posts from one author or publication. Pass nextCursor back as |
| search_postsA | Search all of Medium for posts by keyword. Pass nextCursor back as |
| list_followingA | Authors (default) or publications the logged-in user follows, with the total count. |
| list_reading_listsA | The user's reading list (saved posts) and their named lists, with item counts. |
| get_listA | Posts saved in the reading list or one of the user's named lists, most recently added first. |
| followA | Follow an author or publication. Does nothing if already following. Only use when the user explicitly asks. If the name is ambiguous the candidates are returned; ask the user which one they mean. |
| unfollowA | Unfollow an author or publication. Only use when the user explicitly asks. If the name is ambiguous the candidates are returned; ask the user which one they mean. |
| save_to_listA | Save a post to the reading list (default) or one of the user's named lists. Does nothing if it's already there. Only use when the user asks. |
| remove_from_listA | Remove a post from the reading list (default) or one of the user's named lists. Only use when the user asks. |
| clapA | Clap for a post (visible to its author). Medium allows 50 claps per reader per post in total; this refuses to go past that. Only use when the user asks. undo_clap takes them back. |
| undo_clapB | Remove all of the user's claps from a post. Only use when the user asks. |
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 14 tools
Most tools target distinct actions and resources, but get_list and list_reading_lists overlap somewhat since both involve reading lists, and get_feed vs get_recent_posts could be confused by name alone. Descriptions generally resolve the boundaries.
Most names follow a clear verb_noun pattern like get_feed, search_posts, save_to_list, and remove_from_list. Minor deviations exist with auth_status lacking a verb and read_post/clap/undo_clap using different verb styles, but the pattern is still predictable.
14 tools is well-scoped for a Medium reader/engagement server, covering reading, searching, following, list management, and clapping without unnecessary redundancy. Each tool earns its place.
The surface covers core reading workflows: feeds, posts, search, author/publication posts, following, reading lists, and clapping. Minor gaps exist such as no named-list creation/deletion and no direct user/publication profile lookup, but these are not critical for the stated reader-oriented purpose.