intercept_chrome
Launch an isolated Chrome window to intercept and inspect HTTP(S) traffic for debugging purposes. Routes all browser traffic through a specified proxy port without affecting normal browsing.
Instructions
Launch a fresh independent Chrome window with all HTTP(S) traffic intercepted. The browser uses an isolated profile so it won't affect your normal browsing.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| proxyPort | Yes | Proxy port to route traffic through |
Implementation Reference
- src/index.ts:136-146 (handler)The MCP tool 'intercept_chrome' is registered in index.ts and delegates the logic to `client.activateInterceptor('fresh-chrome', proxyPort)`.
server.registerTool( 'intercept_chrome', { title: 'Intercept Chrome Browser', description: 'Launch a fresh independent Chrome window with all HTTP(S) traffic intercepted. The browser uses an isolated profile so it won\'t affect your normal browsing.', inputSchema: z.object({ proxyPort: z.number().describe('Proxy port to route traffic through'), }), }, async ({ proxyPort }) => jsonResult(await client.activateInterceptor('fresh-chrome', proxyPort)) ); - src/httptoolkit-client.ts:101-111 (handler)The `activateInterceptor` method in HttpToolkitClient sends a POST request to the HTTP Toolkit server API endpoint `/interceptors/{id}/activate/{proxyPort}` to perform the actual interception activation.
async activateInterceptor( id: string, proxyPort: number, options?: unknown ): Promise<{ result: { success: boolean; metadata?: unknown } }> { return this.request( 'POST', `/interceptors/${encodeURIComponent(id)}/activate/${proxyPort}`, options || {} ); }