Anthropic Model Context Protocol (MCP) Server with Ollama Integration

Created By
jorgesandovala year ago
Model Context Protocol (MCP) server integrated with an external inference service (e.g., Ollama/Gemma3) via middleware.
Overview

What is the Simple MCP Server?

The Simple MCP Server is an implementation of the Anthropic Model Context Protocol (MCP) server that integrates with the Ollama inference service, allowing for efficient communication and context management between clients and AI models.

How to use the Simple MCP Server?

To use the Simple MCP Server, set up the server and middleware using Docker, and interact with it via API endpoints to send user messages and receive AI-generated responses.

Key features of the Simple MCP Server?

  • Implements the official MCP protocol for compatibility with various clients.
  • Middleware for communication with Ollama's Gemma model.
  • Supports context management and conversation history.
  • Provides standard prompt templates and error handling as per MCP specifications.

Use cases of the Simple MCP Server?

  1. Integrating AI inference capabilities into applications using the MCP protocol.
  2. Managing conversation contexts for chatbots and virtual assistants.
  3. Utilizing AI models for various tasks through a standardized interface.

FAQ from the Simple MCP Server?

  • What is the purpose of the MCP Server?

The MCP Server facilitates communication between clients and AI models while managing conversation contexts.

  • How do I install the Simple MCP Server?

You can install it using a setup script or manually by cloning the repository and using Docker.

  • Is the Simple MCP Server compatible with other AI models?

Yes, it is designed to work with any client that supports the Model Context Protocol.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jorgesandoval
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
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
Crevio

2 days ago