mcpbeat Sign in

Xflux MCP Server

by yxs1640-png owner confirmed
local only

Xflux runs on your own machine — the client starts it, so there is no endpoint to ping. 52 installs a week from npm. Last commit 5 Nov 2026.

X/Twitter read API for agents: search, timelines, Smart Money. Claude/Cursor MCP. Not for posting.

Installs per day peak 147 · avg 12 · -19% w/w
a month agotoday
52
Installs / week
npm · @xflux/xflux-mcp-server
0
Stars
0 open issues
5 Nov 2026
Last commit
4 releases in 90 days
MIT
License
TypeScript

What the code does

We read the source, 3 d ago · rules 995398eba69f

In the project's build, not in the package

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

    return u.hostname.toLowerCase() === "hooks.slack.com" && u.pathname.startsWith("/services/");

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Nothing serious here today

Today is the operative word: we check Xflux every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add xflux -e 'XFLUX_API_KEY=<XFLUX_API_KEY>' -- npx -y @xflux/xflux-mcp-server
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "xflux": {
      "command": "npx",
      "args": [
        "-y",
        "@xflux/xflux-mcp-server"
      ],
      "env": {
        "XFLUX_API_KEY": "<XFLUX_API_KEY>"
      }
    }
  }
}
~/.codex/config.toml
[mcp_servers.xflux]
command = "npx"
args = ["-y", "@xflux/xflux-mcp-server"]
env = { XFLUX_API_KEY = "<XFLUX_API_KEY>" }
.cursor/mcp.json
{
  "mcpServers": {
    "xflux": {
      "command": "npx",
      "args": [
        "-y",
        "@xflux/xflux-mcp-server"
      ],
      "env": {
        "XFLUX_API_KEY": "<XFLUX_API_KEY>"
      }
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "xflux": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@xflux/xflux-mcp-server"
      ],
      "env": {
        "XFLUX_API_KEY": "<XFLUX_API_KEY>"
      }
    }
  }
}

Put your own value in place of <XFLUX_API_KEY> (API key from https://www.xfluxapi.com/dashboard/api-keys (free tier available)). The author’s registry entry marks it as required.

Optional settings from the registry entry, left out of the block above: XFLUX_API_BASE (Optional API base URL (default https://www.xfluxapi.com/api/v1)).

Alternatives to Xflux

same job, measured the same way
Shippost MCP
by ryankramer

Twitter/X tools for AI agents — read timelines, post tweets, search, and engage

97 installs/wk local only
twscrape Twitter/X (read-only)
by jsilets

Read-only X/Twitter MCP: posts, threads, replies, search via twscrape. No API key.

558 installs/wk local only
Twitterapi MCP Server
by kaitoinfra

Twitter/X read-only MCP server — 12 tools: search, users, tweets, followers, timelines, trends.

12 tools answering
twitr.sh
by twitr

X/Twitter reads, search, monitors and posting. Pay-per-call in USDC — no signup, no API keys.

14 tools answering
TwtAPI
by tonygjj

Hosted Twitter/X tools for search, users, timelines, followers, trends, and research.

answering
X Twitter
by veezee

X (formerly Twitter) posts, profiles, and search for AI agents. Free key, self-minted, no signup.

answering
TweetAPI MCP
by tweetapi

Read-only public Twitter data and TweetAPI docs for AI agents. Not affiliated with X Corp.

answering
Prowlo — Reddit & X for AI agents
by prowlo

Reddit & X data for AI agents over MCP. Semantic search, hosted, no Reddit API.

43 tools answering

Xflux — questions

Answers built from our own checks of this server.

Why is there no uptime for Xflux?
Xflux runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @xflux/xflux-mcp-server was installed 52 times last week.
How do I connect Xflux?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls @xflux/xflux-mcp-server straight from npm; nothing to host, nothing to sign up for.
How many people use Xflux?
The npm package @xflux/xflux-mcp-server was installed 52 times in the last week. Week over week that is -19%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Xflux open source?
Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.