Is this an official X (Twitter) MCP server?

No. It is Memtro's MCP server with Memtro's X (Twitter) connector behind it: the connector reads X (Twitter) through its API with the credentials you connect on Dashboard → Connections, and X (Twitter) publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in X (Twitter)?

Not yet. Today every X (Twitter) tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Social and reputation

X (Twitter) MCP server

X (Twitter) in any MCP client, through Memtro: X (Twitter) does not publish this server. Memtro's X (Twitter) connector reads X (Twitter) through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Read-only access to an X (Twitter) account: profile metrics, your recent posts with likes/reposts/impressions, mentions, recent search and account lookups. The X API is a paid, pay-per-use product: the app needs credits to read posts.

Reads

x_meProfile and metrics of the connected X account: name, @username, bio, followers, following, post count, verification.
x_postsThe connected account's own recent posts (newest first) with likes, reposts, replies, quotes, bookmarks and impressions.
x_mentionsPosts that mention the connected account (newest first) with author, text and engagement.
x_searchSearch public posts from the last 7 days with X query syntax: keywords, "exact phrase", from:user, to:user, @user, #tag, url:domain, -is:retweet…
x_userLook up a public X account by @handle: name, bio, location, website, followers, following, post count, verification and profile URL.

Connect it

First connect X (Twitter) on Dashboard → Connections, then add Memtro to your client once. The X (Twitter) tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

One command registers the server; the tools are then available in every session.

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer sk-memtro-..."

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared X (Twitter) connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› How did our posts perform this week?
› Who mentioned us in the last 24 hours?
› Search X for people talking about our product name this week
› How many followers does our account have now?
› Who is @competitor and how big is their following?

Questions

Is this an official X (Twitter) MCP server?: No. It is Memtro's MCP server with Memtro's X (Twitter) connector behind it: the connector reads X (Twitter) through its API with the credentials you connect on Dashboard → Connections, and X (Twitter) publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in X (Twitter)?: Not yet. Today every X (Twitter) tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.