
getsherlog/sherlog-mcp
Developer toolsЭта страница переведена автоматически. Технические детали смотрите в оригинале. Открыть оригинал
MCP that combats tools overload
Обзор
A powerful Model Context Protocol (MCP) server that provides a persistent IPython shell per session. The server only exposes a limited number of tools and at the core of it just exposes the following 2 - And the rest of the tools are more for supporting the LLM to write the code or call the appropriate cli to complete the task. There are some tools for code retrieval based on tree sitter but thats pretty much it. For example, installing packages or installing cli. Or doing introspection of variables in the ipython shell. The server also supports adding external mcp servers. The idea here is you can run mcp servers inside the shell that allows you to persist results in the shell with variables and results etc. One of the primary things I have noticed is that LLMs mess up when provided with a lot of tools and also as is quite evident by now.
README
Показан фрагмент оригинального README. Открыть оригинал.
Sherlog Log AI MCP
A powerful Model Context Protocol (MCP) server that provides a persistent IPython shell per session. The server only exposes a limited number of tools and at the core of it just exposes the following 2 -
call_cliexecute_python_code
And the rest of the tools are more for supporting the LLM to write the code or call the appropriate cli to complete the task. There are some tools for code retrieval based on tree sitter but thats pretty much it.
For example, installing packages or installing cli. Or doing introspection of variables in the ipython shell.
The server also supports adding external mcp servers. The idea here is you can run mcp servers inside the shell that allows you to persist results in the shell with variables and results etc.
One of the primary things I have noticed is that LLMs mess up when provided with a lot of tools and also as is quite evident by now. There are multiple articles and videos (written and shared by people way more qualified than me) and they main theme across them is the problems with tools overload and context limitation.
This server is my attempt at “solving” that problem.
How you ask ?
Note: The core of this approach is:
- All tool calls are persisted to a variable in the shell and the LLM would then write code to inspect the variable, slice/dice and get the required part out of a “gigantic” payload. My idea was similar to when us engineers work with large data we get them into dataframes and then slice/dice to get the required part out.
- CLI calls are composable and that helps the LLM to get only the required content
Both are ways of not polluting the context with useless info.
Overview
Sherlog MCP Server transforms Claude Desktop into a stateful data analysis powerhouse by providing:
- Session-Aware IPython Shells: Isolated workspaces per session with automatic persistence
- DataFrame-Centric Architecture: Every operation returns DataFrames, creating a unified data model
- Multi-Session Support: Handle up to 4 concurrent sessions with automatic lifecycle management
- MCP Proxy: Seamlessly integrates any external MCP server, executing all operations within the same IPython context
Think of it as giving Claude a persistent Python notebook that maintains separate workspaces for different conversations, where every piece of data is immediately available for the next operation.
Architecture & Design
Sherlog MCP Server supports different deployment scenarios through specialized Docker containers:
Container Variants
Vanilla Container
A lightweight, general-purpose environment optimized for data analysis and development workflows.
Pre-installed Tools:
- GitHub CLI (
gh) - Complete GitHub integration for repository management, issues, PRs, and workflows - Python Ecosystem - Full scientific computing stack (pandas, numpy, matplotlib, etc.)
Установка
npx -y @modelcontextprotocol/server-filesystem /tmp