brannow/kimi-mcp-server
3.2
If you are the rightful owner of kimi-mcp-server and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to dayong@mcphub.com.
Kimi MCP Server is a Model Context Protocol server that provides Kimi AI tools for technical discussions and architectural reviews.
Tools
2
Resources
0
Prompts
0
Kimi MCP Server
Get Kimi K2's pragmatic technical perspective directly in Claude Code.
Example usage: reviews, architecture decisions, and technical discussions.
Quick Start
- Get API key: Moonshot AI or OpenRouter (free tier)
- Install:
git clone <repo> && cd kimi-mcp-server && npm run setup - Use: Open Claude Code, type
/kimior/kimi-plan
What You Get
Claude Code Tools:
/kimi- Get pragmatic perspective on technical decisions/kimi-plan- Architectural review of your technical plans
Configuration
The setup script will ask you to choose:
Option 1: Moonshot AI (Direct)
- API Key: Get yours here
- Model:
kimi-k2-0711-preview - Requires paid account
Option 2: OpenRouter (Recommended)
- API Key: Get yours here
- Model:
moonshotai/kimi-k2:free - Free tier available
Manual Setup
If you prefer to configure manually:
1. Install Dependencies
npm install
npm run build
2. Set Environment Variables
# For Moonshot AI
export KIMI_API_KEY=your_key_here
export KIMI_API_URL=https://api.moonshot.ai/v1
export KIMI_API_MODEL=kimi-k2-0711-preview
# For OpenRouter (free tier)
export KIMI_API_KEY=your_key_here
export KIMI_API_URL=https://openrouter.ai/api/v1
export KIMI_API_MODEL=moonshotai/kimi-k2:free
3. Register with Claude
# User scope (recommended)
claude mcp add --scope user kimi-server node $(pwd)/dist/server.js
# Project scope (team shared)
claude mcp add --scope project kimi-server node $(pwd)/dist/server.js
Commands
npm run setup- Interactive setup (recommended)npm run remove- Remove from Claude Codenpm run build- Build TypeScriptnpm start- Test locally
Environment Variables
Create a .env file or set environment variables:
KIMI_API_KEY=your_api_key_here # Required
KIMI_API_URL=https://api.moonshot.ai/v1 # Optional, defaults shown
KIMI_API_MODEL=kimi-k2-0711-preview # Optional, defaults shown
Use custom .env anywhere on the system:
Sideload custom env via the System KIMI_ENV_FILE variable
export KIMI_ENV_FILE=/absolute/path/to/custom/.env
Usage Examples
Code Review
/kimi Should we use React Context or Redux for state management in a small app?
Architecture Review
/kimi-plan
We're building a microservices architecture:
- API Gateway (Kong)
- Auth Service (JWT)
- User Service (Node.js + PostgreSQL)
- Notification Service (Redis + WebSockets)
Troubleshooting
API key not working?
- Verify key at your provider's console
- Check environment:
echo $KIMI_API_KEY
Commands not showing up?
- Restart Claude Code
- Check registration:
claude mcp list - Re-run setup:
npm run setup
Setup fails?
- Ensure Node.js 18+:
node --version - Install Claude CLI if missing
- Check permissions in project directory
Development
Project Structure
src/
├── config/
│ ├── defaults.ts # Default configuration
│ └── env.ts # Environment loading
├── tools/
│ ├── kimi-argue.ts # Technical discussion
│ └── kimi-review-plan.ts # Architecture review
└── server.ts # Main MCP server
scripts/
├── setup.js # Interactive setup
└── remove.js # Removal script
Adding Tools
- Create
src/tools/my-tool.ts - Add to
server.tstools list - Run
npm run build - Test with
npm start
Reset Everything
npm run remove # Remove from Claude
rm -rf dist/ .env # Clean files
npm run setup # Fresh start
Need help?