Package Exports
- @pcircle/claude-code-buddy-mcp
- @pcircle/claude-code-buddy-mcp/dist/index.js
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@pcircle/claude-code-buddy-mcp) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
π§ Claude Code Buddy (CCB)
The Only MCP Server That Remembers
Make Claude Code remember everything. Build faster. Vibe harder.
π Quick Start β’ π Docs β’ π Website β’ π¬ Discussions
π₯ See It In Action (Interactive Demo)
π΄ Without CCB# Session 1 (Monday)
You: "We use JWT for auth because..."
Claude: "Got it! β
"
# Session 2 (Tuesday)
You: "Remember our auth approach?"
Claude: "Sorry, I don't have context..."
You: *explains everything again* π€
# Session 3 (Wednesday)
You: "Our JWT implementation..."
Claude: "What JWT implementation?"
You: *RAGE QUITS* π’ |
β With CCB# Session 1 (Monday)
You: buddy-do "setup JWT auth"
CCB: β
Implemented + Saved to memory
# Session 2 (Tuesday)
You: buddy-remember "auth"
CCB: π "JWT auth implemented on 2024-01-15
β³ Access tokens: 15min
β³ Refresh tokens: 7 days
β³ Secret rotation: monthly"
# Session 3 (Any day, forever)
You: buddy-do "add OAuth"
CCB: π§ "I see you have JWT. Let's
integrate OAuth alongside it..." |
π‘ Try it yourself:
# In Claude Code/Cursor
buddy-help # See all commands
buddy-do "explain how CCB works" # Watch it intelligently respond
buddy-remember "project decisions" # Query your project memoryπ Read User Guide β’ π§ API Reference
π€ The Problem
You know this pain:
Session 1: "Let me explain our architecture..."
Session 2: "As I mentioned before, our architecture..."
Session 3: "Like I said earlier, our architecture..."
Session 4: π€Every. Single. Session.
β¨ The Solution
β Before CCB
|
β After CCB
|
π― Core Features
1. π§ Project Memory That Actually Works
# Session 1 (Last week)
You: "We chose PostgreSQL for JSONB support"
# Session 42 (Today)
You: buddy-remember "why PostgreSQL?"
CCB: "Based on your decision from 2024-01-15: PostgreSQL was
chosen for JSONB support and advanced query capabilities..."Claude remembers. Forever.
2. π― Smart Task Routing (Autopilot Mode)
You: "Review this code"
CCB: *Detects task type*
*Activates code review mode*
*Applies best practices*
*Delivers structured review*No more "how should I do this?" Just do it.
3. π¬ Dead Simple Commands
buddy-do "setup authentication" # Execute any dev task
buddy-remember "API design" # Query project memory
buddy-help # When stuckThree commands. Infinite possibilities.
π 2-Minute Quick Start
Step 1: Install (Choose Your IDE)
π― Cursor Users (Click to expand)
Just click this magic link:
cursor://anysphere.cursor-deeplink/mcp/install?name=@pcircle/claude-code-buddy-mcp&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIkBwY2lyY2xlL2NsYXVkZS1jb2RlLWJ1ZGR5LW1jcCJdfQ==Done. Restart Cursor and you're ready.
β‘ Claude Code Users (Click to expand)
Add this to ~/.claude/mcp_settings.json:
{
"mcpServers": {
"@pcircle/claude-code-buddy-mcp": {
"command": "npx",
"args": ["-y", "@pcircle/claude-code-buddy-mcp"]
}
}
}Restart Claude Code and you're golden.
Step 2: Test It
# In Claude Code/Cursor, type:
buddy-help
# You should see CCB's command list
# Now try:
buddy-do "explain CCB features"
# Watch the magic happen β¨π That's it! You're vibing now.
π Need help? Detailed installation guide | Troubleshooting
π‘ Real-World Usage
Scenario 1: Building a New Feature
You: buddy-do "create a real-time chat with WebSocket"
CCB analyzes your project...
π Detected: React + Node.js + Express
π§ Recalled: Your preference for TypeScript strict mode
π Applying: Error boundaries pattern from LoginPage.tsx
β
Generated:
ββ server/chat.ts (WebSocket server)
ββ components/ChatWindow.tsx (React component)
ββ hooks/useWebSocket.ts (Custom hook)
πΎ Saved to memory: "WebSocket chat architecture - 2024-01-20"Scenario 2: "Wait, Why Did We Do That?"
You: buddy-remember "authentication approach"
CCB searches knowledge graph...
π Found 3 related memories:
ββ 2024-01-15: Initial Auth Decision
β π¬ "JWT chosen over sessions for stateless API"
β β‘ Reasoning: Mobile app compatibility
β
ββ 2024-01-18: Token Expiry Implementation
β π» Code: auth/middleware.ts:42-67
β π§ Access: 15min | Refresh: 7 days
β
ββ 2024-01-22: Security Enhancement
π‘οΈ Added: Rate limiting + Token rotation
π Prevented: Token reuse vulnerabilityScenario 3: Continuous Development Flow
Day 1 β You: "Implement user login"
β CCB: β
Created + πΎ Remembered
β
Day 5 β You: "Add password reset"
β CCB: π§ "I see you use JWT tokens..."
β β
Integrated seamlessly
β
Day 10β You: "Add OAuth support"
β CCB: π§ "Based on your JWT + password reset..."
β β
Consistent with existing auth
β
Week 8β You: "Why did we choose JWT again?"
β CCB: π *Instant recall from Day 1*No context re-explanation. Ever again.
π Why CCB vs. Others?
| Feature | Plain Claude Code | Other MCP Tools | CCB |
|---|---|---|---|
| Persistent Memory | β | β οΈ Basic | β Full Knowledge Graph |
| Smart Routing | β | β | β Auto-detects task type |
| Vibe Coding Optimized | β οΈ | β | β Built for it |
| Zero Setup | β | β οΈ Complex | β 2 minutes |
| Free & Open Source | β | β οΈ Varies | β AGPL-3.0 |
π οΈ Advanced Features
Auto-Memory System
When you use buddy-do, CCB automatically records:
- β Task goals and outcomes
- β Technical decisions and reasoning
- β Errors encountered and solutions
- β Development milestones
You don't think about memory. CCB does.
Multi-Project Support
Each project gets its own isolated memory space.
cd ~/project-A
buddy-remember "auth" # Returns project-A's auth decisions
cd ~/project-B
buddy-remember "auth" # Returns project-B's auth decisionsNo cross-contamination. Ever.
17 MCP Standard Tools
Full integration with Model Context Protocol.
See complete list: ToolDefinitions.ts
π§ͺ Technical Details
Requirements
|
Platform Support
|
π Security First
- β 100% Local Processing - Your data never leaves your machine
- β No External API Calls - Uses your Claude Code subscription
- β npm audit: 0 vulnerabilities
- β Open Source - Audit the code yourself
π€ Contributing
We'd love your help making CCB better!
- π Found a bug? Open an issue
- π‘ Have an idea? Start a discussion
- π οΈ Want to code? Check Good First Issues
Contributing Guide: CONTRIBUTING.md
π Documentation
- π Full Documentation
- π Quick Install Guide
- π User Guide
- π οΈ API Reference
- β Troubleshooting
β FAQ
Q: Does it cost money?
A: Nope. 100% free and open source (AGPL-3.0). Uses your existing Claude Code subscription.
Q: Is my data safe?
A: Yes. Everything processed locally. Zero external API calls. Zero data upload.
Q: How is this different from plain Claude Code?
A: CCB adds two superpowers:
- Persistent Memory - Claude remembers your project across sessions
- Smart Routing - Automatically detects and handles different task types
Think of it as Claude Code + a really good memory + autopilot mode.
Q: Can I customize it?
A: Absolutely. Prompt templates in src/core/PromptEnhancer.ts.
Want deeper customization? Fork it, hack it, make it yours. That's the open source way.
Q: Does it work with Cursor?
A: Yes! Cursor has native MCP support. One-click install.
π Acknowledgments
Built on the shoulders of giants:
- Model Context Protocol (MCP) - The foundation
- Claude Code - The platform
- All our amazing contributors and early testers
π License
AGPL-3.0 - See LICENSE
This means: Use it, modify it, share it. But keep it open source.
π Star History
Built by developers, for developers
Stop repeating yourself. Start vibing.
π Get Started β’ π Read the Docs β’ π¬ Join the Discussion
β If CCB saved you time today, give it a star!
It helps others discover this tool.
Not affiliated with Anthropic PBC β’ Independent open-source project
Languages: English β’ ηΉι«δΈζ