1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@x-mcp search for recent tweets from @jack" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

x-mcp

by kandotrun

Overview Schema Related Servers Score Discussions

TypeScript

Remote

x-mcp

Read-only MCP server for Kan's twitter.2-38.com FxTwitter API proxy.

日本語版は下にあります: 日本語

Remote MCP endpoint

https://x.mcp.2-38.com/mcp

Discovery metadata:

https://x.mcp.2-38.com/.well-known/mcp.json

This server exposes MCP tools that call the existing public proxy endpoints under:

https://twitter.2-38.com/api/fx/2/...

Example upstream call wrapped by search_posts:

https://twitter.2-38.com/api/fx/2/search?q=from%3Ajack&feed=latest&count=10

Related MCP server: x-mcp

AI agent skill first

MCP tells an agent what tools exist, but a skill tells it when and how to use them. Before asking an AI agent to use this MCP, have it install or load the bundled skill:

https://raw.githubusercontent.com/kandotrun/x-mcp/main/skills/x-mcp/SKILL.md

Full copy/paste prompts are available here:

docs/agent-install-prompts.md

Short English prompt:

Install or load this x-mcp skill first:
https://raw.githubusercontent.com/kandotrun/x-mcp/main/skills/x-mcp/SKILL.md

Then configure MCP server `x` with:
https://x.mcp.2-38.com/mcp

Verify tools/list includes search_posts and call search_posts with
{ "q": "from:jack", "feed": "latest", "count": 2 }.
Use this only for public read-only X/Twitter search and retrieval through twitter.2-38.com.

MCP configuration

Hermes Agent

hermes skills inspect https://raw.githubusercontent.com/kandotrun/x-mcp/main/skills/x-mcp/SKILL.md
hermes skills install https://raw.githubusercontent.com/kandotrun/x-mcp/main/skills/x-mcp/SKILL.md --category social-media -y
hermes mcp add x --url https://x.mcp.2-38.com/mcp
hermes mcp test x

Or add this to ~/.hermes/config.yaml and restart Hermes / start a new session:

mcp_servers:
  x:
    url: "https://x.mcp.2-38.com/mcp"

Hermes will expose tools with the mcp_x_ prefix, for example mcp_x_search_posts.

Generic MCP clients

{
  "mcpServers": {
    "x": {
      "url": "https://x.mcp.2-38.com/mcp"
    }
  }
}

Use your client's HTTP / Streamable HTTP MCP transport setting if it requires an explicit transport type.

Tools

search_posts — call /2/search
get_post — call /2/status/:id
get_profile — call /2/profile/:handle
get_profile_statuses — call /2/profile/:handle/statuses
get_profile_media — call /2/profile/:handle/media
get_trends — call /2/trends
typeahead — call /2/typeahead
get_openapi — call /2/openapi.json

Smoke test

curl -sS https://x.mcp.2-38.com/health
curl -sS https://x.mcp.2-38.com/.well-known/mcp.json

For an MCP-level smoke test, call tools/list and then search_posts using your MCP client. A successful search_posts call with q=from:jack returns JSON text containing:

{
  "upstreamUrl": "https://twitter.2-38.com/api/fx/2/search?q=from%3Ajack&feed=latest&count=2",
  "status": 200
}

Local development

npm install
cp wrangler.example.jsonc wrangler.jsonc
npm run check
npx wrangler dev --config wrangler.jsonc

MCP endpoint locally:

http://localhost:8787/mcp

Deploy

cp wrangler.example.jsonc wrangler.jsonc
# Fill account_id in wrangler.jsonc if needed.
npm run deploy

wrangler.jsonc is intentionally gitignored so account-specific deployment config stays local.

Security and scope

Public, unauthenticated, read-only MCP endpoint.
Do not include secrets, private data, or access tokens in search queries.
Not for posting, liking, reposting, following, DMs, notifications, private accounts, or authenticated timelines.
Upstream availability/rate limits/response shape depend on the underlying FxTwitter service.

日本語

Kan の twitter.2-38.com FxTwitter API proxy を read-only で呼ぶ MCP server です。

公開MCP endpoint

https://x.mcp.2-38.com/mcp

Discovery metadata:

https://x.mcp.2-38.com/.well-known/mcp.json

このMCPは、既存の公開proxy endpointを呼びます。

https://twitter.2-38.com/api/fx/2/...

search_posts が包む upstream 呼び出し例:

https://twitter.2-38.com/api/fx/2/search?q=from%3Ajack&feed=latest&count=10

まずAIエージェントにskillを入れる

MCPだけだと「どの場面で、どう使うべきか」がAIに伝わりにくいので、このrepoにはAIエージェント向けskillを同梱しています。

Skill URL:

https://raw.githubusercontent.com/kandotrun/x-mcp/main/skills/x-mcp/SKILL.md

コピペ用の導入プロンプトはこちらです。

docs/agent-install-prompts.md

短い日本語プロンプト:

まず以下の x-mcp skill をインストール、または読み込んでください。
https://raw.githubusercontent.com/kandotrun/x-mcp/main/skills/x-mcp/SKILL.md

その後、MCP server `x` を以下で設定してください。
https://x.mcp.2-38.com/mcp

`tools/list` に `search_posts` が出ることを確認し、
`search_posts` を { "q": "from:jack", "feed": "latest", "count": 2 } で試してください。
このMCPは twitter.2-38.com 経由の公開X/Twitter情報取得専用で、read-only用途だけに使ってください。

MCP設定

Hermes Agent

hermes skills inspect https://raw.githubusercontent.com/kandotrun/x-mcp/main/skills/x-mcp/SKILL.md
hermes skills install https://raw.githubusercontent.com/kandotrun/x-mcp/main/skills/x-mcp/SKILL.md --category social-media -y
hermes mcp add x --url https://x.mcp.2-38.com/mcp
hermes mcp test x

CLIが使えない場合は、~/.hermes/config.yaml に次を追加してHermesを再起動、または新しいセッションを開始してください。

mcp_servers:
  x:
    url: "https://x.mcp.2-38.com/mcp"

Hermesでは mcp_x_search_posts のように mcp_x_ prefix付きでtoolが見えます。

汎用MCP client

{
  "mcpServers": {
    "x": {
      "url": "https://x.mcp.2-38.com/mcp"
    }
  }
}

client側でtransport指定が必要な場合は、HTTP / Streamable HTTP MCP transportを選んでください。

Tools

search_posts — /2/search を呼ぶ
get_post — /2/status/:id を呼ぶ
get_profile — /2/profile/:handle を呼ぶ
get_profile_statuses — /2/profile/:handle/statuses を呼ぶ
get_profile_media — /2/profile/:handle/media を呼ぶ
get_trends — /2/trends を呼ぶ
typeahead — /2/typeahead を呼ぶ
get_openapi — /2/openapi.json を呼ぶ

Smoke test

curl -sS https://x.mcp.2-38.com/health
curl -sS https://x.mcp.2-38.com/.well-known/mcp.json

MCPレベルでは、clientから tools/list → search_posts を確認してください。q=from:jack の成功例では、返ってくるJSON textに次のような内容が含まれます。

{
  "upstreamUrl": "https://twitter.2-38.com/api/fx/2/search?q=from%3Ajack&feed=latest&count=2",
  "status": 200
}

ローカル開発

npm install
cp wrangler.example.jsonc wrangler.jsonc
npm run check
npx wrangler dev --config wrangler.jsonc

ローカルMCP endpoint:

http://localhost:8787/mcp

デプロイ

cp wrangler.example.jsonc wrangler.jsonc
# 必要に応じて wrangler.jsonc の account_id を埋める
npm run deploy

wrangler.jsonc はアカウント固有の設定なのでgitignoreしています。

セキュリティと範囲

公開・認証なし・read-only のMCP endpointです。
search query に secret / private data / access token を入れないでください。
投稿、いいね、RT、フォロー、DM、通知、private account、認証timelineには使えません。
upstreamの可用性、rate limit、response shapeはFxTwitter側に依存します。

This server cannot be installed

license - not found

quality - not tested

maintenance

How are these scores calculated?

Maintenance

–Maintainers

–Response time

–Release cycle

–Releases (12mo)

Commit activity

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
open source
OpenAI
Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kandotrun/x-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server