Zin MCP Client

MCP搜索检索

提供方 zinja-coder

搜索检索 未标注 无需鉴权 社区 / 第三方

MCP Client which serves as bridge between mcp servers and local LLMs running on Ollama, Created for MCP Servers Developed by Me, However other MCP Servers may run as well

一句话选型结论

按资料字段整理

Zin MCP Client 属于搜索检索类 MCP 服务器,传输方式未标注,无需鉴权,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类搜索检索 传输方式未标注 鉴权无需鉴权 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

搜索检索
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

适用场景

research-and-datapythonaimcpcli-appethical-hacking-toolsvaptcybersecurity-tools

安装与配置

未标注 无需鉴权
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
联网搜索取证

让模型查最新资料并给出出处。

资料聚合

把一个主题的网页、文档集中抓回来整理。

情报与竞品检索

按关键词持续检索行业动态和竞品信息。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在搜索检索场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Zin MCP Client当前 未标注 未标注 未标注 无 2026-05-18
Brave Search 433812ff 2 未标注 未标注 无 2026-05-17
Sequentialthinking 1 SSE · 服务端推送 远程部署 有 2026-05-18
Baidu Netdisk 未标注 未标注 未标注 无 2026-05-17
ragflow 未标注 stdio · 本地进程 本地部署 有 2026-04-11
mindsdb (430e18) 未标注 未标注 未标注 有 2026-05-17

服务器档案

搜索检索
字段来自项目仓库与公开索引,中文说明由本站标注
提供方zinja-coder上游标注的维护方 zinja-coder
分类搜索检索本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验2026-05-18上游最后核验时间

详细介绍

11.7 KB
来自项目仓库与上游目录的原文,未做删改

Archive note:

First of all thanks to everyone who supported this project. But I have to make it Read-Only and drop future developments due to below mentioned reasons:
- Other Projects: I have to work on the other projects which are much more usefull
- Resource Limitation: Due to limited time and resources, I am not able to add more features in it
- Better Alternatives: Even if I work on this project and add many more features, the end result will not make sesnse as such features related to MCP client and all is already implemented in other alternatives, So I want to spend that time into other projects such Jadx AI MCP
- Goal Achieved: The initial goal for this project is to make cli based lightweight MCP Client so I can test my MCP Servers. Adding more features will just make it something it is not intended to become. For example, the web ui update that I implemented but they are out of place as there already exist much better alternatives.

ZIN-MCP-CLIENT (Part of Zin's MCP Suite)

⚡ Lightweight, Fast, Simple, Cross Platform, CLI, Web UI and Open Web UI based MCP Client for STDIO MCP Servers, to fill the gap and provide bridge between your local LLMs running Ollama and MCP Servers.

Image generated using AI tools.


🤖 What is ZIN MCP Client?

A powerful yet lightweight, fast, simple and flexible client for interacting with MCP (Model Context Protocol) servers through local LLMs. This tool allows you to connect to and utilize various tools from multiple MCP servers through an easy-to-use command-line interface.

Watch the demos!

  • Rich CLI interaction

https://github.com/user-attachments/assets/fad3d994-8113-47df-b10c-54541a5c3aec

  • Perform Code Review to Find Vulnerabilities locally

https://github.com/user-attachments/assets/4cd26715-b5e6-4b4b-95e4-054de6789f42

  • Plug n Play support for Open Web UI

https://github.com/user-attachments/assets/94e1ff33-0c88-40a8-8447-d9c3278a1d50

  • Supports Multiple Servers - GhidraMCP Server

https://github.com/user-attachments/assets/759f7138-1cc5-400f-b7e2-a6a7f0dca894

  • Light Weight Web UI

https://github.com/user-attachments/assets/704c214b-0ebb-4da9-971c-5f04446e9646

Features

  • Multi-Server Support: Connect to multiple MCP servers simultaneously
  • Local LLM Integration: Use local LLMs via Ollama for privacy and control
  • Interactive CLI: Clean, intuitive command-line interface with rich formatting
  • Minimal Light Weight Web UI: Clean, minimal, lightweight web ui for ease of use
  • Open Web UI Integration: Plug n Play integration with Open Web UI to get rich features of Open Web UI with strong MCP Client
  • Comprehensive Logging: Detailed logs for debugging and troubleshooting
  • ReAct Agent Framework: Utilizes LangChain's ReAct agent pattern to intelligently invoke tools
  • Cross Platform: Cross Platform Support
  • Simple, Fast, Lightweight: It is simple, it is fast, it is lightweight

Check the Zin MCP Suite

> [!NOTE]
>
> This project is in active development. Expect breaking changes with releases. Review the release changelog before updating.
>
> This project is primarily built to used with local llm for personal small scale use only. Exposing this on network may pose security risk and thus not encouraged.
>
> This project is mainly developed for Zin MCP Servers which are below mentioned MCP Servers, But support for other MCP Servers is there and testing is also done on other MCP Servers such as Ghidra

  • APKTool-MCP-Server
  • JADX-MCP-Server

🛠️ Getting Started

1. Downlaod from Releases: https://github.com/zinja-coder/zin-mcp-client/releases```bash

1.

unzip zin-mcp-client-<version>.zip

├zin-mcp-client/
├── zin_mcp_client.py
├── web_client.py
├── mcp_proxy.py
├── static/
├── src/
├── mcp-config.json
├── README.md
├── LICENSE

2. Navigate to zin-mcp-client directory

cd zin-mcp-client

3. This project uses uv (recommended) - https://github.com/astral-sh/uv instead of pip for dependency management.

## a. Install uv (if you dont have it yet) - (Only Required Step)

curl -LsSf https://astral.sh/uv/install.sh | sh

All below steps are not required.

## b. OPTIONAL, if for any reasons, you get dependecy errors in jadx-mcp-server, Set up the environment

uv venv
source .venv/bin/activate # or .venv\Scripts\activate on Windows
## c. OPTIONAL Install dependencies
uv pip install -r requirements.txt

4. Not recommended, you can also use pip for this.

pip install -r requirements.txt
or
pip install -r requirements.txt --break-system-packages

The setup for zin-mcp-client is done.


## 🤖 2. Ollama Setup```bash
1. Download and Install ollama: https://ollama.com/download

If you are on linux you can directly run below command to install it:

&gt; curl -fsSL https://ollama.com/install.sh | sh

2. Download and run any LLM that has capability to invoke tool.

For example, the llama 3.1 has capability to invoke the tool.

You can run it using following command:

&gt; ollama run llama3.1:8b

[Note]: Kindly note the above command will fetch the model with 4b parameters. If you have stronger hardware kindly fetch higher parameter model for better performance.

3. Serve the Ollama on API server using following command

&gt; ollama serve

This will serve the ollama api on port 1134, you can confirm that it running using `curl` command as following:

&gt; curl http://localhost:11434/                                                                                                                                              18:54:00
`Ollama is running`

⚙️ 3. Config File Setup

The config file is the MCP Server configuration file that tells zin mcp client how to start the MCP Servers.

It follows the same style as Claude's configuration file.

Below is the sample configuration file for Zin MCP Suite Servers:```json
{
"mcpServers": {
"jadx-mcp-server": {
"command": "/path/to/uv",
"args": [
"--directory",
"/path/to/jadx-mcp-server/",
"run",
"jadx_mcp_server.py"
]
},
"apktool-mcp-server": {
"command": "/path/to/uv",
"args": [
"--directory",
"/path/to/apktool-mcp-server/",
"run",
"apktool_mcp_server.py"
]
}
}
}


Replace:

- `path/to/uv` with the actual path to your `uv` executable
- `path/to/jadx-mcp-server` with the absolute path to where you have stored the jadx-mcp-server

&gt; [!NOTE]
&gt;
&gt;  The default location of config file is inside zin-mcp-client directory named `mcp-config.json`, however you can provide path to your own config file using `--config` option such as```bash
uv run zin_mcp_client.py --server jadx-mcp-server --model llama3.1:8b --config /home/zinjacoder/mcp-config.json

Give it a shot

  1. Run zin_mcp_client.py```bash
    uv run zin_mcp_client.py

2. Use `--server` option to specify server of your choice, use `--config` option to provide path to your config file, use `--model` option to use specific model, use `--debug` to enable verbose output

## If something went wrong - DEBUG and Troubleshooting

&gt; [!NOTE]
&gt;
&gt;  For low spec systems, use only one server at a time to avoid LLM hallucinations.

1. Look the logs:

- All the logs and debug information and raw traffic and interactions are stored in logs in easy to read way, If anything goes wrong check the logs.

2. Debug Mode:

- You can also use the `--debug` flag to enable debug to print each and every detail on console on runtime to help you find the issue.

https://github.com/user-attachments/assets/ee478917-c4f5-46fb-9f0e-ad31d7c33ee0

3. Open Issue:

- If you can not resolve the error on you own, use the logs and debug mode&#x27;s output and provide them to us by opening an issue at https://github.com/zinja-coder/zin-mcp-client/issues

## Web Client
1. Done configuration mentioned above
2. Run web client using following:```bash
uv run web_client.py
  1. Demo of the web client is shown in video at top

Setting up with Open Web UI

  1. Done configuration mentioned above.
  2. Run the MCP Proxy using following:bash uv run mcp_proxy.py

  3. Go to Open Web Ui portal.

  4. In Open Web UI -> Settings -> Connection -> add new connection as shown in below image

Add the URL for MCP Proxy running on port 8000 with localhost if running locally as shown in image. You can put anything in API key.

  1. Now prompt and utilize the MCP client, Plug n Play setup.

Current State Of Local LLM and MCPs:

Currently, proprietary API-based models like Anthropic’s Claude tend to be more proficient proficient at tool calling.

However, the open-source world is advancing rapidly! Models specifically fine-tuned on function calling datasets are becoming increasingly available through Ollama. Researching models tagged with function calling or tool use on platforms like Hugging Face or checking discussions on communities like r/LocalLLaMA is key to finding capable local options.


🛣️ Future Roadmap

  • [x] Web UI

  • [x] Integrate with Open Web UI

  • [x] Add Support HTTP based MCP Servers - Because a lot servers provide a way to make their servers act as a STDIO based.

  • [x] Add support exposing this client on network as well, Indirectly for network access - done indirectly via open web ui integration

  • [x] Store chat locally and provide chat history - done indirectly via open web ui integration

  • [ ] END-GOAL : Make all reverse engineering MCP Servers, bring them together, to make reverse engineering as easy as possible purely from vibes.

To report bugs, issues, feature suggestion, Performance issue, general question, Documentation issue.

  • Kindly open an issue with respective template.

  • Tested on Mac OS and Linux environment with jadx-mcp-server, Ghidra MCP Server

🙏 Credits

This project is a possible due to ollama, an amazing utility to rung local LLMs. The langchain project,

And in last thanks to @anthropics for developing the Model Context Protocol and @FastMCP team.

Apart from this, huge thanks to all open source projects which serve as a dependencies for this project and which made this possible.

📄 License

ZIN MCP Client and all related projects inherits the Apache 2.0 License.

⚖️ Legal Warning

Disclaimer

The tools zin-mcp-client and zin mcp suite are intended strictly for educational, research, and ethical security assessment purposes. They are provided "as-is" without any warranties, expressed or implied. Users are solely responsible for ensuring that their use of these tools complies with all applicable laws, regulations, and ethical guidelines.

By using zin-mcp-client or zin mcp suite, you agree to use them only in environments you are authorized to test, such as applications you own or have explicit permission to analyze. Any misuse of these tools for unauthorized reverse engineering, infringement of intellectual property rights, or malicious activity is strictly prohibited.

The developers of zin-mcp-client and zin mcp suite shall not be held liable for any damage, data loss, legal consequences, or other consequences resulting from the use or misuse of these tools. Users assume full responsibility for their actions and any impact caused by their usage.

Use responsibly. Respect intellectual property. Follow ethical hacking practices.


🙌 Contribute or Support

  • Found it useful? Give it a ⭐️
  • Got ideas? Open an issue or submit a PR
  • Built something on top? DM me or mention me — I’ll add it to the README!
  • Do you like my work and keep it going? Sponsor this project.

Built with ❤️ for the reverse engineering and AI communities and all the awesome hackers and open source contributors around the world.

常见问题

5 问
答案由本站依据条目字段整理,不引用上游原文
Zin MCP Client 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Zin MCP Client 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

Zin MCP Client 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Zin MCP Client 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

Zin MCP Client 能提供哪些能力?

资料显示能力标签包括 Python、搜索、文档处理。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-18。