Call Grok Bot

Name: Call Grok Bot
Author: ZensHQ

作者：ZensHQ版本 0.1.3i★ –i在你的电脑上运行

注册名称ai.zens/call-grokbot

安装

概览

作者提供的说明（英文原文）

Consult existing Grok Bots from Codex and Claude Code using official Cursor browser login.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 网页与浏览器

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： CALL_GROKBOT_AUTH_MODE

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "call-grokbot": {
      "command": "npx",
      "args": [
        "-y",
        "call-grokbot"
      ],
      "env": {
        "CALL_GROKBOT_AUTH_MODE": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add call-grokbot --env CALL_GROKBOT_AUTH_MODE=your-value -- npx -y call-grokbot

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "call-grokbot": {
      "command": "npx",
      "args": [
        "-y",
        "call-grokbot"
      ],
      "env": {
        "CALL_GROKBOT_AUTH_MODE": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "call-grokbot": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "call-grokbot"
      ],
      "env": {
        "CALL_GROKBOT_AUTH_MODE": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

CALL_GROKBOT_AUTH_MODE env
Use the official Cursor CLI browser session. Run call-grokbot login before use.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过域名 zens.ai 验证（注册中心会核实域名所有权）
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“网页与浏览器”中的其他服务器比较i

星标数多于此分类中其他 880 个服务器的 0%
发布到注册中心的时间比此分类中其他 880 个服务器的 87% 更新
基础检查结果等于或优于此分类中其他 880 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Call Grok Bot 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.1.3）于5天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Browser Use, Chrome DevTools MCP, MCP Server Browser

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Browser Use

作者：browser-use

Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.

电脑或云端★ 120,087MIT17天前更新

安装

Chrome DevTools MCP

作者：ChromeDevTools

MCP server for Chrome DevTools

在你的电脑上运行★ 54,821Apache-2.016天前更新

安装

MCP Server Browser

作者：bytedance

MCP server for browser use access

在你的电脑上运行★ 39,550Apache-2.014个月前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

call-grokbot

Ask your existing Grok Bots from Codex and Claude Code. A local stdio MCP server sends one self-contained task, reads incremental replies, and can interrupt a contacted bot. Your bot keeps its existing conversation, memory, and connected tools.

Unofficial. Not affiliated with, endorsed by, or supported by Cursor / Anysphere, xAI / Grok, OpenAI, or Anthropic. The Grok Bot RPC is undocumented and may change. No public model-inference endpoint is provided.

English · 日本語 · Español · Português (Brasil) · 简体中文 · 繁體中文

Authentication details

Watch the demo

Click the cover to watch the 50-second demo on YouTube (English narration).

How it works

Before you start

Install Node.js 22.13+, npm, and Git.
Install and sign in to the client you want to use: Codex or Claude Code. Your coding client's account is separate from the Cursor login below.
Install the official Cursor CLI.
Have a Grok Bot account and at least one existing bot. Use the exact bot name shown in your app; this package does not create bots.

Choose the plugin guide for Codex or Claude Code. Both plugins include the consult skill and start the MCP server with a pinned npx package. You do not need a global call-grokbot install, a source checkout, an npm account, or a personal API key.

macOS browser authentication uses the official CLI's login Keychain entries. Linux and Windows use the official CLI's auth file. Do not copy tokens into MCP configuration. Real-account plugin tests passed on macOS; Linux and Windows have CI coverage, but their real-account login flows have not been verified.

Plugin release 0.1.2 uses npm runtime 0.1.1. Its npx commands pin the official npm tarball URL, so npm cannot substitute the current same-name source checkout. This fixes command not found and MCP CONNECTION_CLOSED inside this repository and also works with an empty cache. No global package installation is required.

Codex plugin quickstart

1. Install the plugin in your terminal

codex plugin marketplace add ZensHQ/call-grokbot --ref plugin-v0.1.2

codex plugin add call-grokbot@call-grokbot codex plugin list

Confirm that call-grokbot@call-grokbot is installed and enabled. These are terminal commands. If your Codex installation does not recognize plugin, update to a version that supports plugin commands. See the official Codex plugin documentation.

2. Sign in to the bot account in your terminal

npx --yes https://registry.npmjs.org/call-grokbot/-/call-grokbot-0.1.1.tgz login

npx --yes https://registry.npmjs.org/call-grokbot/-/call-grokbot-0.1.1.tgz doctor

login runs the official Cursor CLI's agent login. In the browser, select the account that owns your bot and complete any security check. doctor should report "authenticated": true, "authMode": "browser", and "cursorCliFound": true, without printing credentials.

3. Open a new Codex session and call the skill

Start Codex from the project you want to work in:

codex

Type this in the Codex conversation, not in your terminal:

$call-grokbot:consult List my existing bots. Do not send any message.

Choose an exact name from the result. In the example below, replace Research Bot with your bot's actual name:

$call-grokbot:consult Ask my existing bot "Research Bot" to reply exactly PONG.

Send the task once. If it is running, use check until it finishes; do not resend.

This sends a real message to that bot's existing conversation. A successful check means you received PONG and the task reached finished; an initial acknowledgement is not enough. For a real task, replace the PONG request with one self-contained brief containing the relevant facts, constraints, allowed actions, and desired output.

Claude Code plugin quickstart

1. Install the plugin in your terminal

claude plugin marketplace add ZensHQ/call-grokbot

claude plugin install call-grokbot@call-grokbot --scope user claude plugin list

Confirm that call-grokbot@call-grokbot is enabled. User scope makes it available to your Claude Code projects on this machine. If you are already inside Claude Code, the interactive equivalents are:

/plugin marketplace add ZensHQ/call-grokbot

/plugin install call-grokbot@call-grokbot

In the interactive install panel, choose Install for you (user scope). See the official Claude Code plugin documentation for other installation scopes.

2. Sign in to the bot account in your terminal

npx --yes https://registry.npmjs.org/call-grokbot/-/call-grokbot-0.1.1.tgz login

npx --yes https://registry.npmjs.org/call-grokbot/-/call-grokbot-0.1.1.tgz doctor

Complete the official Cursor CLI browser sign-in with the account that owns your bot. Confirm "authenticated": true, "authMode": "browser", and "cursorCliFound": true in the doctor result. If you already signed in for the Codex plugin on this machine, both plugins share that official CLI session; run npx --yes https://registry.npmjs.org/call-grokbot/-/call-grokbot-0.1.1.tgz doctor to check it instead of signing in again.

3. Check the connection, then open a new Claude Code session

In your terminal:

claude mcp list

claude

The health check should show plugin:call-grokbot:call-grokbot as connected. Allow the server to finish connecting before your first request. If a session was open before installation, start a new one so it loads the plugin and skill.

Type this in the Claude Code conversation:

/call-grokbot:consult List my existing bots. Do not send any message.

Replace Research Bot below with an exact existing name from the result:

/call-grokbot:consult Ask my existing bot "Research Bot" to reply exactly PONG.

Send the task once. If it is running, use check until it finishes; do not resend.

This is a real message in your bot's conversation. Verify both PONG and finished. For normal work, provide the relevant content in the brief: the bot cannot automatically see your Claude Code session or project files.

Setup troubleshooting

Symptom	What to do
`call-grokbot: command not found`	Plugin installs do not add a global executable. Use `npx --yes https://registry.npmjs.org/call-grokbot/-/call-grokbot-0.1.1.tgz login` or `npx --yes https://registry.npmjs.org/call-grokbot/-/call-grokbot-0.1.1.tgz doctor` in your terminal.
`command not found` or `CONNECTION_CLOSED` inside the call-grokbot source checkout	Use plugin 0.1.2 and its pinned npm tarball URL. Adding a fix to a terminal command alone does not update an already installed plugin. The older `--global` workaround can fail with an empty npm cache.
`CLI_MISSING`	Install the official Cursor CLI linked above. For a nonstandard location, set `CALL_GROKBOT_CURSOR_CLI` to its absolute executable path.
`AUTH_REQUIRED` or `AUTH_EXPIRED`	Run the pinned `npx` login command again, finish browser sign-in, and run `npx --yes https://registry.npmjs.org/call-grokbot/-/call-grokbot-0.1.1.tgz doctor`. MCP startup does not open a browser for you.
The skill or MCP tools are missing	Confirm the plugin is installed and enabled with `codex plugin list` or `claude plugin list`, then start a new client session. An MCP-only install does not include the skill.
Claude Code says the tools are unavailable or the server is still connecting	Wait for MCP startup and check `claude mcp list`. If the session still has no tools, open a new session after the health check reports connected. Do not resend a task that may already have been sent.
A bot is missing or a request returns 403	Confirm the exact bot name and the browser account you signed in to. A valid login does not guarantee access to the undocumented bot RPC; see Recovery and boundaries.

Update an existing plugin installation

A Codex marketplace pinned to an earlier tag stays on that tag. To move it to this plugin release, run these commands in your terminal:

codex plugin remove call-grokbot@call-grokbot

codex plugin marketplace remove call-grokbot codex plugin marketplace add ZensHQ/call-grokbot --ref plugin-v0.1.2 codex plugin add call-grokbot@call-grokbot

For the Claude Code user-scope installation:

claude plugin marketplace update call-grokbot

claude plugin update call-grokbot@call-grokbot --scope user

Start a new client session after updating. Your official Cursor CLI login is shared independently of the plugin and does not need to be repeated while valid.

Optional: direct MCP configuration

Use this instead of the plugin when you only need the four MCP tools. Do not install both paths in the same client, or you will get duplicate tools. This path does not include consult; ask the coding assistant to use the call-grokbot tools in an ordinary prompt.

First complete the same terminal login and doctor check:

npx --yes https://registry.npmjs.org/call-grokbot/-/call-grokbot-0.1.1.tgz login

npx --yes https://registry.npmjs.org/call-grokbot/-/call-grokbot-0.1.1.tgz doctor

For Codex, register the server from your terminal:

codex mcp add call-grokbot -- npx --yes https://registry.npmjs.org/call-grokbot/-/call-grokbot-0.1.1.tgz

For a bot allowlist and longer tasks, configure the same entry in ~/.codex/config.toml:

[mcp_servers.call-grokbot]

command = "npx" args = ["--yes", "https://registry.npmjs.org/call-grokbot/-/call-grokbot-0.1.1.tgz"] startup_timeout_sec = 30 tool_timeout_sec = 660 env = { CALL_GROKBOT_AGENTS = "Research Bot" }

For Claude Code, register the server from your terminal:

claude mcp add --transport stdio --scope user call-grokbot -- npx --yes https://registry.npmjs.org/call-grokbot/-/call-grokbot-0.1.1.tgz

Or use this .mcp.json in a trusted project instead of the user-scope entry:

"mcpServers": { "call-grokbot": { "command": "npx", "args": ["--yes", "https://registry.npmjs.org/call-grokbot/-/call-grokbot-0.1.1.tgz"], "env": { "CALL_GROKBOT_AUTH_MODE": "browser", "CALL_GROKBOT_AGENTS": "Research Bot" } } } }

Replace Research Bot with an exact existing name. Open a new client session after changing MCP configuration.

Optional: global or source installation

For a global command, install npm install --global call-grokbot@0.1.1. You can then use call-grokbot login, doctor, and the other subcommands directly instead of the pinned npx form.

To run from source:

git clone https://github.com/ZensHQ/call-grokbot.git

cd call-grokbot npm ci npm run build node dist/cli.js login node dist/cli.js doctor

Use node /absolute/path/to/call-grokbot/dist/cli.js for source commands. For JSON/TOML MCP configuration, set command to node and args to ["/absolute/path/to/call-grokbot/dist/cli.js"].

Four tools

Tool	Purpose
`list()`	List existing bots visible to the account, the optional allowlist, and local contacts. Sends no message.

| ask({agent, message, wait_seconds}) | Send once to an exact existing bot. A nonexistent o

只显示了开头部分；其余内容请在仓库中阅读

Call Grok Bot

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

需要你填写的值

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“网页与浏览器”中的其他服务器比较i

常见问题

替代选择

Browser Use

Chrome DevTools MCP

MCP Server Browser

作者的 README

call-grokbot

Watch the demo

How it works

Before you start

Codex plugin quickstart

1. Install the plugin in your terminal

2. Sign in to the bot account in your terminal

3. Open a new Codex session and call the skill

Claude Code plugin quickstart

1. Install the plugin in your terminal

2. Sign in to the bot account in your terminal

3. Check the connection, then open a new Claude Code session

Setup troubleshooting

Update an existing plugin installation

Optional: direct MCP configuration

Optional: global or source installation

Four tools