edge-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Host for the HTTP server. Default is 127.0.0.1. | 127.0.0.1 |
| PORT | No | Port for the HTTP server. Default is 7123. | 7123 |
| EDGE_CDP_PORT | No | CDP port to connect to Edge. Default is 9222. | 9222 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| navigateB | Navigate the active Edge tab to a URL. |
| go_backA | Go back one step in the active tab's history. |
| go_forwardB | Go forward one step in the active tab's history. |
| reloadC | Reload the active tab. |
| clickB | Click an element matching the CSS selector on the active tab. |
| typeA | Type text into a focusable element matching the CSS selector, simulating keystrokes (fires key events). Use for typing into inputs or contenteditable regions. For filling a form field in one shot, prefer fill. |
| fillA | Set the value of an input/textarea/select matching the CSS selector in one shot (no key events). Clears the field first. Faster than type for setting a known value. Sets the value via the DOM and dispatches an input event so frameworks (React, Vue, etc.) pick up the change. |
| pressA | Press a key on the active tab (sent to the currently focused element). Accepts KeyDescriptor names like Enter, Tab, Escape, ArrowDown, or single characters like 'a'. |
| screenshotB | Capture a screenshot of the active tab (full page or viewport) and return it as an image. The image is returned inline so the model can see it. |
| get_textA | Return the visible text content of an element (or the whole page if no selector). Whitespace is collapsed; hidden text is excluded. |
| get_htmlA | Return the HTML of an element (outerHTML) or the whole document. Useful for inspecting structure; for visible text use get_text. |
| evaluateB | Run a JavaScript expression in the active tab's page context and return the result as JSON. The expression is evaluated as the body of an async function, so you can use await. DOM globals (document, window) are available. Results must be JSON-serializable. |
| list_tabsA | List all open tabs in Edge with their targetId, URL, and title. |
| new_tabA | Open a new tab in Edge and optionally navigate it to a URL. Returns the new tab's targetId. |
| switch_tabA | Bring a tab to the front so it becomes the active tab. All navigation/interaction/read tools operate on the active tab, so call this first to target a specific tab. |
| close_tabA | Close a tab. If no targetId is given, closes the active tab. If the last tab is closed, Edge's behavior depends on the user-data-dir. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Each tool has a clearly distinct purpose: navigation, tab management, interaction, inspection, and evaluation are separated cleanly. The only closely related tools are type, fill, and press, but the descriptions explicitly distinguish simulated typing, one-shot value setting, and key presses.
All names use lower snake_case and are action-oriented, which is highly readable. However, some are single verbs (navigate, click) while others are verb_noun (get_text, list_tabs, switch_tab), so it is not a strict uniform pattern throughout.
Sixteen tools is slightly above the typical well-scoped range but remains reasonable for browser automation, covering navigation, tabs, interaction, reading, and evaluation. Each tool has a plausible role, with little obvious redundancy.
The surface covers the core browser lifecycle: navigate/reload/history, tab management, clicking, typing, screenshots, DOM text/HTML inspection, and JS evaluation. Minor gaps remain around explicit scrolling, waiting for elements/load states, hover/drag, and file upload, though evaluate can work around some of these.