SuperAPI AI Directory
Partner with us中文AI newsFavorites
All toolsAI developer platformszin-mcp-client

zin-mcp-client

Lightweight, Fast, Simple, CLI-Based MCP Client for STDIO MCP Servers, to fill the gap and provide bridge between your local LLMs running Ollama and MCP Servers. Specially crafted for Zin MCP Servers for reverse engineering.

Open website

About this tool

Purpose

zin-mcp-client is a lightweight, fast, and simple cross-platform MCP client used to bridge STDIO-type MCP servers and locally running Ollama large language models, filling the connection gap between local LLMs and MCP servers. It was originally built for the reverse engineering MCP servers developed by the author (the Zin MCP suite, such as APKTool-MCP-Server and JADX-MCP-Server), and it also supports other MCP servers.

Main Capabilities

  • Multi-server support: can connect to multiple MCP servers at the same time.
  • Local LLM integration: use local models through Ollama for privacy and control.
  • Interactive CLI: a clear and intuitive interface with rich formatted output.
  • Lightweight Web UI: a simple, minimalist web interface.
  • Open Web UI integration: plug and play with Open Web UI, gaining its rich features through the MCP client.
  • Comprehensive logging: provides detailed logs for debugging and troubleshooting.
  • ReAct agent framework: uses LangChain's ReAct agent pattern to intelligently invoke tools.
  • Cross-platform support.
  • Simple, fast, lightweight.

Usage

  1. Download from the Releases page:https://github.com/zinja-coder/zin-mcp-client/releases
  2. Complete the Ollama setup.
  3. Configuration file setup: the configuration file is used to tell zin mcp client how to start the MCP server, in the same style as Claude's configuration file. The default location is mcp-config.json in the zin-mcp-client directory, and a custom path can also be specified with the --config option. In the example configuration, replace path/to/uv with the actual path to the uv executable, and replace path/to/jadx-mcp-server with the absolute path to jadx-mcp-server.
  4. Run zin_mcp_client.py: you can use --server to specify the server, --config to specify the configuration file path, --model to specify the model, and --debug to enable verbose output.
  5. Run the Web client.
  6. Work with Open Web UI: run the MCP Proxy listening on port 8000, go to Settings -> Connection in Open Web UI to add a connection, fill in the URL of the local MCP Proxy (the API key can be anything), and then it can be used.

Applicable Scenarios

  • Invoke MCP server tools locally through Ollama models.
  • Test custom MCP servers.
  • Perform local code review to find vulnerabilities.
  • Use reverse engineering-related MCP servers (the Zin MCP suite).
  • Get a richer interactive experience through Open Web UI.

Limitations and Notes

  • The repository has been made read-only. The author stopped further development due to other projects, limited resources, better alternatives already existing, and the initial goal having been achieved, and will not continue adding features.
  • For low-spec systems, it is recommended to use only one server at a time to avoid LLM hallucinations.
  • Currently, proprietary API models (such as Anthropic's Claude) are usually stronger at tool calling; open-source models are developing rapidly, and you can look for models labeled function calling or tool use on platforms such as Hugging Face, or refer to discussions in the r/LocalLLaMA community.
  • The project has been used on Mac OS and Linux with jadx-mcp-server, Ghidra MCP Server testing.
  • The roadmap includes: integrating Open Web UI, supporting HTTP-based MCP servers, exposing the client to the network (already indirectly accomplished through Open Web UI integration), storing chats locally and providing history (already indirectly accomplished through Open Web UI integration).
  • Legal notice: This tool and the Zin MCP suite are strictly for educational, research, and ethical security assessment purposes, and are provided "as is" without any express or implied warranties. Users are responsible for ensuring that their use complies with all applicable laws, regulations, and ethical guidelines, and may only use it in authorized environments. Use for unauthorized reverse engineering, intellectual property infringement, or malicious activities is prohibited. The developers are not responsible for any damages, data loss, legal consequences, etc. caused by use or misuse.
  • License: ZIN MCP Client and related projects inherit the Apache 2.0 license.

Links

  • Project address:https://github.com/zinja-coder/zin-mcp-client
  • Issue feedback:https://github.com/zinja-coder/zin-mcp-client/issues

Related tools

Browse category