open-index/open-npm huggingface dataset:
npm package: @iflow-mcp/cerebras-cerebras-code-mcp
Description: Model Context Protocol (MCP) server for Cerebras Code API integration with any MCP-compatible client. Run 'cerebras-mcp --config' for setup or 'cerebras-mcp --remove' for cleanup.
Author: Kevin Taylor
Latest version: 1.3.4

# Cerebras Code MCP Server v1.3.3

This MCP server is designed for **planning with Claude Code, Cline, or Cursor** and **making changes with Cerebras** to maximize speed and intelligence while avoiding API limits. Use your preferred AI for planning and strategy, then leverage Cerebras for high-quality code generation.

It will use the Qwen 3 Coder model, and can be embedded in IDEs like Claude Code and Cline, with beta support for Cursor.

## ✨ New in v1.3.3

- **Project Restructure**: Organized project into smaller, more manageable components for DX purposes
- **Stronger Instruction**: Improved `write` usage count among models
- **Claude Code - Enhanced Visual Diffs**: Displays changes/edits in a pretty format
- **VS Code Support**: Added install/remove support for VS Code
- **Update Config Wizard for Messy Configs**: Added a removal wizard that helps uninstall

## 1. Install the NPM Package
```bash
npm install -g cerebras-code-mcp
```

