Mnevis MCP Server
Provides a tool to forward prompts from any MCP-compatible AI agent to a local Ollama instance, allowing the agent to offload language model tasks to a locally running LLM.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Mnevis MCP ServerExplain the difference between TCP and UDP."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Mnevis MCP Server
⚠️ This is an experiment.
A lightweight, zero-dependency Python MCP server that exposes a single do_everything tool.
Any AI agent that supports MCP can use it to offload all language-model work to a local
OpenAI-compatible endpoint, reducing cost on the agent's primary LLM.
How it works
AI Agent (e.g. Bob/Claude/Copilot/Cursor)
│
│ MCP stdio (JSON-RPC 2.0)
▼
mnevis server.py
│
│ HTTP POST /v1/chat/completions
▼
Local LLM (Ollama, LM Studio, llama.cpp, vLLM, …)The agent calls the do_everything tool with a prompt (and optional system instruction).
The server forwards the request to the local LLM using the standard OpenAI chat-completions API
and returns the model's response to the agent.
The tool description is worded so that any LLM automatically understands it should delegate
every task to the tool instead of reasoning on its own.
Related MCP server: MCP-123
Requirements
Python 3.11+
No third-party packages — uses the standard library only (
urllib,json,sys,os)A running local LLM that exposes a
/v1/chat/completionsendpoint
(e.g. Ollama, LM Studio, llama.cpp server, vLLM)
Configuration
All settings are read from environment variables at startup:
Variable | Default | Description |
|
| Base URL of the local LLM server |
|
| Port the LLM server listens on |
|
| Model name to pass in the request |
| (empty) | Optional API key (sent as |
Examples
Ollama (default port 11434):
MNEVIS_MODEL=llama3 python server.pyLM Studio (default port 1234):
MNEVIS_URL=http://localhost MNEVIS_PORT=1234 MNEVIS_MODEL=lmstudio-community/Meta-Llama-3-8B-Instruct python server.pyvLLM with API key:
MNEVIS_URL=http://my-gpu-box MNEVIS_PORT=8000 MNEVIS_MODEL=mistral-7b MNEVIS_API_KEY=secret python server.pyRunning the server
The server communicates over stdio (JSON-RPC 2.0), so it is spawned as a child process by
the MCP host — you do not run it manually in most cases.
To test it directly:
python server.pyThen paste a raw JSON-RPC message, e.g.:
{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"0.0.1"}}}Registering with an MCP host
Bob / Cursor / Claude Desktop
Add to your mcp.json (workspace or global):
{
"mcpServers": {
"mnevis": {
"command": "python",
"args": ["/absolute/path/to/mnevis-mcp/server.py"],
"env": {
"MNEVIS_URL": "http://localhost",
"MNEVIS_PORT": "11434",
"MNEVIS_MODEL": "llama3",
"MNEVIS_API_KEY": ""
}
}
}
}Replace the args path with the actual absolute path on your machine.
Set LOLA_PORT / LOLA_MODEL to match your local LLM setup.
Exposed tool
do_everything
Argument | Type | Required | Description |
| string | ✅ | The full task, question, or conversation to process |
| string | ❌ | Optional system / persona instruction for the local LLM |
The tool description explicitly instructs the calling agent to send every task here rather
than reasoning itself, ensuring maximum cost offloading.
Project layout
mnevis-mcp/
├── server.py # MCP server (single file, stdlib only)
├── pyproject.toml # Project metadata
├── README.md # This file
└── .gitignoreLicense
MIT
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Tools
Related MCP Servers
- Alicense-qualityDmaintenanceMCP server for toolhouse.ai. This does not rely on an external llm unlike the official server.Last updated4MIT
- Flicense-qualityDmaintenanceA minimal Python package for easily setting up and running MCP servers and clients, allowing functions to be automatically exposed as tools that LLMs can use with just 2 lines of code.Last updated22
- Alicense-qualityDmaintenanceAn MCP server that publishes CLI tools on your machine for discoverability by LLMsLast updated151MIT
- Alicense-qualityBmaintenanceA dead simple MCP server for exposing your app functions to AI agents like Claude Desktop.Last updated305MIT
Related MCP Connectors
MCP server exposing the Backtest360 engine API as tools for AI agents.
Local-first RAG engine with MCP server for AI agent integration.
MCP server for AI dialogue using various LLM models via AceDataCloud
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mar-co-za/mnevis-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server