Skip to main content
Glama

MCPMan

by semistrict
GitHub
TypeScript
OverviewInspectNewEndpointsSchemaRelated ServersReviewsScore
Need Help?View Source CodeReport Issue

MCPMan

A Model Context Protocol (MCP) server manager that acts as a proxy/multiplexer for multiple MCP servers.

Overview

MCPMan allows you to:

  • Connect to multiple MCP servers simultaneously (stdio and HTTP transports)

  • Generate and execute code from natural language descriptions using LLMs

  • Execute JavaScript code with access to all connected MCP tools

  • Invoke tools from multiple servers with batch and parallel execution

  • Manage server configurations with OAuth 2.1 support

  • Dynamically add new servers without restarting

  • Store and access tool results through $results array

Quick Start

Installation

bun install

Initialize Configuration

mcpman init

Add MCP Servers

# Add stdio server mcpman add filesystem --command npx --args @modelcontextprotocol/server-filesystem # Add HTTP server with OAuth mcpman add api-server --url https://api.example.com/mcp

Generate and Execute Code from Natural Language

The code tool uses LLMs (via Claude Agent SDK or MCP sampling) to generate JavaScript code from natural language descriptions. Generated code is validated with TypeScript compiler before execution.

# Generate code from description mcpman code "list all files in the current directory" # Generate code with custom root directories mcpman code "read the package.json file and show the dependencies" --roots /path/to/project

Features:

  • Automatic Code Generation: LLM writes JavaScript code to accomplish your task

  • TypeScript Validation: Generated code is validated with TypeScript compiler API (with up to 3 retries if validation fails)

  • Type-Safe API: Generated TypeScript definitions provide autocomplete and type checking for all MCP tools

  • Server Filtering: Optional servers parameter limits which MCP servers are available to reduce context size and improve code quality

  • $results Integration: Generated code results are automatically stored in $results array

When using as an MCP tool, strongly recommend specifying the servers parameter to limit context:

// Good - limits context to only playwright tools { functionDescription: "navigate to google.com and take a screenshot", servers: ["playwright"] } // Avoid - includes all servers which may result in poor performance { functionDescription: "navigate to google.com and take a screenshot" }

Evaluate Function Expressions with MCP Tools

# Simple function with no arguments mcpman eval "() => listServers()" # Function with argument mcpman eval "(arg) => filesystem.listFiles({ path: arg.directory })" --arg '{"directory": "."}' # Specify custom root directories mcpman eval "(arg) => filesystem.listFiles({ path: arg.path })" --arg '{"path": "/tmp"}' --roots /tmp # Complex function with console output mcpman eval "(arg) => { console.log('Processing:', arg.name); return arg.value * 2; }" --arg '{"name": "test", "value": 21}'

Run as MCP Server

mcpman serve

Architecture

MCPMan operates in two modes:

Server Mode

  • Acts as an MCP server exposing multiple tools:

    • code - Generate and execute JavaScript code from natural language descriptions using LLMs with TypeScript validation

    • eval - Execute JavaScript with access to all MCP tools

    • invoke - Batch invoke tools with parallel/sequential execution

    • list_servers - List connected servers and their tools

    • help - Get documentation for specific tools

    • install - Dynamically add new servers

  • Connects to multiple upstream MCP servers

  • Transparently forwards root directory information from clients to upstream servers

  • Provides unified JavaScript execution environment with $results array

CLI Mode

  • Direct command-line interface for server management

  • Execute JavaScript code with MCP tool access

  • Configure and test server connections

Configuration

Configuration is stored in ~/.mcpman/settings.json:

{ "servers": { "filesystem": { "transport": "stdio", "command": "npx", "args": ["@modelcontextprotocol/server-filesystem"], "env": {}, "disabled": false, "timeout": 30000 }, "api-server": { "transport": "http", "url": "https://api.example.com/mcp", "headers": {}, "oauth": { "clientName": "mcpman", "redirectUrl": "http://localhost:3000/callback", "scopes": ["mcp:tools"], "clientId": "optional-client-id", "clientSecret": "optional-client-secret" }, "disabled": false, "timeout": 30000 } } }

CLI Commands

# Server management mcpman init # Initialize configuration mcpman add <name> # Add new server mcpman list # List configured servers mcpman validate # Validate configuration mcpman test # Test server connections # Execution mcpman code "description" [--roots /path] # Generate and execute code from natural language mcpman eval "function-expr" [--arg '{}'] [--roots /path] # Execute function expression with MCP tools mcpman serve # Run as MCP server # Authentication mcpman auth <server-name> # Authenticate with OAuth server

JavaScript Execution Environment

Inspired by - Instead of directly calling MCP tools, LLMs write code that interacts with a JavaScript API. This approach leverages LLMs' strength in writing code and enables more sophisticated tool chaining and composition.

In the eval environment, each configured server is available as a global object. All code must be provided as function expressions:

// No argument function - list servers () => listServers() // Function with argument - list files (arg) => filesystem.listFiles({ path: arg.directory }) // Complex function with multiple operations (arg) => { console.log("Processing directory:", arg.path); const files = filesystem.listFiles({ path: arg.path }); return files.filter(f => f.name.endsWith('.js')); } // Async function with multiple server calls async (arg) => { const servers = listServers(); console.log("Available servers:", servers); const result = await someServer.someTool({ param: arg.value }); return result; } // Access previous results via $results array () => { console.log("Previous result:", $results[0]); return $results[0]; }

$results Array

When using the eval or invoke tools as an MCP client, results are automatically stored in the $results array. Each tool invocation appends its result to this array, and you can access previous results by index:

// After calling invoke or eval, results are stored $results[0] // First result $results[1] // Second result

Batch Tool Invocation

The invoke tool allows you to call multiple MCP tools in batch mode:

// Sequential execution (stops on first error) { calls: [ { server: "filesystem", tool: "read_file", parameters: { path: "package.json" } }, { server: "filesystem", tool: "read_file", parameters: { path: "README.md" } } ], parallel: false } // Parallel execution (all tools execute concurrently) { calls: [ { server: "filesystem", tool: "list_directory", parameters: { path: "." } }, { server: "git", tool: "status", parameters: {} } ], parallel: true }

Logging

When running in server mode, MCPMan redirects console output to log files:

  • Main log: ~/.mcpman/mcpman.log - All console.log/error/warn/info output

  • Trace log: ~/.mcpman/trace.log - Detailed trace logging (requires MCPMAN_TRACE=1)

Logs use synchronous writes to ensure all messages are captured, even during crashes. Error objects are formatted with full stack traces and causes.

# Enable trace logging MCPMAN_TRACE=1 mcpman serve # View logs tail -f ~/.mcpman/mcpman.log tail -f ~/.mcpman/trace.log

Development

Setup

bun install pre-commit install # Install git hooks

Available Scripts

bun dev # Development server with hot reload bun run build # Build compiled binary bun run lint # Lint code bun run format # Format code bun run typecheck # Type check bun test # Run tests

Code Style

  • TypeScript with strict type checking

  • Biome for linting and formatting (100 char line width, 2-space indents)

  • Zod schemas for configuration validation

  • Pre-commit hooks ensure code quality

MCP Protocol Support

MCPMan fully supports the MCP protocol including:

  • Tool discovery and execution

  • Root directory management (transparent proxy)

  • Request/response handling

  • Error propagation

  • OAuth 2.1 authentication for HTTP transports

License

MIT

This server cannot be installed

-
security - not tested
-
license - not tested
-
quality - not tested

How are these scores calculated?

hybrid server

The server is able to function both locally and remotely, depending on the configuration or use case.

A Model Context Protocol server manager that acts as a proxy/multiplexer, enabling connections to multiple MCP servers simultaneously and providing JavaScript code execution with access to all connected MCP tools. Supports both stdio and HTTP transports with OAuth authentication, batch tool invocation, and dynamic server management.

  1. Overview
    1. Quick Start
      1. Installation
      2. Initialize Configuration
      3. Add MCP Servers
      4. Generate and Execute Code from Natural Language
      5. Evaluate Function Expressions with MCP Tools
      6. Run as MCP Server
    2. Architecture
      1. Server Mode
      2. CLI Mode
    3. Configuration
      1. CLI Commands
        1. JavaScript Execution Environment
          1. $results Array
        2. Batch Tool Invocation
          1. Logging
            1. Development
              1. Setup
              2. Available Scripts
              3. Code Style
            2. MCP Protocol Support
              1. License

                Appeared in Searches

                New MCP Servers

                MCP directory API

                We provide all the information about MCP servers via our MCP API.

                curl -X GET 'https://glama.ai/api/mcp/v1/servers/semistrict/mcpman'

                If you have feedback or need assistance with the MCP directory API, please join our Discord server