LLM 툴을 제공하여 코드를 지능적으로 검색할 수 없는 코드베이스와 채팅.

MCPunk는 대화를 통해 코드베이스를 탐색하고 이해합니다. 그것은에 의해 작동:

1. 논리 펑크로 파일 파괴 (기능, 클래스, 마크 다운 섹션)
2. LLM 도구를 사용하여 이러한 펑크를 검색하고 쿼리하십시오.
3. LLM은 특정 코드를 찾을 수 있도록 귀하의 질문에 대답해야합니다

embeddings 없음, 복잡한 구성 없음 - 그냥 명확하고, 당신이 볼 수 있는 감사 검색 및 가이드. Claude Desktop 또는 다른 MCP 클라이언트와 함께 훌륭합니다.

GitHub 저장소

본문 바로가기

-Context는 King입니다. - LLM은 적절한 상황에만 제공될 수 있습니다. -Context는 Precious - LLMs는 컨텍스트가 필요하지만, 너무 많이 처리할 수 없습니다. 한국어 MCPunk는 LLM 컨텍스트를 제공하는 RAG입니다. 힌트는 LLM을 사용하여 관련 콘텐츠에만 실제로 좁습니다.

• ** 루프에서 인간 ** - ** 당신은 정확하게 LLM이 고려한 데이터를 볼 수 있습니다 그리고 어떻게 그것을 발견, 당신은 당신이 원하는 채팅 및 직접 물건으로 점프 할 수 있습니다.

설치

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
2. Put the snippet below in your claude_desktop_config.json (Details about claude_desktop_config.json including location)
3. Restart Claude Desktop and you should see the tools available after a small delay, like the screengrab below
4. 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",)

{
  "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 configure_project
• [Claude] Call list_all_files_in_project
• [Claude] Call find_files_by_chunk_content
• [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: