Safari’s new MCP server allows coding agents to inspect and debug websites


Apple introduces a new MCP server for Safari that allows coding agents to inspect websites directly in the browser, allowing them to access page content, console logs, network requests, screenshots, and more. Here are the details.

The MCP server is included in Safari Technology Preview 247

New post This is what Apple says in a blog post on WebKit Safari Technology Preview 247 Includes Safari MCP server, “a Model Context Protocol server for web developers that makes your web development and debugging faster and more powerful.”

From the post:

We know that agents are becoming more and more integrated into the coding process, and the Safari MCP server allows your agent to connect to the Safari browser window and see how your code is actually rendered in the browser.

MCP is an open standard created by Anthropic and later donated to the Linux Foundation’s Agentic AI Foundation. It essentially provides a common way for compatible AI agents to connect to external tools, services, and data sources, allowing them to access data and perform authorized actions rather than relying solely on what users paste into a conversation.

In practice, MCP can allow eligible clients such as ChatGPT, Claude, and Gemini to connect to MCP servers that expose services and resources including GitHub, Slack, Google Drive, Notion, databases, local files, and browser development tools.

With the new server configured in Safari Technology Preview 247, coding agents can inspect web pages, access console logs and network requests, capture screenshots, and interact with elements on the page.

Here’s a use case described in Apple’s post:

You see something wrong with your site in the browser. You open the console to hunt him down. You click on the Styles tab. You see what is broken. You go back to your code to fix it. Or maybe you can take a screenshot, detail the problem to your agent, and let them fix it for you. Hopefully it gets it right, the error is fixed and you can continue.

But when it’s not fixed, you go through the workflow again — Browser. Demand. Agent.

And again and again, until you finally crush the bug.

Regardless of the browser or tools you use, the debugging workflow involves multiple clicks, tools, and window jumps to make a single fix, but it doesn’t have to be that way. If you already use agents in your development workflow, Safari MCP server makes your debugging faster and more efficient.

The article outlines several potential uses for the Safari MCP server, including helping agents debug and identify websites. Safari compatibility issues, analyze performance, check accessibility, and test various page and user interface states.

In addition, the post lists and describes about 20 tools included with the server, e.g browser_console_messages to “return buffered console logs for the current or specified tab”. screenshot to “take screenshot of current page as PNG”. list_network_requests “list network request summaries (URL, method, status, time) for the current token” and page_interactions “Interact with the DOM in a sequence: click, type, scroll, hover, press, etc.”

To learn how to get started and use MCP on safari with Claude, Codex and more, follow this link.

It’s worth checking out on Amazon

FTC: We use automatic affiliate links that generate income. More.



Source link

Leave a Reply

Your email address will not be published. Required fields are marked *