
Ollama
Connects to your local Ollama installation to run AI models privately without cloud APIs. Lets you query models, list available models, and get model details.
Integrates Ollama's local LLM models with MCP-compatible applications, enabling on-premise AI processing and custom model deployment while maintaining data control.
What it does
- Query local Ollama AI models
- List all downloaded models
- Get detailed model information
- Generate text responses locally
Best for
About Ollama
Ollama is a community-built MCP server published by rawveg that provides AI assistants with tools and capabilities via the Model Context Protocol. Integrate Ollama's local LLM models for secure, on-premise AI and data control with MCP-compatible apps. Deploy custom m It is categorized under ai ml, developer tools.
How to install
You can install Ollama in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
License
Ollama is released under the AGPL-3.0 license.
๐ฆ Ollama MCP Server
Supercharge your AI assistant with local LLM access
An MCP (Model Context Protocol) server that exposes the complete Ollama SDK as MCP tools, enabling seamless integration between your local LLM models and MCP-compatible applications like Claude Desktop and Cline.
Features โข Installation โข Available Tools โข Configuration โข Retry Behavior โข Development
โจ Features
- โ๏ธ Ollama Cloud Support - Full integration with Ollama's cloud platform
- ๐ง 14 Comprehensive Tools - Full access to Ollama's SDK functionality
- ๐ Hot-Swap Architecture - Automatic tool discovery with zero-config
- ๐ฏ Type-Safe - Built with TypeScript and Zod validation
- ๐ High Test Coverage - 96%+ coverage with comprehensive test suite
- ๐ Zero Dependencies - Minimal footprint, maximum performance
- ๐ Drop-in Integration - Works with Claude Desktop, Cline, and other MCP clients
- ๐ Web Search & Fetch - Real-time web search and content extraction via Ollama Cloud
- ๐ Hybrid Mode - Use local and cloud models seamlessly in one server
๐ก Level Up Your Ollama Experience with Claude Code and Desktop
The Complete Package: Tools + Knowledge
This MCP server gives Claude the tools to interact with Ollama - but you'll get even more value by also installing the Ollama Skill from the Skillsforge Marketplace:
- ๐ This MCP = The Car - All the tools and capabilities
- ๐ Ollama Skill = Driving Lessons - Expert knowledge on how to use them effectively
The Ollama Skill teaches Claude:
- Best practices for model selection and configuration
- Optimal prompting strategies for different Ollama models
- When to use chat vs generate, embeddings, and other tools
- Performance optimization and troubleshooting
- Advanced features like tool calling and function support
Install both for the complete experience:
- โ This MCP server (tools)
- โ Ollama Skill (expertise)
Result: Claude doesn't just have the car - it knows how to drive! ๐๏ธ
๐ฆ Installation
Quick Start with Claude Desktop
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"ollama": {
"command": "npx",
"args": ["-y", "ollama-mcp"]
}
}
}
Global Installation
npm install -g ollama-mcp
For Cline (VS Code)
Add to your Cline MCP settings (cline_mcp_settings.json):
{
"mcpServers": {
"ollama": {
"command": "npx",
"args": ["-y", "ollama-mcp"]
}
}
}
๐ ๏ธ Available Tools
Model Management
| Tool | Description |
|---|---|
ollama_list | List all available local models |
ollama_show | Get detailed information about a specific model |
ollama_pull | Download models from Ollama library |
ollama_push | Push models to Ollama library |
ollama_copy | Create a copy of an existing model |
ollama_delete | Remove models from local storage |
ollama_create | Create custom models from Modelfile |
Model Operations
| Tool | Description |
|---|---|
ollama_ps | List currently running models |
ollama_generate | Generate text completions |
ollama_chat | Interactive chat with models (supports tools/functions) |
ollama_embed | Generate embeddings for text |
Web Tools (Ollama Cloud)
| Tool | Description |
|---|---|
ollama_web_search | Search the web with customizable result limits (requires OLLAMA_API_KEY) |
ollama_web_fetch | Fetch and parse web page content (requires OLLAMA_API_KEY) |
Note: Web tools require an Ollama Cloud API key. They connect to
https://ollama.com/apifor web search and fetch operations.
โ๏ธ Configuration
Environment Variables
| Variable | Default | Description |
|---|---|---|
OLLAMA_HOST | http://127.0.0.1:11434 | Ollama server endpoint (use https://ollama.com for cloud) |
OLLAMA_API_KEY | - | API key for Ollama Cloud (required for web tools and cloud models) |
Custom Ollama Host
{
"mcpServers": {
"ollama": {
"command": "npx",
"args": ["-y", "ollama-mcp"],
"env": {
"OLLAMA_HOST": "http://localhost:11434"
}
}
}
}
Ollama Cloud Configuration
To use Ollama's cloud platform with web search and fetch capabilities:
{
"mcpServers": {
"ollama": {
"command": "npx",
"args": ["-y", "ollama-mcp"],
"env": {
"OLLAMA_HOST": "https://ollama.com",
"OLLAMA_API_KEY": "your-ollama-cloud-api-key"
}
}
}
}
Cloud Features:
- โ๏ธ Access cloud-hosted models
- ๐ Web search with
ollama_web_search(requires API key) - ๐ Web fetch with
ollama_web_fetch(requires API key) - ๐ Faster inference on cloud infrastructure
Get your API key: Visit ollama.com to sign up and obtain your API key.
Hybrid Mode (Local + Cloud)
You can use both local and cloud models by pointing to your local Ollama instance while providing an API key:
{
"mcpServers": {
"ollama": {
"command": "npx",
"args": ["-y", "ollama-mcp"],
"env": {
"OLLAMA_HOST": "http://127.0.0.1:11434",
"OLLAMA_API_KEY": "your-ollama-cloud-api-key"
}
}
}
}
This configuration:
- โ Runs local models from your Ollama instance
- โ Enables cloud-only web search and fetch tools
- โ Best of both worlds: privacy + web connectivity
๐ Retry Behavior
The MCP server includes intelligent retry logic for handling transient failures when communicating with Ollama APIs:
Automatic Retry Strategy
Web Tools (ollama_web_search and ollama_web_fetch):
- Automatically retry on rate limit errors (HTTP 429)
- Maximum of 3 retry attempts (4 total requests including initial)
- Request timeout: 30 seconds per request (prevents hung connections)
- Respects the
Retry-Afterheader when provided by the API - Falls back to exponential backoff with jitter when
Retry-Afteris not present
Retry-After Header Support
The server intelligently handles the standard HTTP Retry-After header in two formats:
1. Delay-Seconds Format:
Retry-After: 60
Waits exactly 60 seconds before retrying.
2. HTTP-Date Format:
Retry-After: Wed, 21 Oct 2025 07:28:00 GMT
Calculates delay until the specified timestamp.
Exponential Backoff
When Retry-After is not provided or invalid:
- Initial delay: 1 second (default)
- Maximum delay: 10 seconds (default, configurable)
- Strategy: Exponential backoff with full jitter
- Formula:
random(0, min(initialDelay ร 2^attempt, maxDelay))
Example retry delays:
- 1st retry: 0-1 seconds
- 2nd retry: 0-2 seconds
- 3rd retry: 0-4 seconds (capped at 0-10s max)
Error Handling
Retried Errors (transient failures):
- HTTP 429 (Too Many Requests) - rate limiting
- HTTP 500 (Internal Server Error) - transient server issues
- HTTP 502 (Bad Gateway) - gateway/proxy received invalid response
- HTTP 503 (Service Unavailable) - server temporarily unable to handle request
- HTTP 504 (Gateway Timeout) - gateway/proxy did not receive timely response
Non-Retried Errors (permanent failures):
- Request timeouts (30 second limit exceeded)
- Network timeouts (no status code)
- Abort/cancel errors
- HTTP 4xx errors (except 429) - client errors requiring changes
- Other HTTP 5xx errors (501, 505, 506, 508, etc.) - configuration/implementation issues
The retry mechanism ensures robust handling of temporary API issues while respecting server-provided retry guidance and preventing excessive request rates. Transient 5xx errors (500, 502, 503, 504) are safe to retry for the idempotent POST operations used by ollama_web_search and ollama_web_fetch. Individual requests timeout after 30 seconds to prevent indefinitely hung connections.
๐ฏ Usage Examples
Chat with a Model
// MCP clients can invoke:
{
"tool": "ollama_chat",
"arguments": {
"model": "llama3.2:latest",
"messages": [
{ "role": "user", "content": "Explain quantum computing" }
]
}
}
Generate Embeddings
{
"tool": "ollama_embed",
"arguments": {
"model": "nomic-embed-text",
"input": ["Hello world", "Embeddings are great"]
}
}
Web Search
{
"tool": "ollama_web_search",
"arguments": {
"query": "latest AI developments",
"max_results": 5
}
}
๐๏ธ Architecture
This server uses a hot-swap autoloader pattern:
src/
โโโ index.ts # Entry point (27 lines)
โโโ server.ts # MCP server creation
โโโ autoloader.ts # Dynamic tool discovery
โโโ tools/ # Tool implementations
โโโ chat.ts # Each exports toolDefinition
โโโ generate.ts
โโโ ...
Key Benefits:
- Add new tools by dropping files in
src/tools/ - Zero server code changes required
- Each tool is independently testable
- 100% function coverage on all tools
๐งช Development
Prerequisites
- Node.js v16+
- npm or pnpm
- Ollama running locally
Setup
# Clone repository
git clone https://github.com/rawveg/ollama-mcp.git
cd ollama-mcp
# Install dependencies
npm install
# Build project
np
---
*README truncated. [View full README on GitHub](https://github.com/rawveg/ollama-mcp).*
Alternatives
Related Skills
Browse all skillsUI design system toolkit for Senior UI Designer including design token generation, component documentation, responsive design calculations, and developer handoff tools. Use for creating design systems, maintaining visual consistency, and facilitating design-dev collaboration.
Guide for building TypeScript CLIs with Bun. Use when creating command-line tools, adding subcommands to existing CLIs, or building developer tooling. Covers argument parsing, subcommand patterns, output formatting, and distribution.
Use when working with the OpenAI API (Responses API) or OpenAI platform features (tools, streaming, Realtime API, auth, models, rate limits, MCP) and you need authoritative, up-to-date documentation (schemas, examples, limits, edge cases). Prefer the OpenAI Developer Documentation MCP server tools when available; otherwise guide the user to enable `openaiDeveloperDocs`.
Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals. Use PROACTIVELY for API documentation or developer portal creation.
Integrate Vercel AI SDK applications with You.com tools (web search, AI agent, content extraction). Use when developer mentions AI SDK, Vercel AI SDK, generateText, streamText, or You.com integration with AI SDK.
Use when building MCP servers or clients that connect AI systems with external tools and data sources. Invoke for MCP protocol compliance, TypeScript/Python SDKs, resource providers, tool functions.