agent-x-search
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@agent-x-searchSearch X for recent posts about AI agents and include original post URLs."
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.
Agent X Search
Give your agent native X search, with original-post citations and transparent usage.
中文 · Client setup · Recorded walkthrough · Measured overhead
An unofficial, local stdio MCP server. Existing Grok subscription login by default; explicitly selected xAI API keys are also supported. No browser automation, HTTP server, background service, build step or runtime dependencies.
0.1.0 is available on GitHub Releases with an installable package archive and checksum. npm publication is pending; until then install the GitHub archive using the fixed-path instructions below. API-key mode is experimental and has not been live-tested. Verification matrix.
A 30-second walkthrough
Ask your agent:
Find one recent official Grok feature announcement on X. Include its date and original post URL.
A recorded subscription CLI run returned:
24 Aug 2026 — Grok Voice Think Fast 2.0 announcement.
Original post: https://x.com/SpaceXAI/status/2091987538999197752
That call took 32.794 seconds, one model round. This is historical output from the local predecessor, not a speed promise or a new run of this candidate. Provenance and transcript replay.
Related MCP server: grok-build-plugin
Connect
Requires Node.js 24.5+, a local MCP client, network access, and an eligible Grok subscription session or xAI API key. Zero runtime dependencies does not mean zero account requirements or free searches.
After npm publication:
codex mcp add agent-x-search -- npx -y agent-x-search@0.1.0 serve
claude mcp add --transport stdio agent-x-search -- npx -y agent-x-search@0.1.0 serveSet your client's tool timeout to 300 seconds for long searches. Generate a complete config without changing files:
npx -y agent-x-search@0.1.0 config --client codexOther targets: claude-code, cursor, vscode, opencode, cline. One package, not six plugins. Client setup and verification levels.
Fixed-path installation
Avoid runtime npx lookups by installing into a directory you choose:
npm install --prefix /absolute/path/to/agent-tools --omit=dev --ignore-scripts agent-x-search@0.1.0
node --use-env-proxy /absolute/path/to/agent-tools/node_modules/agent-x-search/bin/agent-x-search.mjs config --client codex --localOn Windows, use your own absolute path and quote paths containing spaces. Paste the generated config into your client. It starts the installed file directly; no global npm installation or OS startup item is needed. Before publication, install the local agent-x-search-0.1.0.tgz instead of the package name.
From source: node --use-env-proxy bin/agent-x-search.mjs serve. Only contributors running tests need npm ci.
Authentication and billing
Default OAuth: install and sign in with the official Grok CLI, then run grok models to populate its metadata. This package reads that existing session into memory, implements no login, and copies no tokens. If expired, official grok models handles refresh. Ordinary searches do not launch the CLI.
The subscription proxy is an internal compatibility surface, not a guaranteed public third-party API. Eligibility, quota and protocol behavior can change. This project is not affiliated with xAI or X and does not promise unlimited or free access.
Explicit API-key mode: use serve --auth api-key with XAI_API_KEY in the MCP server environment. It calls the official xAI Responses endpoint and incurs API charges; no Grok CLI is required. This path has offline contract coverage, not live validation. Never put a key in a prompt or issue.
There is no automatic billing switch. Setting XAI_API_KEY alone does not change OAuth mode. Failed or uncertain requests are never retried or sent to another backend.
npx -y agent-x-search@0.1.0 doctor
npx -y agent-x-search@0.1.0 doctor --auth api-keyDoctor only reads local state. It does not search, refresh tokens, or validate credentials against xAI.
Tools
Tool | Behavior |
| Default and normally the only tool. One Responses request; xAI may perform several internal searches. |
| Opt in with |
Both default to Grok 4.6; --model MODEL selects another model available to your auth mode without a discovery request. API-key mode rejects --enable-deep to avoid mixing billing modes.
Inputs: query, include_handles or exclude_handles, inclusive from_date/to_date, desired count (1–20), media (none, images, videos, both), and detail (brief, standard, detailed). Count/detail are guidance, not retrieval guarantees. Native parameter contract.
Results retain answer, x_citations, citation_count, citation_status, backend, model, elapsed_ms; add auth_mode, usage, and incomplete. Missing usage is unknown, not zero. Verify claims against original posts. MCP structured content includes a JSON text fallback for compatibility; client handling determines actual context usage.
Configure and troubleshoot
Flags override environment variables, then defaults. No project config file is needed. All settings and errors.
reauth_required: use officialgrok modelsorgrok login.cli_metadata_required: rungrok models; version headers come from its cache.cli_unavailable: install official Grok CLI or set--grok-cli; direct API-key search does not need it.unsafe_cli_integrations: deep mode refuses your discovered hooks/plugins/MCP/LSP integrations; direct search is independent of that toolset.rate_limited: wait for quota availability; no retry occurred.request_uncertain: a timeout may already have consumed quota or API spend. Do not assume it was free.Startup/discovery failure: run doctor as the same OS user, check Node/paths, then the client's MCP diagnostics. No model call is needed to diagnose transport.
No telemetry or persistent result cache. Grok may retain its normal CLI session metadata. See engineering evidence, architecture and limits, and contributing. MIT licensed.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
No tool schema history has been recorded yet.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Live AI-native web search with citations. One tool for every MCP client. Flat per-request pricing.
X (formerly Twitter) posts, profiles, and search for AI agents. Free key, self-minted, no signup.
Search GitHub, npm, PyPI, StackOverflow, ArXiv from one MCP — built for coding agents.
Twitter (X) API alternative for AI agents: tweet search, profiles, followers. $0.0002 per result.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceSearch X (formerly Twitter) in real-time from your AI assistant using xAI's Grok API, with no X API account required.57MIT
- AlicenseNot gradedqualityBmaintenanceLive X (Twitter) and web search for any coding agent through your existing Grok subscription. Exposes a grok_search MCP tool, so no X API key or X developer account is needed.5925Apache 2.0
- AlicenseBqualityCmaintenanceEnables interacting with Twitter/X through natural language, including searching tweets, posting, sending DMs, and managing timelines via any MCP client.8MIT
- FlicenseNot gradedqualityDmaintenanceEnables real-time search of X (Twitter) posts, user timelines, and trends using either xAI's Responses API or the official X API v2.4-
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/Fryingpan-Jason/agent-x-search'
If you have feedback or need assistance with the MCP directory API, please join our Discord server