mcp-runner

Created By
cookiecada year ago
A TypeScript SDK for running MCP (Model Context Protocol) servers with process reuse capabilities
Overview

what is mcp-runner?

mcp-runner is a TypeScript SDK and CLI designed for running MCP (Model Context Protocol) servers with process reuse capabilities, allowing for efficient server management and execution.

how to use mcp-runner?

To use mcp-runner, install it via npm and utilize the command-line interface or import it into your TypeScript projects to run MCP servers based on configurations defined in cline_mcp_settings.json.

key features of mcp-runner?

  • Server process reuse across multiple calls
  • Graceful termination with timeout handling
  • Automatic server lifecycle management
  • TypeScript support
  • Comprehensive error handling and logging

use cases of mcp-runner?

  1. Running multiple MCP server instances efficiently.
  2. Managing server processes for various tools in a single application.
  3. Automating server interactions in TypeScript projects.

FAQ from mcp-runner?

  • Can mcp-runner be used with any MCP server?

Yes! mcp-runner is designed to work with any server that follows the Model Context Protocol.

  • Is there a command-line interface available?

Yes! mcp-runner includes a CLI for easy interaction with MCP servers.

  • How do I handle errors while using mcp-runner?

The SDK includes comprehensive error handling for server process errors, tool execution errors, and timeout handling.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
cookiecad
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago