@twitterapis/mcp 0.6.0 → 0.6.1

package/CHANGELOG.md

@@ -1,16 +1,23 @@
 # Changelog
 
+## 0.6.1 (2026-07-20)
+
+### Fixed
+
+- **The server advertised the wrong version.** `serverInfo.version` in the MCP handshake and the outbound `user-agent` header were both hardcoded to `0.3.0`, so every client since 0.4.0 was told it was talking to 0.3.0. Both now derive from `package.json`, so the literal cannot drift again.
+- Corrected a factual error in the 0.6.0 changelog entry below: the endpoint that stopped advertising `count` alongside `twitter_tweet_replies` is `twitter_tweet_thread`, not `twitter_tweet_retweeters`. `twitter_tweet_retweeters` does accept `count` and is unchanged.
+
 ## 0.6.0 (2026-07-20)
 
 ### Fixed
 
-- **Removed three phantom parameters from the published tool schemas.** Eleven write tools (`twitter_create_tweet`, `twitter_delete_tweet`, `twitter_favorite_tweet` / `twitter_unfavorite_tweet`, `twitter_retweet` / `twitter_unretweet`, `twitter_bookmark_tweet` / `twitter_unbookmark_tweet`, `twitter_follow_user` / `twitter_unfollow_user`, `twitter_dm_send`) advertised an optional `account` parameter that the API never accepted, so agents that passed it were silently ignored. `twitter_tweet_replies` and `twitter_tweet_retweeters` advertised the full pagination shape when the endpoint only accepts `cursor`.
+- **Removed three phantom parameters from the published tool schemas.** Eleven write tools (`twitter_create_tweet`, `twitter_delete_tweet`, `twitter_favorite_tweet` / `twitter_unfavorite_tweet`, `twitter_retweet` / `twitter_unretweet`, `twitter_bookmark_tweet` / `twitter_unbookmark_tweet`, `twitter_follow_user` / `twitter_unfollow_user`, `twitter_dm_send`) advertised an optional `account` parameter that the API never accepted, so agents that passed it were silently ignored. `twitter_tweet_replies` and `twitter_tweet_thread` advertised the full pagination shape when the endpoint only accepts `cursor`.
 - A fail-closed MCP-to-OpenAPI parity gate now runs on every `npm test`, so a tool schema can no longer drift from the live API contract unnoticed.
 - README: corrected the Links section (the REST base URL is `https://api.twitterapis.com`; removed a link to a status page that does not exist) and added an FAQ covering signup, read-vs-write scope, supported clients, billing, and data handling.
 
 ### Breaking
 
-- If your client explicitly passed `account` to a write tool, or `count` to `twitter_tweet_replies` / `twitter_tweet_retweeters`, those keys are no longer part of the schema. They were never honoured by the API, so behaviour is unchanged; only the advertised schema is now accurate.
+- If your client explicitly passed `account` to a write tool, or `count` to `twitter_tweet_replies` / `twitter_tweet_thread`, those keys are no longer part of the schema. They were never honoured by the API, so behaviour is unchanged; only the advertised schema is now accurate.
 
 ## 0.5.0 (2026-07-06)
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@twitterapis/mcp",
-  "version": "0.6.0",
+  "version": "0.6.1",
   "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.",
   "repository": {
     "type": "git",

package/src/index.js

@@ -16,8 +16,14 @@
 //
 // Run:  npx -y @twitterapis/mcp@latest   (stdio transport)
 
+import { createRequire } from "node:module";
 import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
 import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
+
+// Single source of truth for the version. Previously this was a literal in two
+// places and drifted: the package shipped 0.5.0 while the MCP handshake and the
+// outbound user-agent both still advertised 0.3.0.
+const VERSION = createRequire(import.meta.url)("../package.json").version;
 import { TOOLS, buildQuery } from "./tools.js";
 
 const API_KEY = process.env.TWITTERAPIS_KEY;
@@ -52,7 +58,7 @@ async function callEndpoint(path, args, method = "GET") {
     Authorization: `Bearer ${API_KEY}`,
     "x-api-key": API_KEY,
     accept: "application/json",
-    "user-agent": "twitterapis-mcp/0.3.0",
+    "user-agent": `twitterapis-mcp/${VERSION}`,
   };
   if (auth_token && ct0) {
     headers["x-auth-token"] = auth_token;
@@ -99,7 +105,7 @@ async function callEndpoint(path, args, method = "GET") {
 }
 
 // ── MCP server ───────────────────────────────────────────────────────────────
-const server = new McpServer({ name: "twitterapis", version: "0.3.0" });
+const server = new McpServer({ name: "twitterapis", version: VERSION });
 
 for (const tool of TOOLS) {
   const method = tool.method || "GET";