postward-media-mcp
Officialby postward-cc
README.md
# postward-media-mcp
Standalone **media registry MCP** over any S3-compatible bucket (Wasabi, AWS S3,
Cloudflare R2, MinIO…). Give your AI agent upload, download, tagging and
collections — **with or without [PostWard](https://postward.cc)**.
> The agent thinks. PostWard orchestrates and publishes. Media lives where you want it.
## Direct mode (no PostWard account)
```jsonc
// MCP client config
{
"mcpServers": {
"media": {
"command": "npx",
"args": ["-y", "postward-media-mcp"],
"env": {
"MEDIA_MCP_MODE": "direct",
"S3_ENDPOINT": "https://s3.us-east-1.wasabisys.com",
"S3_BUCKET": "my-bucket",
"S3_REGION": "us-east-1",
"S3_ACCESS_KEY": "...",
"S3_SECRET_KEY": "..."
}
}
}
}
```
Metadata (names, tags, collections) lives portably in the bucket under
`.media-mcp/index.json`. Large bodies never cross the MCP payload: tools
return **presigned PUT/GET URLs** with short expiry.
## Gateway mode (PostWard)
The same `media.*` tool surface is also available through the
[PostWard MCP](https://postward.cc/docs/postward-mcp) when connected — assets
gain campaign linking, approval state and publication history.
## Tools
`media_capabilities` · `media_list` · `media_search` · `media_create_upload` ·
`media_create_download_url` · `media_delete` · `media_tag` · `media_untag` ·
`media_create_collection` · `media_add_to_collection` · `media_remove_from_collection`
## License
MIT
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues