feat(mcp): add browser_set_geolocation tool #38645

AdamParker19 · 2025-12-27T17:58:26Z

Adds geolocation mocking support to Playwright MCP via a new \�rowser_set_geolocation\ tool that uses the browser context's setGeolocation() method. Also adds \�rowser_clear_geolocation\ to reset the mocked state.

The tool:

Accepts latitude (-90 to 90), longitude (-180 to 180), and optional accuracy
Automatically grants geolocation permissions
Works at the browser context level, affecting all pages

Fixes microsoft/playwright-mcp#1114

pavelfeldman · 2025-12-30T22:32:11Z

packages/playwright/src/mcp/browser/tools/geolocation.ts

+import { defineTool } from './tool';
+
+const setGeolocation = defineTool({
+    capability: 'core',


These don't sound core to me, please kick them out into a separate geolocation capability.

pavelfeldman

Can't have a patch w/o tests either.

AdamParker19 · 2025-12-31T03:19:26Z

@pavelfeldman

Thanks for the review! I've addressed both feedback items:

1. Separate capability: Changed from capability: 'core' to capability: 'geolocation'. The tools now require --caps=geolocation to enable.

2. Added tests: Created tests/mcp/geolocation.spec.ts with:

Capability availability test (verifies tools appear with --caps=geolocation)
browser_set_geolocation functional test (sets coords, navigates, verifies mocked location)
browser_clear_geolocation test

All 3 tests pass locally.

Let me know your feedback :)

pavelfeldman · 2025-12-31T23:38:38Z

packages/playwright/src/mcp/browser/tools/geolocation.ts

+            accuracy: params.accuracy ?? 0,
+        });
+
+        response.addCode(`await context.grantPermissions(['geolocation']);`);


Let's generate page.context().grantPermission to give LLM a better clue if it needs to generate the source code.

pavelfeldman · 2025-12-31T23:41:35Z

packages/playwright/src/mcp/browser/tools/geolocation.ts

+        const browserContext = await context.ensureBrowserContext();
+
+        // Clear permissions revokes geolocation access
+        await browserContext.clearPermissions();


You would want to keep the permission and run browserContext.setGeolocation(null) instead.

pavelfeldman · 2025-12-31T23:45:39Z

packages/playwright/src/mcp/browser/tools/geolocation.ts

+import { defineTool } from './tool';
+
+const setGeolocation = defineTool({
+    capability: 'geolocation',


This property is typed, make sure you update the types and the docs.

Adds geolocation mocking support to Playwright MCP via a new \�rowser_set_geolocation\ tool that uses the browser context's setGeolocation() method. Also adds \�rowser_clear_geolocation\ to reset the mocked state. The tool: - Accepts latitude (-90 to 90), longitude (-180 to 180), and optional accuracy - Automatically grants geolocation permissions - Works at the browser context level, affecting all pages Fixes microsoft/playwright-mcp#1114

Addresses PR review feedback: - Changed capability from 'core' to 'geolocation' - Tools now require --caps=geolocation flag to enable - Added geolocation.spec.ts with tests for: - Capability availability with --caps=geolocation - browser_set_geolocation functional test - browser_clear_geolocation test

- Use page.context().grantPermissions/setGeolocation for better LLM code hints - Use setGeolocation(null) instead of clearPermissions() to preserve permissions - Add 'geolocation' to ToolCapability type in config.d.ts - Update capabilities documentation in config.d.ts - Update --caps CLI help text to include geolocation - Update test assertions to match new generated code format

AdamParker19 · 2026-01-01T09:00:52Z

Thanks for the detailed review @pavelfeldman! I've addressed all feedback and rebased on latest main:

Changes made:

1. Generated code uses page.context() for better LLM hints

- await context.grantPermissions(['geolocation']);
- await context.setGeolocation({ latitude: 37.77, longitude: -122.42, accuracy: 100 });
+ await page.context().grantPermissions(['geolocation']);
+ await page.context().setGeolocation({ latitude: 37.77, longitude: -122.42, accuracy: 100 });

2. browser_clear_geolocation now uses setGeolocation(null) to preserve permissions

- await browserContext.clearPermissions();
+ await browserContext.setGeolocation(null);

3. Updated types and documentation

Added 'geolocation' to ToolCapability type in config.d.ts
Updated capability documentation
Updated --caps CLI help text

4. Rebased on latest main - resolved conflict with new --allow-unrestricted-file-access option

All 3 tests pass locally:

✓ test geolocation capability available with --caps=geolocation
✓ browser_set_geolocation  
✓ browser_clear_geolocation

github-actions · 2026-01-02T18:32:29Z

Test results for "MCP"

14 failed
❌ [chrome] › mcp/generator.spec.ts:23 › generator tools intent @mcp-ubuntu-latest
❌ [chromium] › mcp/generator.spec.ts:23 › generator tools intent @mcp-ubuntu-latest
❌ [firefox] › mcp/generator.spec.ts:23 › generator tools intent @mcp-ubuntu-latest
❌ [webkit] › mcp/generator.spec.ts:23 › generator tools intent @mcp-ubuntu-latest
❌ [chrome] › mcp/generator.spec.ts:23 › generator tools intent @mcp-windows-latest
❌ [chromium] › mcp/generator.spec.ts:23 › generator tools intent @mcp-windows-latest
❌ [firefox] › mcp/generator.spec.ts:23 › generator tools intent @mcp-windows-latest
❌ [webkit] › mcp/generator.spec.ts:23 › generator tools intent @mcp-windows-latest
❌ [msedge] › mcp/generator.spec.ts:23 › generator tools intent @mcp-windows-latest
❌ [chrome] › mcp/generator.spec.ts:23 › generator tools intent @mcp-macos-15
❌ [chromium] › mcp/generator.spec.ts:23 › generator tools intent @mcp-macos-15
❌ [chromium] › mcp/test-debug.spec.ts:48 › test_debug (pause/resume) @mcp-macos-15
❌ [firefox] › mcp/generator.spec.ts:23 › generator tools intent @mcp-macos-15
❌ [webkit] › mcp/generator.spec.ts:23 › generator tools intent @mcp-macos-15

2847 passed, 116 skipped

Merge workflow run.

Fixed 41 ESLint indentation errors - project style requires 2-space indentation, not 4-space.

AdamParker19 · 2026-01-02T18:43:26Z

Good morning and Happy new year to you @pavelfeldman

I have fixed the indentation issue and the docs & lint test should pass now what do you want me to do about the other tests please let me know

Skn0tt · 2026-01-14T09:38:31Z

Hi folks! I'm unsure we need a new tool for this, every tool means more context usage just for the tool definition.

I've had good results with guiding my agent to use browser_run_code to grant permissions and set geolocation. Have you tried that, and if yes, what's your experience with that approach?

AdamParker19 · 2026-01-14T11:17:22Z

Hi @Skn0tt, thanks for the feedback!

I understand the concern about context usage. To address that, per Pavel's earlier review, I moved this tool into a separate geolocation capability (opt-in via --caps=geolocation). This ensures it doesn't pollute the context for users who don't explicitly ask for it.

Regarding browser_run_code, while it is a powerful fallback, I see a few strong reasons for a dedicated tool here:

Reliability: Setting geolocation correctly requires a specific multi-step sequence (granting permissions + setting coordinates). I've found that models often hallucinate the syntax or miss the permission step when trying to write this as raw Playwright code. A dedicated tool guarantees it works every time.
Safety & Sandboxing: Many deployments disable browser_run_code (arbitrary code execution) for security reasons. A dedicated tool allows agents to perform this specific, common action without requiring full remote code execution privileges.
Discovery: It acts as a clear signpost for the model that "this browser can handle location-based tasks," which run_code doesn't explicitly advertise.

Since this is now behind a flag and doesn't affect the default context, is this okay to you what is your feedback?

Hi folks! I'm unsure we need a new tool for this, every tool means more context usage just for the tool definition.

I've had good results with guiding my agent to use browser_run_code to grant permissions and set geolocation. Have you tried that, and if yes, what's your experience with that approach?

pavelfeldman reviewed Dec 30, 2025

View reviewed changes

pavelfeldman reviewed Dec 31, 2025

View reviewed changes

AdamParker19 added 3 commits January 1, 2026 12:46

AdamParker19 force-pushed the feat/mcp-geolocation branch from 236f9d4 to 80f5a61 Compare January 1, 2026 08:41

style: fix indentation to use 2 spaces

79ccef8

Fixed 41 ESLint indentation errors - project style requires 2-space indentation, not 4-space.

AdamParker19 requested a review from pavelfeldman January 8, 2026 18:47

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat(mcp): add browser_set_geolocation tool #38645

feat(mcp): add browser_set_geolocation tool #38645

AdamParker19 commented Dec 27, 2025

Uh oh!

pavelfeldman Dec 30, 2025

Uh oh!

pavelfeldman left a comment

Uh oh!

AdamParker19 commented Dec 31, 2025

Uh oh!

pavelfeldman Dec 31, 2025

Uh oh!

pavelfeldman Dec 31, 2025

Uh oh!

pavelfeldman Dec 31, 2025

Uh oh!

AdamParker19 commented Jan 1, 2026

Uh oh!

github-actions bot commented Jan 2, 2026

Uh oh!

AdamParker19 commented Jan 2, 2026

Uh oh!

Skn0tt commented Jan 14, 2026

Uh oh!

AdamParker19 commented Jan 14, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

feat(mcp): add browser_set_geolocation tool #38645

Are you sure you want to change the base?

feat(mcp): add browser_set_geolocation tool #38645

Conversation

AdamParker19 commented Dec 27, 2025

Uh oh!

pavelfeldman Dec 30, 2025

Choose a reason for hiding this comment

Uh oh!

pavelfeldman left a comment

Choose a reason for hiding this comment

Uh oh!

AdamParker19 commented Dec 31, 2025

Uh oh!

pavelfeldman Dec 31, 2025

Choose a reason for hiding this comment

Uh oh!

pavelfeldman Dec 31, 2025

Choose a reason for hiding this comment

Uh oh!

pavelfeldman Dec 31, 2025

Choose a reason for hiding this comment

Uh oh!

AdamParker19 commented Jan 1, 2026

Changes made:

Uh oh!

github-actions bot commented Jan 2, 2026

Test results for "MCP"

Uh oh!

AdamParker19 commented Jan 2, 2026

Uh oh!

Skn0tt commented Jan 14, 2026

Uh oh!

AdamParker19 commented Jan 14, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants