Connector field guide

Developer tools MCP servers

These servers expose different parts of a development workflow: repository data and actions, or interactive browser control.

Grouped by developer workflow and listed alphabetically. The verified label comes from the upstream registry.

Upstream MCP servers for repository work and browser automation.

Compare the options

2 servers

Best suited to: Agents that need to inspect repositories, issues, or pull requests, with optional repository workflow actions.
Access consideration: The configured token or app permissions determine which GitHub resources and operations are available.

Best suited to: Exploratory browser workflows and agent loops that need to inspect page structure and interact with its controls.
Access consideration: A persistent profile can retain login state and cookies between sessions; choose profile behavior deliberately.

Comparison of developer tools MCP servers by purpose and main access consideration
Server	Best suited to	Access consideration
GitHub MCP Server	Agents that need to inspect repositories, issues, or pull requests, with optional repository workflow actions.	The configured token or app permissions determine which GitHub resources and operations are available.
Playwright MCP	Exploratory browser workflows and agent loops that need to inspect page structure and interact with its controls.	A persistent profile can retain login state and cookies between sessions; choose profile behavior deliberately.

GitHub’s MCP server exposes repository, issue, and pull request tools to an MCP client.

Best for
Agents that need to inspect repositories, issues, or pull requests, with optional repository workflow actions.

Sources checked: 2026-10-27

The configured token or app permissions determine which GitHub resources and operations are available.
Write-capable tools can change repositories or work items; use read-only mode when changes are outside the task.

Microsoft’s Playwright MCP server lets an agent navigate and interact with browser pages using structured accessibility snapshots.

Best for
Exploratory browser workflows and agent loops that need to inspect page structure and interact with its controls.

Sources checked: 2026-10-27

Navigate pages, inspect accessibility snapshots, and interact with referenced elements.
Support browser sessions with persistent or isolated profiles and multiple browser engines.

A persistent profile can retain login state and cookies between sessions; choose profile behavior deliberately.
Browser navigation and interaction can reach sensitive sites or act in authenticated sessions, so constrain the browser environment and session access.