SkillAgentSearch skills...

local-runtime-mcp

Portable MCP runtime with 21 tools for processes, files, images, Chromium profiles and Windows desktop control. Shared OpenAI and Cloudflare connections with owner-approved OAuth.

Install / Use

claude mcp add hicancan -- npx -y github:hicancan/local-runtime-mcp

If the server publishes to npm under a different name, use that package instead — check the repo README.

About this skill
🔌

MCP Server

Model Context Protocol server

Quality Score

87/100

Category

Automation

Supported Platforms

Claude Code
Claude Desktop

Our assessment of local-runtime-mcp

local-runtime-mcp scores 87/100 on our quality scale, 1597th of 2,768 Automation skills we index.

Its MCP Server is 32 KB long, well organised into 22 sections with 20 code examples: a thorough specification that gives an agent plenty to work with.

It has 47 GitHub stars, so there is little community track record yet; judge it on its content.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
7/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated today, so local-runtime-mcp is actively maintained.
  • It is released under AGPL-3.0, a copyleft license: you can use it, but modified versions you distribute must carry the same license.
  • Its trust signals score 97/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-11-18. Automated pattern scan on 2026-11-18. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

local-runtime-mcp compared with similar skills

All 4 of these similar skills score higher than local-runtime-mcp; compare them before choosing.

SkillScoreStarsUpdatedFormat
local-runtime-mcp (this skill)by hicancan8747todayMCP Server
taste-skillby Leonxlnx100118.3k10d agoCLAUDE.md
Agent-Reachby Panniantong100113.0k10d agoCLAUDE.md
hyperframesby heygen-com10086.4ktodayCLAUDE.md
rufloby ruvnet10082.0ktodayCLAUDE.md

Frequently asked questions

How do I install local-runtime-mcp?
Run claude mcp add hicancan -- npx -y github:hicancan/local-runtime-mcp. The install tabs above show the steps for each supported agent.
Which AI agents does local-runtime-mcp work with?
It is written for Claude Code and Claude Desktop, as a MCP Server file. Other agents that read the same format can often use it too.
Is local-runtime-mcp safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is AGPL-3.0-licensed and scores 97/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is local-runtime-mcp still maintained?
The repository was last updated today, so local-runtime-mcp is actively maintained.

Local Runtime MCP

CI Release License: AGPL-3.0-only M8ven Verified

English · 简体中文

Give AI clients the programs, files, images, browser profiles, and desktop of the machine running lrmcp. Local Runtime MCP is a portable local runtime with 22 built-in MCP tools and reusable webpage capabilities registered from the file tree.

The same runtime offers an exact-origin-authorized browser SDK and a local model API with a separate model-only key. A browser model uses registered start / read / stop capabilities; Harness and applications keep their own agent loops. See tools, webpages and models.

Connect locally over stdio or Streamable HTTP, or remotely through OpenAI Secure MCP Tunnel and Cloudflare Tunnel. One running instance can expose both tunnels at once, with one set of process sessions, browser instances, and desktop control. Independent process sessions and browser tabs run concurrently; shared files and desktop input have explicit coordination rules.

  • Native multimodal results. Files, browser pages, and desktop observations return text and MCP image content directly.
  • Explicit browser targets. Connect several Chromium profiles, select a named browser instance, and operate its opaque tab handles.
  • Desktop control that leaves you working. See every display and window, read UI Automation trees with their text, and operate controls through their patterns without the pointer, keyboard or focus. Physical input, when needed, borrows them under a token, shown by a small pill you can click to stop.
  • Portable configuration. Keep local-runtime-mcp.yaml, the executable, and browser integration together on a fixed or removable drive.
  • Independent connection providers. Enable OpenAI, Cloudflare, or both for the same Runtime Host. Public HTTP supports static Bearer credentials or OAuth authorization with owner approval.
  • Platform-specific engines. Go hosts the runtime and MCP adapters; Rust implements Windows capture, UI Automation, and input; TypeScript implements Chromium integration.

Architecture

The connection layer delivers MCP requests. The capability layer defines machine operations. One Runtime Host owns the resources shared by every enabled entry point and client of a running instance.

flowchart TB
    Operator[Operator] --> CLI[CLI + configuration]
    CLI --> Supervisor[Entry-point supervisor]
    Supervisor --> Host[One Runtime Host]
    Local[Local MCP client] --> Stdio[MCP stdio]
    Local --> Public[Public-facing HTTP origin · Bearer or OAuth]
    Remote[Remote AI clients] --> OpenAI[OpenAI Tunnel adapter]
    Remote --> Cloudflare[Cloudflare adapter + cloudflared]
    OpenAI --> Private[Private HTTP origin · runtime credential]
    Cloudflare --> Public
    Stdio --> MCP[MCP adapter · 22 tools]
    Private --> MCP
    Public --> MCP
    MCP --> Process[Process]
    MCP --> Files[Filesystem]
    MCP --> Image[Image]
    MCP --> Computer[Computer]
    MCP --> Browser[Browser]
    Process --> Machine[Machine processes + files]
    Files --> Machine
    Image --> Machine
    Computer --> Native[Rust Windows engine]
    Native --> Desktop[Interactive desktop]
    Browser --> Bridge[Authenticated loopback bridge]
    Bridge --> Profiles[Chromium profile extensions]
    Profiles --> CDP[CDP tabs + frames]
    Host -. resource lifetime .-> MCP
    Host -. owns .-> Process
    Host -. owns .-> Files
    Host -. owns .-> Computer
    Host -. owns .-> Bridge
    Supervisor -. owns provider lifetime .-> OpenAI
    Supervisor -. owns provider lifetime .-> Cloudflare

Solid arrows show request flow; dotted arrows show lifetime ownership. Text and images travel as MCP content. OpenAI's private origin and the public-facing HTTP origin publish the same MCP Server while retaining their respective authentication boundaries. Cloudflare reaches the public origin over loopback; its external URL uses HTTPS.

| Layer | Responsibility | | --- | --- | | CLI and configuration | Select entry points explicitly and resolve configuration once. | | Entry-point supervisor | Own provider lifetimes, report exits, and keep surviving entry points available. | | Connection adapters | Deliver requests through stdio, HTTP, or a tunnel provider to the shared Server. | | MCP adapter | Publish tool schemas, validate inputs, and encode results. | | Capability services | Define resource identities, observations, actions, and concurrency. | | Platform backends | Execute OS operations, Windows native interaction, and Chromium CDP commands. |

The Host creates one Process Manager, Filesystem Service, Browser Bridge, and Computer Controller. A provider failure affects that entry point; the Host and other live entry points continue. When all entry points finish, or the operator interrupts the runtime, shutdown stops admission, cancels pending work, cleans up managed processes and input, and closes listeners and helpers. Individual request failures retain the running Host and its other resources. Recovery restores connectivity without replaying machine actions.

Commands and transports

lrmcp
├── serve
│   ├── --transport stdio|http
│   └── --tunnel openai|cloudflare   (repeatable with HTTP)
├── setup
│   ├── browser
│   └── oauth
├── version
└── help

serve starts one Host. Select --transport stdio for local process pipes or --transport http for HTTP connectivity. With HTTP, repeat --tunnel to enable both providers. Saved credentials configure a provider; the command selects whether it runs.

| Command | Connection and credentials | | --- | --- | | lrmcp serve --transport stdio | Standard MCP process pipes; the parent process supplies access. | | lrmcp serve --transport http | Direct loopback Streamable HTTP using the configured public-client authentication mode. | | lrmcp serve --transport http --tunnel openai | Official OpenAI forwarding to a private loopback MCP endpoint; configure the tunnel ID and API key. | | lrmcp serve --transport http --tunnel cloudflare | Official cloudflared companion forwards to authenticated loopback HTTP. | | lrmcp serve --transport http --tunnel openai --tunnel cloudflare | Both providers reach the same Host and resources. | | lrmcp setup browser | Generate bridge credentials and extract/configure the extension. | | lrmcp setup oauth --client-name NAME --redirect-uri URI | Register an OAuth client with its exact callback URI and generate credentials. | | lrmcp setup oauth --show | Display existing OAuth credentials deliberately in the local terminal. | | lrmcp version | Print the executable version. | | lrmcp help | Show commands and flags. |

OpenAI starts its private endpoint on a dynamically assigned loopback port and uses a fresh, in-memory private-hop credential. Cloudflare uses the configured public-facing loopback origin and its maintained companion executable. Domain services remain independent of either provider. A second machine runs its own Host and uses a distinct connection address; independent machines have independent resources and handles.

Configuration

flowchart LR
    Defaults[Defaults] --> YAML[Adjacent YAML]
    YAML --> Environment[Environment overrides]
    Environment --> Flags[Command-line overrides]
    Flags --> Config[Resolved configuration]
    Config --> Connection[Connection adapter]
    Config --> Host[Runtime Host]

Precedence is command line > environment > YAML > defaults. The file path is always <lrmcp directory>/local-runtime-mcp.yaml. Configuration validation covers the components selected for this invocation. Browser instance identity belongs to each browser profile's extension storage; process, tab, and desktop observation handles belong to the current runtime lifecycle.

Capability domains

| Domain | Tools | | --- | ---: | | Process | 2 | | Filesystem | 6 | | Image | 1 | | Computer | 5 | | Browser | 8 | | Total | 22 |

Process · 2 tools

flowchart TB
    Run[process_run] --> Resolve[Resolve program using child PATH]
    Resolve --> Launch[Direct launch · pipe or PTY]
    Launch --> Final[Completed result]
    Launch --> Sessions[Independent process sessions]
    Sessions --> Continue[process_continue · session_id]
    Continue --> Input[Serialized stdin + PTY resize]
    Continue --> Output[Bounded output · cursor read + wait]
    Output --> Cursor[Received output_cursor → next read]
    Sessions --> Retain[Completed async result · up to 10 minutes]
    Continue --> Stop[Independent terminate path]
  • process_run accepts program, argument array, working directory, environment overrides, initial stdin, execution timeout, output limits, and pipe or PTY I/O.
  • process_continue reads retained output from explicit byte offsets, writes stdin, closes pipe input, resizes a PTY, waits, or terminates a managed session.

Bare program names use the merged child PATH in both I/O modes; Windows also uses PATHEXT. Explicit relative executable paths resolve against the requested working directory. To execute shell syntax, launch the desired shell explicitly with its arguments.

Different sessions run concurrently. Within one session, input writes are serialized and output reads preserve the bounded stdout and stderr buffers. Waiting for output leaves termination available, including when stdin is blocked. Output and queued input are bounded; a single stdin payload is limited to 16 MiB.

Each result includes output_cursor: {stdout, stderr} with the next byte offsets. Pass the last successfully received cursor to process_continue to collect only new output. Omitting the cursor starts at zero and rereads the retained output. The returned stdout_offset and stderr_offset identify the actual start of each stream; a truncation flag indicates that the requested prefix has aged out of its buffer. Completed asynchronous sessions remain readable for up to ten minutes. Under capacity pressure, the oldest completed session makes room for a new process; active sessions keep their place.

If a pure-read response is lost, repeat process_continue with the same session_id and cursor. The response can include output produced since the previous attempt. Advance the cursor and append output only after receiving a successful result. Calls that start a process or change stdin, PTY size, or process lifetime require checking the resource before retrying after an uncertain response. A lost initial launch response may leave the client without a session ID.

duration_ms is elapsed process time while the program runs and its fixed lifetime after exit. Collecting a completed session later leaves that duration unchanged.

Cancellation delivered to process_run before it returns a live session terminates and collects that process. Cancellation delivered to process_continue stops that call's wait; use terminate=true to end the session. HTTP disconnect cancellation follows the negotiated MCP protocol: SDK request-context propagation applies to protocol 2026-07-28 and newer; older stateless requests may finish their bounded wait after the client disconnects. Execution timeout and Host shutdown terminate managed processes independently of the MCP request deadline.

Filesystem · 6 tools

flowchart TB
    Read[List · stat · read · search] --> Files[Machine filesystem]
    Write[Create · replace · patch] --> Path[Resolve commit path identity]
    Path 

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars47
CategoryAutomation
Updated15h ago
Forks0

Languages

Go

Trust signals

97/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 info