Sharing my new skill!

It keeps track of high-signal X accounts for top AI news, papers, projects, etc.

Total gamechanger for me.

Built with X MCP tools. Give your agent the skill and tell it to generate the artifact with top stories.

Works for Codex, Claude, Hermes, OpenClaw, or whatever you use.

3 steps:

1. Set up X MCP - X API: https://docs.x.com/tools/mcp#x-mcp-%E2%80%94-x-api…

2. Install skill here: https://github.com/dair-ai/dair-academy-plugins/tree/main/plugins/x-agent-intelligence…

3. Run prompt: “Use the x-agent-intelligence skill to build a self-contained local feed from my X MCP connection; ask for my source handles if needed, save feed.html, and validate it.”

It should generate a nice, beautiful HTML artifact like the one shown in the clip. You can tune it however you want.

You can then set a schedule/automation to do this daily or whatever cadence you prefer. I have it every 4 hours.

You will need to curate the X accounts yourself, but I have shared a few good ones under the assets.

You can ask your agent to tune it to however you like.

I have also shared my personal feed with our community here: https://academy.dair.ai/dashboard/resources/x-agent-intelligence…

I understand if it gets tricky to set up. Please reach out to me in the community forum. I plan to do a little tutorial or live session soon to help others reproduce the process.

You can also store the feed as a wiki, as I have in my own implementation, but that’s optional.

If you encounter any issues or have ideas on how to improve it, please open a PR.

MCP servers for the X API and X developer docs - X

Source: https://docs.x.com/tools/mcp TwoMCP(Model Context Protocol) servers are available for working with X from AI tools:

X MCP — X API

Connect any MCP-compatible AI tool (Grok Build, Cursor, Claude, VS Code, and others) directly to theX API. The model can then search the full archive, look up users, manage bookmarks, fetch trends and news, and draft Articles — all with your own X account’s permissions.The X API exposes a hostedStreamable HTTPMCP server at**https://api\.x\.com/mcp(protocol2025\-06\-18,serverInfo: xmcp). You reach it through the open-sourcexurl mcp**bridge, which handles OAuth for you and injects a fresh Bearer token on every call.

Capabilities at a glance

How it works

X’s OAuth requiresyour owndeveloper app. There is no dynamic client registration, andapi\.x\.com/mcpdoes not advertise native MCP OAuth discovery. Instead of pointing your client at the URL directly, you run a tiny local bridge. The bridge owns the app identity, performs the one-time login, and keeps the token fresh.

• The bridge runs via thenpm launcher(npx), so there isno separate install step.
• Onfirst run with no cached token, it opens your browser for a one-time OAuth2 login, then caches andauto-refreshesthe token forever after.
• All diagnostics go tostderr;stdout stays a clean JSON-RPC channel.

Getting started

Pick one of two routes:

• **Simple — App-only Bearer.**Paste your app’s Bearer token into anAuthorizationheader on the MCP client. No bridge, no browser login. Read-only endpoints; no user context (can’t act as you). Works with clients that support remote MCP with custom headers.
• **Full —xurl mcpbridge (OAuth 2.0 user context).**A local bridge handles the OAuth 2.0 PKCE login and auto-refreshes tokens, so the model acts with your account’s scopes. Required for writes (bookmarks, Articles) and any user-context tool.

Simple route (app-only Bearer)

1. Create an X appin theX Developer Portal.
2. Copy your App-only Bearer tokenfrom the app’s “Keys and tokens” page.
3. Point your client athttps://api\.x\.com/mcpwith the token as anAuthorizationheader — seeApp-only (direct URL, no bridge)below for the snippet.

Full route (xurl bridge)

