About this integration
Twitter/X tools for AI agents — read timelines, post tweets, search, and engage
- Transport
- stdio
- Authentication
- oauth
- Initial setup
- user-authorization
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.1.1
- Package
- shippost-mcp
- Last compatibility test
- Not independently tested
Connect your agent
shippost-mcpPublisher documentation requires a Twitter OAuth 2.0 access token, recommends a refresh token, and documents an optional ShipPost API key for paid AI tools. The tool set can publish and modify social activity. Documentation was reviewed; the package, Twitter/X API, and paid ShipPost API were not executed or independently security-audited.
Capabilities: Read Twitter/X profiles, timelines, mentions, tweets, and search results, Post, reply, like, retweet, and follow, Use optional ShipPost AI drafting and analytics tools
Connected profiles
Additional details
io.github.RyanKramer/shippost-mcp
Source ↗ · Checked 2026-09-170.1.1
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17pypi
Source ↗ · Checked 2026-09-17TWITTER_ACCESS_TOKEN
Source ↗ · Checked 2026-09-17shippost-mcp
Source ↗ · Checked 2026-09-190.1.1
Source ↗ · Checked 2026-09-19The MCP client launches shippost-mcp as a local command with authorization values supplied through its environment. This is documented behavior, not a runtime test.
Source ↗ · Checked 2026-09-19TWITTER_ACCESS_TOKEN is a required OAuth 2.0 access token; TWITTER_REFRESH_TOKEN and TWITTER_CLIENT_ID support renewal, while SHIPPOST_API_KEY is optional for paid AI features.
Source ↗ · Checked 2026-09-19Configure shippost-mcp as the local MCP command and pass the Twitter OAuth values in the command environment; no remote MCP endpoint is documented.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19