jurasofish/mcpunk

Chat with your codebase without embeddings by giving the LLM tools to search your code intelligently.
MCPunk lets you explore and understand codebases through conversation. It works by:
1. Breaking files into logical chunks (functions, classes, markdown sections)
2. Giving the LLM tools to search and query these chunks
3. Letting the LLM find the specific code it needs to answer your questions
No embeddings, no complex configuration - just clear, auditable searching that you can see and guide.
It works great with Claude Desktop, or any other MCP client.
GitHub Repository
Built with the following in mind
Context is King - LLMs can be great but only if provided with appropriate context.
Context is Precious - LLMs need context, but they can't handle too much.
A travesty! MCPunk is RAG that inherently provides the LLM contextual
hints, allowing the LLM to really narrow in on only the relevant content.
Human in the Loop - You can see exactly what data the LLM has considered
and how it found it, You can jump into chat and direct things wherever you want.
# Setup
These are instructions for Claude Desktop, but MCPunk can be used anywhere MCP is used.
1. Install uv
1. Put the snippet below in your claudedesktopconfig.json
(Details about claudedesktopconfig.json including location)
1. Restart Claude Desktop and you should see the tools available after a small
delay, like the screengrab below
1. Chat away: "hey pal can you set up the ~/git/mcpunk project and tell me how python files are chunked"
("command": "uvx", might not work, and you may need to use e.g. "command": "/Users/michael/.local/bin/uvx",)
json
"mcpServers": {
"MCPunk": {
"command": "uvx",
"args": ["mcpunk"]
# Usage Examples
### Answer Questions About Your Codebase
[User] Hey pal can you please set up the ~/git/mcpunk repo, then help me
understand how a user of mcpunk would get the git diff of the currently
checked out branch in the repo that they have configured with mcpunk
[Claude] Call configureproject
[Claude] Call listallfilesinproject
[Claude] Call findfilesbychunkcontent
[Claude] ... makes a total of 21 tool calls with MCPunk.
[Claude] Now I understand how the git diff functionality works in mcpunk.
Let me summarize how a user would get the git diff of the currently checked out branch:
To get a git diff of the currently checked out branch in a repo configured with mcpunk:
1. First, the user needs to configure mcpunk to work with their project by using the configureproject tool
2. To see what branches were recently checked out (to identify what to diff against)
3. Then, to get the diff between the current branch (HEAD) and a reference branch
This will display the differences between the current branch (HEAD) and the specified reference branch.
The ref parameter should be the name of the base branch (like "main" or "develop") that you want to compare against.
[User] Great job pal!
### PR Review
[user] Hey pal can you please set up the ~/git/mcpunk repo and have a
look at the current branch versus scratch/1.5
[Claude] Sets up ~/git/mcpunk and calls diffwithref for ref scratch/1.5
[Claude] I see you've made several changes, primarily adding a new test
file tests/testgitanalysis.py...