		# Changelog

		## 0.7.3 (2026-08-15)

		### Added

		- `twitter_monitor_account_health` (task #111): account-wide monitoring rollup in ONE call, distinct from `twitter_monitor_health` (which needs an id and reports one monitor's cursor): service status ("operational" or "degraded"), active/paused/total counts across every monitor you own, and pending/delivered/failed delivery counts from the last 24 hours. Takes no arguments. A key with zero monitors gets zeroed counts back, never an error. Free per call. The catalog is now 75 tools: 46 reads and 29 write actions.

		## 0.7.2 (2026-08-14)
		@@ -4,0 +10,0 @@

+1

-1

package.json

		{
		"name": "@twitterapis/mcp",
		"version": "0.7.2",
		"version": "0.7.3",
		"description": "Official MCP server for twitterapis.com, the Twitter/X API (search, users, followers, tweets, threads, lists, likes, bookmarks, DMs) plus write actions (post/like/retweet/follow) as native tools for Claude, Cursor, and any MCP client.",
		@@ -5,0 +5,0 @@ "repository": {

+3

-2

README.md

		@@ -94,3 +94,3 @@ # @twitterapis/mcp

		74 tools: 45 reads and 29 write actions. Most user endpoints accept `username` (handle without @) or `user_id` (`twitter_user_likes` and `twitter_user_tweets_complete` require `user_id`); tweet endpoints accept `id` or `url`; paginated endpoints return a `cursor` you pass back to get the next page. Two of the reads are free account/billing lookups (`twitter_account_me`, `twitter_account_payments`); the 13 monitoring tools are also free (account administration, not metered reads).
		75 tools: 46 reads and 29 write actions. Most user endpoints accept `username` (handle without @) or `user_id` (`twitter_user_likes` and `twitter_user_tweets_complete` require `user_id`); tweet endpoints accept `id` or `url`; paginated endpoints return a `cursor` you pass back to get the next page. Two of the reads are free account/billing lookups (`twitter_account_me`, `twitter_account_payments`); the 14 monitoring tools are also free (account administration, not metered reads).

		@@ -181,2 +181,3 @@ Public reads (search, profiles, tweets, followers, likes) work with just your API key. The account-only reads (bookmarks, DMs, home timeline, followers-you-know) and most write actions act AS an authenticated X account, so they need a session linked to your key first (returns HTTP 409 until then). Link a session either by registering your x.com cookies (`twitter_customer_session`) or by logging in with a username/password (`twitter_user_login`). Alternatively, pass per-call inline credentials on any of those tools (`auth_token` + `ct0`, with optional `proxy_url` / `user_agent`) to act AS that account for a single call without pre-registering a session, so one API key can act as many accounts. For write actions, set `proxy_url` to a residential proxy, since X soft-blocks writes that egress from datacenter IPs. Each write tool is annotated `readOnlyHint: false`; reversing actions (delete, unfollow, unlike, unretweet, unbookmark, monitor/webhook delete) are annotated `destructiveHint: true` so MCP clients can prompt before running them. The monitoring tools (see below) are the one exception: they administer your twitterapis.com account, not an X session, so they need only your API key, no linked session and no inline credentials.
		\| `twitter_monitor_health` \| One monitor's status, degradation flag, poll interval, cursor position \|
		\| `twitter_monitor_account_health` \| Account-wide rollup: service status, active/paused monitor counts, 24h delivery outcome counts, one call \|
		\| `twitter_monitor_deliveries` \| Recent delivery events across every monitor, with detection + delivery latency \|
		@@ -281,3 +282,3 @@ \| `twitter_x_user_stream_add_user` \| Compat drop-in for `twitter_monitor_create` using an x_user_stream-shaped envelope \|

		Is it read-only? No. 45 read tools work with just your API key; 29 write actions (post, like, retweet, follow, DM, media upload, article create/edit/publish/delete, monitor/webhook create/update/delete) act as a linked X account or per-call inline credentials, except monitor/webhook CRUD, which is account administration and needs only your API key.
		Is it read-only? No. 46 read tools work with just your API key; 29 write actions (post, like, retweet, follow, DM, media upload, article create/edit/publish/delete, monitor/webhook create/update/delete) act as a linked X account or per-call inline credentials, except monitor/webhook CRUD, which is account administration and needs only your API key.

		@@ -284,0 +285,0 @@ Which clients are supported? Claude Desktop, Cursor, Windsurf, and VS Code (Copilot agent mode), or any Model Context Protocol client.

src/tools.js

Sorry, the diff of this file is too big to display

		@@ -94,3 +94,3 @@ # @twitterapis/mcp

		74 tools: 45 reads and 29 write actions. Most user endpoints accept `username` (handle without @) or `user_id` (`twitter_user_likes` and `twitter_user_tweets_complete` require `user_id`); tweet endpoints accept `id` or `url`; paginated endpoints return a `cursor` you pass back to get the next page. Two of the reads are free account/billing lookups (`twitter_account_me`, `twitter_account_payments`); the 13 monitoring tools are also free (account administration, not metered reads).
		75 tools: 46 reads and 29 write actions. Most user endpoints accept `username` (handle without @) or `user_id` (`twitter_user_likes` and `twitter_user_tweets_complete` require `user_id`); tweet endpoints accept `id` or `url`; paginated endpoints return a `cursor` you pass back to get the next page. Two of the reads are free account/billing lookups (`twitter_account_me`, `twitter_account_payments`); the 14 monitoring tools are also free (account administration, not metered reads).

		@@ -181,2 +181,3 @@ Public reads (search, profiles, tweets, followers, likes) work with just your API key. The account-only reads (bookmarks, DMs, home timeline, followers-you-know) and most write actions act AS an authenticated X account, so they need a session linked to your key first (returns HTTP 409 until then). Link a session either by registering your x.com cookies (`twitter_customer_session`) or by logging in with a username/password (`twitter_user_login`). Alternatively, pass per-call inline credentials on any of those tools (`auth_token` + `ct0`, with optional `proxy_url` / `user_agent`) to act AS that account for a single call without pre-registering a session, so one API key can act as many accounts. For write actions, set `proxy_url` to a residential proxy, since X soft-blocks writes that egress from datacenter IPs. Each write tool is annotated `readOnlyHint: false`; reversing actions (delete, unfollow, unlike, unretweet, unbookmark, monitor/webhook delete) are annotated `destructiveHint: true` so MCP clients can prompt before running them. The monitoring tools (see below) are the one exception: they administer your twitterapis.com account, not an X session, so they need only your API key, no linked session and no inline credentials.
		\| `twitter_monitor_health` \| One monitor's status, degradation flag, poll interval, cursor position \|
		\| `twitter_monitor_account_health` \| Account-wide rollup: service status, active/paused monitor counts, 24h delivery outcome counts, one call \|
		\| `twitter_monitor_deliveries` \| Recent delivery events across every monitor, with detection + delivery latency \|
		@@ -281,3 +282,3 @@ \| `twitter_x_user_stream_add_user` \| Compat drop-in for `twitter_monitor_create` using an x_user_stream-shaped envelope \|

		Is it read-only? No. 45 read tools work with just your API key; 29 write actions (post, like, retweet, follow, DM, media upload, article create/edit/publish/delete, monitor/webhook create/update/delete) act as a linked X account or per-call inline credentials, except monitor/webhook CRUD, which is account administration and needs only your API key.
		Is it read-only? No. 46 read tools work with just your API key; 29 write actions (post, like, retweet, follow, DM, media upload, article create/edit/publish/delete, monitor/webhook create/update/delete) act as a linked X account or per-call inline credentials, except monitor/webhook CRUD, which is account administration and needs only your API key.

		@@ -284,0 +285,0 @@ Which clients are supported? Claude Desktop, Cursor, Windsurf, and VS Code (Copilot agent mode), or any Model Context Protocol client.

@twitterapis/mcp - npm Package Compare versions

New alerts

Fixed alerts

Improved metrics