Claude Parallel Tasks MCP Server
# Claude Parallel Tasks MCP Server
An MCP (Model Context Protocol) server that enables running multiple Claude prompts in parallel, with optional file contexts and output redirection.
## Features
- Run multiple Claude prompts simultaneously in parallel
- Provide file contexts to Claude prompts
- Redirect output to individual files for each task
- Built with TypeScript and the MCP SDK
## Prerequisites
- Node.js and pnpm
- Claude CLI tool installed and configured
- Anthropic API key
## Setup
1. Clone the repository:
```bash
git clone https://github.com/CaptainCrouton89/claude-code-mcp.git
cd claude-code-mcp
```
2. Install dependencies:
```bash
pnpm install
```
3. Set up your environment variables:
```bash
cp .env.example .env.local
```
4. Edit `.env.local` and add your Anthropic API key:
```
ANTHROPIC_API_KEY=your_anthropic_api_key_here
```
5. Build the project:
```bash
pnpm run build
```
## Usage
### Running the Server
```bash
pnpm start
```
### Configuring with Claude Desktop
Add the following to your `claude_desktop_config.json`:
```json
{
"mcpServers": {
"claude-parallel": {
"command": "node",
"args": ["/path/to/claude-code-mcp/dist/index.js"],
"env": {
"ANTHROPIC_API_KEY": "your_anthropic_api_key_here"
}
}
}
}
```
### Available Tools
#### run_parallel_claude_tasks
Runs multiple Claude prompts in parallel with optional file contexts.
**Parameters:**
- `queries`: Array of query objects, each containing:
- `queryText`: The text prompt to send to Claude
- `contextFilePaths` (optional): Array of file paths to provide as context
**Example:**
```json
{
"queries": [
{
"queryText": "Explain this code",
"contextFilePaths": ["src/index.ts"]
},
{
"queryText": "Write a summary of this project",
"contextFilePaths": ["README.md", "package.json"]
}
]
}
```
## Development
```bash
# Install dependencies
pnpm install
# Build the project
pnpm run build
# Run in development mode
pnpm run dev
```
## Security
- API keys are stored in environment variables, not in code
- The `.env.local` file is gitignored to prevent accidental commits
- Use the provided `.env.example` as a template
## License
MIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap with other tools, making disambiguation perfect. The tool's purpose is clearly defined and distinct by default.
The single tool name follows a clear verb_noun pattern (run_parallel_claude_tasks), and with no other tools to compare, consistency is inherently perfect. There are no deviations or mixed conventions.
A single tool is too few for a server named 'Claude Parallel Tasks MCP Server', which suggests a broader scope for managing parallel tasks. This minimal set feels thin and underdeveloped for the implied functionality.
The server lacks essential operations for a parallel tasks domain, such as listing, monitoring, canceling, or retrieving results of tasks. With only a run tool, the surface is severely incomplete and will likely cause agent failures in managing task lifecycles.