@nebula-agents/electron-mcp
Embedded MCP server for Electron apps that exposes BrowserWindow surfaces and lets MCP clients drive renderers through Chrome DevTools Protocol.
README
@nebula-agents/electron-mcp
Embedded MCP server for Electron apps. It runs inside your Electron main
process, exposes the BrowserWindow surfaces you choose, and lets MCP clients
drive those renderers through Chrome DevTools Protocol.
Embedded vs External Attach
This package is for apps that want MCP automation as an opt-in feature of the app itself. Your main process decides when the server starts, which windows are reachable, and which custom tools are registered.
External-attach servers connect to an already-running Electron app through a remote debugging port. That can be useful for local debugging, but it does not let the app own surface naming, gating, or app-specific tools. If you want that external model, this package is probably not the right fit.
Quickstart
import { app, BrowserWindow } from "electron";
import {
createElectronMcpServer,
recommendedGuards,
} from "@nebula-agents/electron-mcp";
let mainWindow: BrowserWindow | null = null;
const mcp = createElectronMcpServer({
getSurfaces: () => ({ main: mainWindow }),
});
app.whenReady().then(async () => {
mainWindow = new BrowserWindow();
if (recommendedGuards({ app, envVar: "MY_APP_MCP" })) {
await mcp.start();
console.log(`MCP listening at ${mcp.url}`);
}
});
app.on("before-quit", () => {
void mcp.stop();
});
Connect an MCP client to the logged HTTP URL. The default is
http://127.0.0.1:9229/mcp.
API
const mcp = createElectronMcpServer({
getSurfaces: () => ({ main: mainWindow, settings: settingsWindow }),
port: 9229,
host: "127.0.0.1",
path: "/mcp",
instructions: "Optional client-facing instructions.",
});
createElectronMcpServer(config) returns a synchronous handle:
addTool(toolDef)registers a custom tool. Call it beforestart().start()starts the loopback HTTP server.stop()stops the HTTP server and detaches CDP sessions.isRunningreports whether the server is active.urlis the bound MCP endpoint once running.
Bundled tools:
list_surfacesshow_surfacehide_surfacefocus_surfacereload_surfacescreenshotevaluateclicktype_textpress_keyhoverquery_domax_snapshotfill_formwait_for_load
Public types are available from the root export and from
@nebula-agents/electron-mcp/types.
Custom Tools
import { z } from "zod";
import type { ToolDef } from "@nebula-agents/electron-mcp/types";
const resetStateTool: ToolDef = {
name: "reset_state",
config: {
title: "Reset State",
description: "Reset the app's local demo state.",
inputSchema: { profile: z.enum(["empty", "demo"]) },
},
handler: async ({ profile }) => {
await resetLocalState(profile);
return { content: [{ type: "text", text: "ok" }] };
},
};
mcp.addTool(resetStateTool);
Tools must be registered before start(). Dynamic tool registration and
tools/list_changed are intentionally out of scope for 0.x.
Security Model
The server binds to loopback only by default: 127.0.0.1. Attempts to bind a
non-loopback host throw. There is no authentication layer in 0.1.0; if your
threat model requires more than loopback isolation, wrap this package in your
own gate or do not start it.
Recommended production guard:
import { recommendedGuards } from "@nebula-agents/electron-mcp";
if (recommendedGuards({ app, envVar: "MY_APP_MCP" })) {
await mcp.start();
}
The helper returns true only when the app is not packaged and the selected
environment variable is set to "1". It throws if neither app.isPackaged nor
isPackaged is provided.
Maintenance
This is open code with no support SLA. Agent Labs reviews issues and PRs on a
best-effort basis. 0.x versions may change API shape based on real usage.
License
MIT.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.