MCP Server Medium
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEDIUM_API_KEY | No | Your Medium API integration token. If not provided, the server will look for it in ~/.medium/config.yaml. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_profileA | Get the authenticated user's Medium profile (id, username, name, url, imageUrl) |
| list_publicationsA | List all publications the authenticated user is related to (edits, writes, or follows) |
| list_contributorsA | List contributors for a given publication |
| create_postB | Create a post on the authenticated user's Medium profile |
| create_publication_postB | Create a post under a specific Medium publication |
| upload_imageC | Upload an image to Medium from a URL or file path |
| get_rss_feedA | Fetch and parse a Medium RSS feed into JSON. Supports profile (@username), publication (publication-name), topic feeds (tag/tag-name), or any full feed URL |
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
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/afikrim/medium-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server