Add plugin integration docs with correct MCP tool names
Document that when installed as browse@saiden plugin, MCP server is named 'context' and tools are accessed as mcp__context__*. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -103,6 +103,19 @@ browse-mcp
|
|||||||
|
|
||||||
The MCP server (`src/mcp.ts`) exposes all browser commands as tools. It uses stdio transport and auto-launches the browser on first command.
|
The MCP server (`src/mcp.ts`) exposes all browser commands as tools. It uses stdio transport and auto-launches the browser on first command.
|
||||||
|
|
||||||
|
### Plugin Integration
|
||||||
|
|
||||||
|
When installed as a Claude Code plugin (`browse@saiden`), the MCP server is named `context`. Tools are accessed as:
|
||||||
|
|
||||||
|
- `mcp__context__goto` - Navigate to URL
|
||||||
|
- `mcp__context__query` - Query elements by CSS selector
|
||||||
|
- `mcp__context__click` - Click an element
|
||||||
|
- `mcp__context__type` - Type into an input field
|
||||||
|
- `mcp__context__screenshot` - Take a screenshot
|
||||||
|
- `mcp__context__close` - Close the browser
|
||||||
|
|
||||||
|
The plugin also provides slash commands: `/browse:start`, `/browse:goto`, `/browse:end`, etc.
|
||||||
|
|
||||||
### Debugging Tools
|
### Debugging Tools
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
|
|||||||
Reference in New Issue
Block a user