Ask Ollama

io.github.LykhoydaPublished by GitHub account Lykhoydav0.7.0Updated Oct 24, 2026

Bridge Claude with local Ollama LLMs for private AI-to-AI collaboration — no API keys, fully local

VerifiedSTDIODesktop onlyDeveloper ToolsAI & ML

Overview

AI-generated overview

Lets an assistant consult a local Ollama model for a private, offline second opinion on code, diffs, or plans.

What you can do
Exposes an ask-ollama tool that sends a prompt to a locally running Ollama model and returns its response, with optional session replay via sessionId. It is part of the Ask LLM family, so the same package can also route prompts to other provider CLIs, but this entry covers the Ollama-only server. Responses are returned as structured output alongside human-readable text.
When to use it
Use it when you want another model to review code, debate a plan, or explain a file without sending anything to a cloud provider. It suits offline or privacy-sensitive environments where a local model is already available.
Requirements
Node.js 24+ on Linux or macOS, and a locally running Ollama server with the desired model pulled. Optional environment variables: OLLAMA_HOST (default GMCPT_TIMEOUT_MS (default 300000), GMCPT_LOG_LEVEL (default warn).
Before you install
The server runs a local process and talks to your Ollama instance; prompts and any file content you include are sent to that local model. It does not require API keys, but it can read workspace files if the assistant passes them. Review what the assistant sends before relying on it for sensitive code.

Installation

In SourceWeft

  1. Open Ask Ollama in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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.

text
You:    ask codex to review src/auth.ts for security issuesCodex:  ⚠ verifyToken() compares tokens with === — not timing-safe (line 42)        ⚠ the session cookie is missing a SameSite attributeClaude: Good catches — applying both fixes to src/auth.ts.

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.

bash
npm i -g @ask-llm/mcp && ask-llm 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:

text
Ask Codex to review my staged changes for bugs and missing error handling. Check each finding against the source before proposing fixes.

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.

HostExperience
Claude CodeReviews, plan critique, comparisons; isolated reviewers and opt-in per-edit pairing
Codex, Cursor, Gemini CLITools and portable workflows; pairing on demand
Grok BuildTools and portable workflows; opt-in per-edit pairing
AntigravityTools; setup prints a manual step for workflows
Pi 0.83.0+Native tools and portable workflows; opt-in per-edit pairing
Claude DesktopTools only
OpenCodeTools and portable workflows; setup verified with fixtures only

See host compatibility for the complete matrix and manual setup limits, including existing Codex registrations.

Supported providers

ProviderAccess
CodexYour authenticated Codex CLI/account
ClaudeYour authenticated Claude Code account; consult it from a host other than Claude Code
GrokAuthenticated Grok Build, an exact Cursor model, or the explicit metered xAI API option
AntigravityYour authenticated agy subscription; execution is off by default, and opt-in has no read-only guarantee
OllamaLocal models on your machine
GeminiAn eligible Gemini Code Assist Standard/Enterprise seat

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.

Source: README.md at commit ba91abc

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

3
  1. v0.7.0LatestSep 27, 2026
  2. v0.6.3Sep 26, 2026
  3. v0.6.2Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts