@agiflowai/powertool
MCP Proxy Server for Claude Code and marketplace plugins. Aggregates multiple MCP servers with built-in project management prompts.
When to Use
Use @agiflowai/powertool when:
- ✓Using Claude Code with MCP servers
- ✓Installing marketplace plugins
- ✓Aggregating multiple MCP servers
- ✓Using built-in project management prompts
Use @agiflowai/agent-cli when:
- ✓Running agents with daemon mode
- ✓Remote agent management
- ✓Persistent agent connections
- ✓Team collaboration workflows
Installation
Quick Start
1. Get Your Configuration from Agiflow
- •Sign up at agiflow.io
- •Create a new project in the dashboard
- •Follow the setup wizard to generate your MCP configuration
- •Copy your project endpoint URL and API key
2. Add to Claude Code
Add to your .mcp.json:
{
"mcpServers": {
"agiflow": {
"command": "npx",
"args": ["-y", "@agiflowai/powertool", "mcp-serve"],
"env": {
"AGIFLOW_MCP_PROXY_ENDPOINT": "https://agiflow.io/api/v1/projects/your-project-id/mcp-configs",
"AGIFLOW_MCP_API_KEY": "your-generated-api-key"
}
}
}
}Configuration Methods
The proxy server supports three configuration methods (in order of precedence):
Method 1: Environment Variables (Recommended for CI/CD)
Get your endpoint and API key from the Agiflow dashboard setup wizard:
Method 2: Saved Credentials (Recommended for Development)
Simply run the command without configuration. The CLI will prompt for authentication and save credentials:
Credentials are saved per project directory and automatically loaded on subsequent runs.
Method 3: Local Configuration File (For Testing)
Use a local JSON configuration file:
Built-in Prompts
Powertool includes built-in prompts for project management workflows with LiquidJS template rendering and 14 custom filters.
PlanPrompt
Break down project requirements into structured tasks and work units with automatic task dependency detection.
TaskPrompt
Implement single tasks with progress tracking, validation, and automated status updates.
WorkPrompt
Execute work units (features/epics) with multiple tasks, handling sequential task implementation.
CompletePrompt
Complete tasks with automated validation checks, test execution, and completion criteria verification.
Template Filters
All prompts support LiquidJS template syntax with these custom filters:
camelCasepascalCasekebabCasesnakeCaseupperCasepluralizesingularizestriplowerupperMCP Proxy Capabilities
Multi-Server Proxy
Connect to and proxy multiple MCP servers (stdio, HTTP, SSE) with automatic connection pooling and lifecycle management.
Tool Aggregation
Aggregate tools from all connected servers with automatic namespacing to avoid conflicts. Tools are accessible as serverName/toolName.
Resource & Prompt Proxying
Proxy resources and prompts from all connected servers. Resources are prefixed as serverName://resourceUri.
Remote Configuration
Fetch MCP server configurations from Agiflow hosted at agiflow.io with automatic caching and updates.
Command Options
-t, --typeTransport type: stdio, http, or sse (default: stdio)-p, --portPort to listen on for HTTP/SSE (default: 3000)--hostHost to bind to for HTTP/SSE (default: localhost)-f, --config-filePath to local MCP configuration JSON fileTroubleshooting
Connection Issues
If you're having trouble connecting to Agiflow:
- •Verify your endpoint URL and API key are correct
- •Check your internet connection
- •Ensure you're using the latest version:
npm update -g @agiflowai/powertool - •Check saved credentials:
cat ~/.agiflow/mcp.credentials.json
MCP Server Connection Errors
If specific MCP servers fail to connect:
- •Verify the MCP server configuration in Agiflow dashboard
- •Check that the MCP server is running and accessible
- •Review server logs for specific error messages
- •Test the MCP server independently without the proxy
Permission Errors
If you encounter permission errors during installation:
Debug Mode
Enable verbose logging for debugging:
API Reference
Complete Command Reference
For a complete list of all commands and options, use the built-in help: