
Ask Grok
io.github.Lykhoyda由 GitHub 帳號 Lykhoyda 發布v0.3.0更新於 Oct 26, 2026
Consult Grok through xAI's metered API with exact model selection and no fallback
發布方自己的服務:Surface
概覽
讓編碼助理透過已登入的 Grok CLI 或 xAI 按量計費 API 諮詢 Grok,為程式碼或方案取得第二意見。
- 可以做什麼
- 在編碼助理工作階段內請 Grok 審查已暫存的變更、檔案或方案。
- 取得標明審查者與模型、引用相關程式碼的發現,或明確表示未發現問題的結論。
- 請 Grok 質疑方案:哪些假設可能失效、哪種更簡單的做法更符合限制條件。
- 明確選擇執行方式(xAI API 或 Grok CLI)、指定模型、推理強度、逾時與輸出 token 上限。
- 可在隨選審查之後選擇啟用逐次編輯的配對審查。
- 適用情境
- 適合已在編碼助理中工作、希望由另一家廠商的模型審查變更或評論方案,而不必複製貼上或離開工作階段的個人開發者或小型團隊。在採納修改前想要一次獨立檢查時特別有用。
- 執行需求
- 以 npm 套件形式透過 stdio 在本機執行,需要 Linux 或 macOS 上的 Node.js 24 以上。需要已登入的 Grok CLI,或為按量計費 API 在 XAI_API_KEY 中提供 xAI API 金鑰。宿主助理須已安裝並登入;安裝程式只註冊宿主與工作流程,不安裝或登入提供方。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Ask Grok,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
Ask LLM
Second opinions for coding agents.
Get a second opinion on your code or plan, inside your coding assistant, using the model subscriptions you already have.
For individual developers and small teams who already use a coding assistant and pay for another model subscription: ask a different vendor's model to review your changes or challenge your plan, without API keys, copy-paste, or leaving the session.
Install
You need Node.js 24+ on Linux or macOS. Before your first review, both your coding assistant (for example Claude Code) and the provider you will consult (for example Codex) must be installed and signed in. Ask LLM configures the connection; it does not install providers or sign you in. If a provider CLI such as Codex has never been signed in on this machine, sign in first and rerun setup.
Setup asks you to confirm each detected host and workflow. Inspect the preview, confirm your assistant's registration and workflows, decline the others, then follow any printed manual steps. Restart your assistant or start a new session in your project.
Your first review
With both Claude Code and Codex installed and signed in, open Claude Code in your project and ask:
Working in Codex with a Claude subscription? Ask Claude instead. Choose a provider from a different vendor than your current assistant. A successful review names the reviewer and model, cites relevant code, and reports findings or says it found none. Your assistant applies changes after you decide what to accept. If the request fails, run ask-llm doctor and follow the troubleshooting guide for your selected assistant and reviewer. Warnings about providers you do not use do not require installing them or adding API keys.
For plans, try: “Ask Claude to challenge this plan: what assumptions could fail, and what simpler approach would fit our constraints?”
After an on-demand review, pair review can add ongoing feedback. Pairing requires explicit opt-in; setup leaves it off. Grok CLI supports a per-edit hook with Codex Sol by default or Claude Opus 5.5 via reviewer: claude; shell reviews cover command text only.
Supported hosts
A host is the assistant you work in; a provider is the model you consult.
See host compatibility for the complete matrix and manual setup limits, including existing Codex registrations.
Supported providers
Cursor Agent can also consult exact models from your Cursor catalog. It is a connection route, with usage governed by your Cursor plan.
Trust and cost
Review runs use read-only provider controls; the assistant you work in remains the editor. Antigravity refuses execution until explicitly enabled and cannot guarantee read-only access after opt-in. Review only material you are allowed to share with the selected provider.
Calls consume your existing provider plan's quota or follow that account's billing. Grok's xAI API is a separate, metered option requiring an API key; Ask LLM never enables billing or overage for you. Ollama supports local inference. Ask LLM sends no telemetry; provider and host data policies still apply.
Agreement between models is not proof of correctness. Validate findings against the code, tests, and your requirements. See data flow and costs and fallbacks.
Migrating from @ask-llm/*
Follow the migration guide before retiring earlier registrations.
Upgrade or remove · Troubleshooting · Documentation
Contributions: CONTRIBUTING.md. Licensed under MIT.
來源:README.md,提交 ba91abc
工具
0版本歷史
3- v0.3.0最新Sep 27, 2026
- v0.2.0Sep 26, 2026
- v0.1.5Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分
其他 Grok 整合

Surface
me.grok.nova-otter-delta-cloud官方發布者
遠端 MCP 伺服器,用來展開短連結,並在助理開啟使用者貼上的網址前給出 fetch 或 skip 的判斷。
Grok Crypto Quant API
dev.fly.grok-backtest-api官方發布者
遠端 MCP 伺服器,提供按次付費的加密量化工具:無倖存者偏差回測、每日市場訊號、策略參數最佳化與代幣詐騙檢查。

Server Track Lab
由 GitHub 帳號 Surface-ops 發布
將伺服器端轉換事件送往廣告平台(Meta 即時、Google 與 LinkedIn 僅預覽),並查看工作區事件統計。

API Meter
由 GitHub 帳號 Surface-ops 發布
API Meter 依客戶、端點與方案統計 API 請求量,讓助理註冊 API、取得接入程式碼並讀取或匯出用量。
three.ws for Grok
由 GitHub 帳號 nirholas 發布
three.ws 遠端伺服器,讓助理依文字或圖片生成、綁定骨架、迭代與檢視 3D 模型和虛擬形象,並賦予其可持續沿用的代理人格。