ollama-MCP-server

Created By
NewAITeesa year ago
Overview

what is ollama-MCP-server?

The ollama-MCP-server is a Model Context Protocol (MCP) server that facilitates seamless integration between local Ollama LLM instances and MCP-compatible applications, providing advanced task decomposition, evaluation, and workflow management.

how to use ollama-MCP-server?

To use the ollama-MCP-server, install it via pip, configure your environment variables, and run the server. You can then interact with it using various tools to manage tasks and evaluate results.

key features of ollama-MCP-server?

  • Task decomposition for complex problems
  • Result evaluation and validation
  • Management and execution of Ollama models
  • Standardized communication via MCP protocol
  • Advanced error handling with detailed messages
  • Performance optimizations like connection pooling and LRU caching

use cases of ollama-MCP-server?

  1. Decomposing complex tasks into manageable subtasks.
  2. Evaluating task results against specified criteria.
  3. Running queries on Ollama models for various applications.

FAQ from ollama-MCP-server?

  • What is the purpose of the ollama-MCP-server?

It serves as a bridge between local Ollama LLM instances and applications using the MCP protocol, enhancing task management and evaluation.

  • How do I install the ollama-MCP-server?

You can install it using pip with the command pip install ollama-mcp-server.

  • Can I customize the server settings?

Yes, you can adjust performance-related settings in the config.py file.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
NewAITees
Star
0
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago