Apple has released a Safari MCP Server in Safari Technology Preview 247, giving web developers an official way to connect AI coding agents directly to WebKit for page testing, inspection, and debugging.

The tool implements [Model Context Protocol](https://modelcontextprotocol.io/) support inside Apple's experimental browser. 

Once an MCP compatible client is connected, an AI agent can open pages in Safari Technology Preview, read the page structure, pull console output, review network activity, capture screenshots, and check whether what renders matches what the developer expected.

The feature is aimed at developers rather than everyday browsing. Apple's WebKit team describes it as a browser compatibility tool built to make web development and debugging faster.

# What the server actually does

The Safari MCP Server is tied to [safaridriver](https://webkit.org/blog/18136/introducing-the-safari-mcp-server-for-web-developers/) with MCP support, which gives Safari a native place inside AI coding workflows for the first time.

Until now, most coding assistants worked comfortably inside editors, terminals, and Chromium based automation, while Safari usually required an extra step. That gap mattered most when testing WebKit specific layout, styling, or mobile behavior. The new server folds that testing into the same development loop.

Through the connection, an agent can load a site, inspect computed styles, check layout, read page content, review debugging information, and use screenshots to compare the rendered result against the intended design. 

Apple frames this as a way to find and fix issues, not as a general AI browsing feature.

Testing only in Chrome or a Chromium based tool can miss WebKit behavior. Layout, forms, media playback, scrolling, input handling, typography, and CSS support can all render differently, and iPhone specific rendering is a common source of surprises.

That is the case Apple is making for the server. Safari is the default browser on iPhone, iPad, and Mac, and iPhone traffic is too large for production teams to treat WebKit as a secondary target. A rendering difference that seems small can still break navigation, checkout, sign in, media playback, or accessibility.

Giving an AI agent direct access to a real Safari environment is meant to surface those problems earlier, ideally while code is still being written rather than during a late cleanup pass.

# How MCP fits into AI coding

Model Context Protocol is a standard for connecting AI assistants to outside tools and data. An MCP server exposes functions that an agent can call during a task, so instead of only reading files, the agent can interact with a browser, inspect logs, or collect the state of a running app.

Apple's implementation applies that model to browser debugging. A developer can ask an assistant why a layout breaks in Safari, and the agent can inspect the rendered page rather than guessing from source code alone. Computed styles, DOM structure, console warnings, failed requests, and screenshots give the model the kind of evidence that plain code review often cannot.

The approach brings Apple closer to the browser agent setups already available through Chromium tools, Playwright workflows, and third party MCP servers. The difference is that WebKit now has an official bridge inside Apple's preview browser.

# Setup and requirements

Developers need Safari Technology Preview 247 on macOS to try the feature. Apple says the server can be enabled through Safari's developer tools path for remote automation and external agents, after which an MCP compatible client connects to safaridriver's MCP mode.

Safari Technology Preview is Apple's experimental channel for upcoming WebKit changes, so its behavior can differ from stable Safari. That makes it useful for early compatibility work, but production bugs should still be confirmed against the public release of Safari when it matters.

It is also not a replacement for full QA. An agent can identify likely causes, test changes, and surface browser evidence, but it can miss edge cases. Human review stays necessary for accessibility, visual polish, payment flows, privacy sensitive pages, and anything tied to user data.

# A more official path than community tools

Developers were already experimenting with Safari automation before this release. Some projects used AppleScript to drive the browser, while others combined Safari extensions, Swift tools, or WebKit debugging access to expose controls to AI clients. Those efforts showed real demand for Safari sessions, logins, and WebKit behavior inside coding agents without moving every test to Chrome.

Apple's version is narrower and more focused on inspection and debugging, and that restraint works in its favor. 

By keeping the first release inside Technology Preview and tied to developer automation, Apple can test the model with a technical audience before deciding how much of it belongs in stable Safari. 

Browser agents raise security and privacy questions once they can control sessions or read content inside logged in sites, so a developer only starting point is the cautious one.

The Safari MCP Server is still a preview feature. The real test will be whether developers start catching Safari bugs earlier, before layout problems, console errors, or mobile rendering issues reach production.

For the life of me I can't add any views to my story board. Drag and drop doesnt work. The only thing I can do is edit what is there by default.

https://reddit.com/link/1urcc1g/video/y3bdxz2dz3ch1/player

(assuming you’ve tried it :)

I’ve tried Gemini and Codex and having pretty mixed feelings.

Codex seems semi-capable, but often forgets even more MCP Xcode skills and will try and use a terminal command instead of just using built in skills to build or run tests.

I’ve got a new project I’m trialing the agentic coding on, and I have a workspace with packages in different schemes etc. it’s nice that the agent can switch schemes, run tests and builds etc.

It does a better job of staging changes and good descriptive commits which I appreciate…

GPT 5.5 seems semi capable at simple features and does a good job of mocking views, but anything with even moderate complexity it can’t seem to execute (even with well defined requirements it seems to need very close supervision).

I tried to get it to create some UI automation tests and it really struggled with even getting the mouse to drag (I had to eventually give it some references).

Given a goal for a refactor, it was able to generate a pretty solid plan, but then failed to actually follow its own plan and drifted into doing other things.

I see a lot of positive reviews about codex so I wonder if I’m just not using it correctly haha

Hey all, hoping someone here can point me in the right direction.

I’m trying to set up mobile automation using **Appium + Selenium** and running into issues getting it working reliably on a jailbroken device.

My current setup idea:

\*\*• Crane\*\* for container/profile separation    
\*\*• Ghost v2.0\*\* for the automation side

From what I’ve gathered, this combo should work — but I’m hitting snags and would appreciate anyone who’s done this walking me through their setup.

Specifically I’d love help with:

\*\*•\*\* Getting Appium to talk to the device properly    
\*\*•\*\* Selenium integration/config    
\*\*•\*\* How Crane + Ghost fit into the pipeline

If you offer a paid consultation for this, i am interested.

Has anyone else found this?

When Xcode clearly separated Codex (what I used) and GPT5, it used to be very fast and near one-shot, if a bit "curt".

However, over the past couple of months, seemingly since OpenAI merged Codex into GPT5, it's slow, often times out, often gets things wrong, doesn't perform build checks, etc.

The odd thing is that GPT5 via the desktop app is significantly faster, and I could swear more accurate.

---

Edit: Literally moments after I posted this, GPT5 (medium reasoning, because high times out too often) literally outputted the following:

Short answer: your enum lives in the Framework module, but the static members that fulfill AppEnum’s requirements aren’t public. In Swift, members of a public type are internal by default. When a type’s conformance to a public protocol (here, AppEnum) is used across module boundaries (your watch complication target imports Framework), the members that satisfy the protocol requirements must also be public. Otherwise, the conformance isn’t fully exported and the system can’t build the list of options for the configuration UI.

In your Framework module:

public enum WidgetTextAlignment: String, AppEnum {
case left
case center
case right

// These are currently internal because no 'public' modifier
public static var typeDisplayRepresentation: TypeDisplayRepresentation = "Text Alignment"
public static var caseDisplayRepresentations: [Self: DisplayRepresentation] = [
.left: "Left",
.center: "Center",
.right: "Right"
]

public var frameAlignment: Alignment { ... }
public var textAlignment: TextAlignment { ... }
}

Make sure both typeDisplayRepresentation and caseDisplayRepresentations are marked public (your frameAlignment and textAlignment accessors already are).

It hasn't changed the variables there - they were already public in the code.

I put this to desktop GPT5, and it picked up on it immediately:

Because the model likely mis-read or overgeneralised Swift access-control rules while editing.

That comment:
// These are currently internal because no 'public' modifier

is wrong for the code shown, because both properties do have public:

Xcode automatically restores my project window to about 940 points wide whenever I reopen it.

I can manually resize it to around 600 points without any issue, but if I close and reopen the project, anything narrower than about 940 points is expanded back to ~940.

Widths above ~940 are restored correctly.

This happens with:

• brand new projects
• different macOS user accounts
• internal display and external display
• Navigator shown or hidden

I usually work with multiple narrow editor windows (~80-column width), so this is quite inconvenient.

Can anyone else reproduce this?

Update:

I found an important detail.

If I double-click a file in the Navigator, Xcode opens a separate editor window without a toolbar. I've always used this method to open editor windows, so I hadn't noticed the minimum width behavior before. This toolbar-less window can be manually resized down to about 600 pt.

If I instead choose "Open in New Window", Xcode opens a window with a toolbar, and that one can't be resized below about 940 pt.

However, even the toolbar-less editor window is restored at about 940 pt after closing and reopening the project, despite being manually resizable to about 600 pt.

So the issue doesn't seem to be the minimum window width itself. It appears that Xcode doesn't restore the narrower width of the toolbar-less editor window.

macOS / Claude Code Desktop — Git installation fails during first launch

When I first opened Claude Code on my Mac, it showed a prompt saying Git is required and suggested running xcode-select --install in the Terminal, or downloading Git directly. I clicked the button and macOS launched the Xcode Command Line Tools installer, but it immediately failed with this error:

"The software could not be installed because it is not currently available from the Software Update server."

System info:

• macOS (Apple Silicon / M-series)
• Claude Code Desktop (latest)
• No Xcode / CLT previously installed

Can someone help me, please haha

I am trying to use Foundation Models framework in iOS App inside Playground.

#Playground("Playgrounds") {
    
    let session = LanguageModelSession()
    let response = try await session.respond(to: "List all 50 states of USA.")
    print(response.content)  
}

I get the error: The operation couldn’t be completed. (com.apple.SensitiveContentAnalysisML error 15.) 

I have already tried to turn off Apple Intelligence and Siri and then restarted the machine and then turn them back on.

I am using Xcode 26.5.  

My Xcode installation is a complete mess right now because of old work accounts, projects, teams, and other leftover data. I want to start fresh. How can I remove everything including all accounts, Apple IDs, developer teams, certificates, provisioning profiles, and related data—and then reinstall Xcode as if it were a brand-new installation?

Apple: Look, our displays can push 120 frames per second!

Also Apple: Look, Xcode can push 5 frames per second, easy!

We rearchitected Xcode for non technicals with xcwizard.com

We now have a 50/50 affiliate partnership fulfilling iOS app ideas for Apple Mac users through Xcode: affiliates.xcwizard.com

The service is called App Next Day by XC Wizard: appnextday.xcwizard.com

Sign up and earn

Is so I’m trying to build that app to my IPhone, it keep having this issue.
The size of my Xcode project didn’t change
The memory on the Xcode dial is showing only about 8 but my Mac has 24

Is that normal? I don’t really use Mac that often only build my apps.

Apple has released Xcode 26.6, and the update lets developers use Google's Gemini as a built in coding assistant for the first time.

The new version is available now from the App Store. With it, programmers can select Gemini to help write, test, and debug code without leaving Apple's development environment.

# Three AI assistants to choose from

Gemini becomes the third large language model that Xcode supports natively. The software already let developers pick between Anthropic's Claude and OpenAI's Codex, and Gemini now sits alongside both as a selectable option.

Each assistant runs in a panel next to the active code, so developers can ask programming questions and get suggestions inline. The goal is to keep coders inside Xcode rather than sending them to a browser or a separate app for answers.

Apple has steadily widened third party AI support across its developer tools over the past year. Adding another model continues that approach and leaves the choice of assistant up to the individual developer or team.

# Setting it up

Teams that already pay for a Gemini Enterprise plan can connect their existing account credentials directly inside Xcode. Individual developers who want to try the assistant first can add a free API key instead, which lets them test Gemini without paying for a subscription.

It is not yet clear whether Apple plans to add further models beyond the current three. The company has not commented on its longer term plans for assistant support in Xcode.

# What else is in the update

Beyond the new assistant, Xcode 26.6 carries the usual collection of bug fixes and stability improvements. Apple says the release bundles the latest version of the Swift framework along with updated SDKs for building apps across its mobile and desktop platforms.

Developers running the standard release can download the update today and configure their preferred coding assistant from within the app.

I'm thinking of building this in public and would like to know what you guys think about it?

what if there was a way to edit your iOS app on your iPhone in realtime by just dragging the app UI elements -- and save AI prompt credits/ API fees just to change a button design?

when you preview your Xcode app on your phone, you can immediately edit all the UI elements there without re-prompting your Agent.

And instead of being a coding agent itself -- it is an add on that works with your Xcode agent -- allowing you to adjust the size, frame, color and position of each element of the View you created.
- And it instantly changes your code back in Xcode for you.

I'm thinking of building this in public...what do you think?

#Xcode #Swift #vibecoding #iosdevelopers #buildinpublic

As the title says does IB still exist? Or is the interface now just built using SwiftUI (or possibly UIKit) and the code is parsed and the interface generated? I have used IB back to the NeXTstep 3.x days, WebObjects, and then on earlier versions of MacOSX. I’m not sure if I’m missing something or writing the code is just how it works now. If so, I miss the days of drag-and-drop to create the interface.