60fps vs io.github.cyanheads/macos-mcp-server
60fps is an MCP server published by 60fps.design. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.cyanheads/macos-mcp-server is an MCP server published by cyanheads. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-07. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  60fps |  io.github.cyanheads/macos-mcp-server |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.4.0 Downloads/month (npm): 1 148 Downloads/week (npm): 333 Forks (GitHub): 0 Stars (GitHub): 4 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.4.0 Downloads/month (npm): 1 148 Downloads/week (npm): 333 Forks (GitHub): 0 Stars (GitHub): 4 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | 60fps | io.github.cyanheads/macos-mcp-server |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 1 (worse) | 4 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-30 |
| Where it runs (differs) | Remote server (mcp.60fps.design/mcp) | On your machine (@cyanheads/macos-mcp-server) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 8, secrets among them: 0 |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/60fps-design/plugin | github.com/cyanheads/macos-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 2 days ago returned HTTP 405 | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
60fps
Real iOS interaction clips, motion breakdowns, SwiftUI to match. Paid licence required.
io.github.cyanheads/macos-mcp-server
Control macOS settings, apps, windows, audio, Music, displays, screenshots, and Focus mode via MCP.
How to run each
60fps As a remote MCP server
claude mcp add --transport http library https://mcp.60fps.design/mcpio.github.cyanheads/macos-mcp-server As a local MCP server: npm package
claude mcp add --transport stdio macos-mcp-server -- npx -y @cyanheads/macos-mcp-serverCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only 60fps has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of 60fps publish no settings it asks for, so we do not compare settings.
What it can do: 60fps · What it can do: io.github.cyanheads/macos-mcp-server · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.