## 2. Get Cerebras API key
Visit [cloud.cerebras.ai](https://cloud.cerebras.ai) and create an API key

[OPTIONAL] Add OpenRouter as a backup in case you hit your Cerebras rate limits
Visit [OpenRouter](https://openrouter.ai/) and get a key to use as a fallback provider.

You can set this key in your MCP settings under OPENROUTER_API_KEY, and it will trigger automatically if anything goes wrong with calling Cerebras.


## 3. Run the Setup Wizard for Claude Code / Cursor / Cline / VS Code (Copilot)
```bash
cerebras-mcp --config
```

Use the setup wizard to configure the tool on your machine.

If you're using Cursor, it will ask you to copy and paste a prompt into your Cursor User Rules.

## 4. Removal/Cleanup (Optional)
```bash
cerebras-mcp --remove
```

Use the removal wizard to clean up configurations for any IDE or perform a complete cleanup.

## 5. Usage

The MCP tool will appear as `write` in your tool list. It supports:

- **Natural language prompts**: Just describe what you want in plain English
- **Context files**: Include multiple files as context for better code understanding
- **Visual diffs**: See changes with Git-style diffs

Example usage:
```
Create a REST API with Express.js that handles user authentication
```
npm package: @iflow-mcp/ceresopa-alicization-town-bridge
Description: Soul Translator — MCP bridge connecting AI agents to Alicization Town via HTTP API
Author: ceresOPA
Latest version: 0.6.3

# Alicization Town — MCP Bridge

[🇨🇳 简体中文](./README_zh.md)

A [Model Context Protocol](https://modelcontextprotocol.io/) (MCP) server that connects AI agents to the Alicization Town pixel sandbox world. Transport: stdio.

## Setup

### Claude Desktop

Add to your `claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "alicization-town": {
      "command": "npx",
      "args": ["-y", "alicization-town-bridge"],
      "env": {
        "SERVER_URL": "http://localhost:5660",
        "BOT_NAME": "Alice",
        "BOT_SPRITE": "Princess"
      }
    }
  }
}
```

### VS Code

Add to your `.vscode/mcp.json`:

```json
{
  "servers": {
    "alicization-town": {
      "command": "npx",
      "args": ["-y", "alicization-town-bridge"],
      "env": {
        "SERVER_URL": "http://localhost:5660",
        "BOT_NAME": "Alice",
        "BOT_SPRITE": "Princess"
      }
    }
  }
}
```

### Local Development

```bash
# Start the game server first
npm run start:server

# Then start the bridge (in another terminal)
SERVER_URL=http://localhost:5660 BOT_NAME=Alice node packages/mcp-bridge/bin/bridge.js
```

## Environment Variables

| Variable | Default | Description |
|---|---|---|
| `SERVER_URL` | `http://localhost:5660` | Game server URL |
| `BOT_NAME` | `Alice` | Character name in the game |
| `BOT_SPRITE` | unset | Optional auto-join sprite (see `list_characters`) |

## Available Tools

| Tool | Type | Description |
|---|---|---|
| `login` | auth | Login or create a profile |
| `list-profile` | auth | List local profiles |
| `logout` | auth | Logout current session |
| `characters` | query | List available character sprites |
| `look` | query | Inspect nearby surroundings |
| `map` | query | Read the town map directory |
| `walk` | action | Walk to a target (auto-pathfinding) |
| `chat` | action | Speak in the town |
| `interact` | action | Interact with the current area |

## License

MIT
npm package: @iflow-mcp/cgoinglove_mcp-server-kakao-map
Description: Kakao Map MCP server
Author: cgoinglove
Latest version: 0.0.2

Kakao Map MCP Server

한국어 | [English](./docs/en.md)

카카오맵 API를 활용하여 대한민국 내 위치 기반 장소 추천을 제공하는 MCP 서버입니다. 한국어 쿼리에 최적화되어 있습니다.

![img](./docs/image.png)

## Tool: kakao_map_place_recommender

설명: 사용자 질의에 따라 대한민국 내 다양한 관련 장소(예: 식당, 상점, 공공시설, 관광명소)를 추천합니다. 카카오맵 API 키워드 검색을 사용합니다.

- `query` (필수): 장소 유형 및 위치를 설명하는 한국어 키워드. 예시: '이태원 맛집', '서울 병원', '강남역 근처 카페'.

## Configuration

### 환경 변수

- `KAKAO_API_KEY`: 카카오 API 키 (필수)

1.  **애플리케이션 등록**: [카카오 디벨로퍼스](https://developers.kakao.com/)에 로그인하고, 아직 애플리케이션이 없다면 [새로 만듭니다](https://developers.kakao.com/docs/latest/ko/getting-started/quick-start#create).
2.  **REST API 키 확인**: 애플리케이션 설정(`[내 애플리케이션] > [앱 설정] > [요약 정보]`)으로 이동합니다. 제공된 여러 키 중에서 **REST API 키**를 찾아 복사합니다. 이 도구에는 이 특정 키가 필요합니다.
3.  **카카오맵 API 활성화**: 애플리케이션에 카카오맵 API가 활성화되어 있는지 확인합니다. `[내 애플리케이션] > [카카오맵] > [활성화 설정]`으로 이동하여 `[상태]`를 `ON`으로 설정합니다. (_참고: 기존 앱에 API를 추가하는 경우, 추가적인 권한 신청 및 승인이 필요할 수 있습니다._)
4.  **참고**: 자세한 내용은 공식 문서를 참조하세요: [카카오 로컬 API 공통 가이드](https://developers.kakao.com/docs/latest/ko/local/common).
npm package: @iflow-mcp/chatgpt-mcp-server
Description: A Model Context Protocol server for Docker management through ChatGPT
Author: toowiredd
Latest version: 0.1.0

# ChatGPT MCP Server
[![smithery badge](https://smithery.ai/badge/@Toowiredd/chatgpt-mcp-server)](https://smithery.ai/server/@Toowiredd/chatgpt-mcp-server)

A Model Context Protocol (MCP) server that provides Docker management capabilities through a custom GPT interface.

## Features

- Docker container management through natural language
- Built on the Model Context Protocol (MCP)
- TypeScript implementation
- Containerized deployment
- Robust error handling and graceful shutdown
- Resource management and port handling
- Rate limiting and API key authentication

## Setup
### Installing via Smithery

To install ChatGPT MCP Server for Claude Desktop automatically via [Smithery](https://smithery.ai/server/@Toowiredd/chatgpt-mcp-server):

```bash
npx -y @smithery/cli install @Toowiredd/chatgpt-mcp-server --client claude
```

### Manual Installation
1. Clone the repository
```bash
git clone https://github.com/toowiredd/chatgpt-mcp-server.git
cd chatgpt-mcp-server
```

2. Install dependencies
```bash
npm install
```

3. Create environment file
```bash
cp env.example .env
# Edit .env with your configuration
```

4. Build the project
```bash
npm run build
```

## Running with Docker

1. Build the container
```bash
npm run docker:build
```

2. Run the container
```bash
npm run docker:run
```

Or manually:
```bash
docker run -d \
  -p 3001:3001 \
  --env-file .env \
  -v /var/run/docker.sock:/var/run/docker.sock \
  chatgpt-mcp-server
```

## Development

- `npm run build` - Build the TypeScript code
- `npm run watch` - Watch for changes and rebuild
- `npm run inspector` - Run the MCP inspector tool

## Environment Variables

- `API_KEY` - API authentication key
- `HTTP_PORT` - Server port (default: 3001)
- `RATE_LIMIT_REQUESTS` - Maximum requests per window
- `RATE_LIMIT_WINDOW` - Window size in milliseconds

## Resource Management

The server implements robust resource management:

- Graceful shutdown on process signals (SIGINT, SIGTERM, SIGQUIT)
- Connection tracking and management
- Request timeout handling
- Port conflict detection
- Keep-alive connection management
- Active request tracking and graceful completion

### Shutdown Process

1. The server initiates graceful shutdown on process signals
2. New connections are rejected
3. Active requests are allowed to complete (with timeout)
4. Keep-alive connections are closed
5. Server ports are properly released
6. Resources are properly released

### Error Handling

- Port conflicts are detected and reported
- Unhandled rejections and exceptions are caught
- Network errors are properly handled
- Resource leaks are prevented through proper handling
- Timeouts ensure the server doesn't hang during shutdown

## License

MIT