1. Create an X appwithOAuth 2.0enabled.
2. Register the redirect URIhttp://localhost:8080/callbackon the app (required for the first-run browser login). To use a different one, setREDIRECT\_URIand register that instead.
3. Copy yourCLIENT\_IDandCLIENT\_SECRET— you’ll put them in the client config. If you ever runxurl auth oauth2manually (e.g., the headless flow below), export them as environment variables in that shell first — the login fails in the browser without them.
4. Have Node.js installed(fornpx).
5. We recommend youinstallxurl:

Connect your client

1. Grok Build

Or add the xurl bridge with one command (the\-eflags become the server’s environment, args after\-\-go tonpx):

Verify and list:

The first time a tool is invoked (or ondoctor), your browser opens for the X login — complete it once and you’re set.

2. Cursor

Create~/\.cursor/mcp\.json(global, all projects) or\.cursor/mcp\.json(this project only):

Then openCursor → Settings → MCP, confirmxapishows a green dot and its tools. On first use Cursor spawns the bridge and your browser opens for login; the tool list populates once the handshake completes.

3. Claude Desktop

Editclaude\_desktop\_config\.json(macOS:~/Library/Application Support/Claude/, Windows:%APPDATA%\\Claude\\):

Restart Claude Desktop; the X tools appear in the tools (🔌) menu.

4. VS Code (GitHub Copilot / Agent mode)

Add to\.vscode/mcp\.json:

5. Any MCP client

xurl bridge (stdio):

If you installedxurlnatively, replacecommand/argswith"command": "xurl", "args": \["mcp", "https://api\.x\.com/mcp"\].App-only Bearer (remote HTTP):

Authentication

OAuth 2.0 user context (default)

The bridge authenticates asyou(PKCE flow), so tools act with your account’s scopes. Resolution order for credentials:CLIENT\_ID/CLIENT\_SECRETenv vars → the active app in~/\.xurl. The bridge caches tokens in~/\.xurland refreshes them automatically (including a forced refresh after a401).

First-run browser login

With no cached token, the bridge prints to stderr and opens your browser:

The MCP handshake is held until you finish — that’s why clients need a generousstartup\_timeout\_sec.

Headless / remote machines

No reachable browser? Authenticate once out-of-band, then start the client:

App-only (direct URL, no bridge)

For read endpoints, you can skip the bridge and point a client straight at the URL with astatic App-only Bearer token. This is useful for clients that support remote MCP with custom headers:

Trade-off: no auto-refresh and no user context (no actions as you). The bridge is recommended for full functionality.

Multiple apps & accounts

In a client config, add"\-\-app", "my\-app"or"\-u", "alice"toargs.

Configuration reference

Advanced env overrides (rarely needed):AUTH\_URL,TOKEN\_URL,API\_BASE\_URL,INFO\_URL.

Verify & troubleshoot

Security & best practices

• Treat~/\.xurland access tokens as secrets— don’t paste them into chats, logs, or shared configs. Prefer per-project\.mcp\.json/\.grok/config\.tomlthat reference env vars over committing raw secrets.
• Use a dedicated appfor MCP with only the scopes you need.
• Writes count against rate limits(bookmarks,article\_publish) and are stricter than reads; expect occasional429s and back off.
• The bridge is local— your credentials never leave your machine except as a Bearer token sent over TLS toapi\.x\.com.

Docs MCP — documentation search

X hosts an MCP server for the X API documentation athttps://docs\.x\.com/mcp. Connect it to your AI tool to search and read documentation pages without leaving your workflow.

Available tools

Configuration

Add the docs MCP server to your MCP client configuration:

This is useful when you’re building with the X API and want your AI assistant to look up endpoint details, authentication guides, or code examples on the fly.

Using both servers together

You can connect both MCP servers simultaneously. This gives your AI assistant the ability to both look up documentationandcall the API.Grok Build(~/\.grok/config\.toml):

Cursor / Claude-style(mcp\.json):

OpenAPI specification

The machine-readable API specification for all X API v2 endpoints.

You can use it to auto-generate API clients, import intoPostman, feed into custom AI agents, or validate request/response schemas.