What it does
Render and verify native Rust GUIs headlessly: access tree, query, a11y, screenshots, motion.
- Connects Runs on your computer
- Account or key No key needed
- Category Developer tools
Use together with
Skills that teach the AI this kind of work; they work alongside this one
andrej-karpathy-skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Why it ranks here
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 14/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 7/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 22/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Install
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
No key, nothing to install · Only the Claude desktop app (Windows or Mac), not the web or phone
Download the maker’s installer
Download the maker’s .mcpb file
The .mcpb file comes straight from the maker; we do not change it
Double-click the file, then click Install in the Claude desktop app
Try it
Use Fenestra MCP and tell me what you can do for me, then show me one thing✓ If Claude says it is using Fenestra MCP or shows a Fenestra MCP tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Fenestra MCP yet
Fenestra MCP runs on your computer, but ChatGPT can only connect servers that run on the web
What you can do instead
A · Use an app that can connect Fenestra MCP
- No key, nothing to install · Only the Claude desktop app (Windows or Mac), not the web or phone
B · Others in Developer tools that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
- Sentry✓ ChatGPT
- Compiler Explorer✓ ChatGPT
- GitDiagram✓ ChatGPT
Claude Code cannot connect Fenestra MCP yet
The maker only provides an installer for the Claude desktop app
What you can do instead
A · Use an app that can connect Fenestra MCP
- No key, nothing to install · Only the Claude desktop app (Windows or Mac), not the web or phone
Cursor cannot connect Fenestra MCP yet
The maker only provides an installer for the Claude desktop app
What you can do instead
A · Use an app that can connect Fenestra MCP
- No key, nothing to install · Only the Claude desktop app (Windows or Mac), not the web or phone
VS Code cannot connect Fenestra MCP yet
The maker only provides an installer for the Claude desktop app
What you can do instead
A · Use an app that can connect Fenestra MCP
- No key, nothing to install · Only the Claude desktop app (Windows or Mac), not the web or phone
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
At a glance
Which apps can use it
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Related guides
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account richer-richard, which owns the repo
- ✓ Pass
Still maintained
Code last changed 2 months ago
- ✓ Pass
Has a licence
Uses Apache-2.0
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Published vulnerabilities (OSV.dev)
Not checked: only npm and PyPI packages with a version can be checked
Makers: ask for a re-check or report wrong info
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/richer-richard-fenestra-mcp)Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
User reviews
No reviews yet
Compared with others in Developer toolsi
- More stars than 92% of the other 6182 servers in this category
- Published to the registry more recently than 18% of the other 6182 servers in this category
- Basic checks equal to or better than 99% of the other 6182 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Fenestra MCP safe?
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed 2 months ago, and the latest version (0.40.1) reached the registry 4 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
What can I use instead?
In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Similar alternatives
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Cloudflare MCP
Cloudflare MCP servers
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| This one Fenestra MCP | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Cloud or install on your computer |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | Yes | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| License | Apache-2.0 | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
fenestra
A UI stack built for the agent loop. Describe a UI as JSON, render it natively, and check it in CI. There's no compile step in that loop, and no flaky screenshots.
fenestra is a pure-Rust GUI framework. Its headless renderer is deterministic, which means people and AI coding agents can both look at what they built and prove it is right. It also speaks A2UI, the open Agent-to-UI standard — this is its first native Rust renderer (fenestra-a2ui). The widget kit and design system below are what that loop can produce.
[▶ Try the live demo](https://richer-richard.github.io/fenestra/) — the dashboard and widget galleries, running in your browser over WebGPU. No DOM and no CSS: every pixel is vello on wgpu, from the same code as the native window. There's also [the book](https://richer-richard.github.io/fenestra/book/) if you want the guided tour.
| Light | Dark |
|---|---|
*That hero shot is a real tool, not a mockup: examples/agent_dashboard.rs is a live dashboard over an AI coding session, with a virtualized feed, charts, and a live tail through the effect layer. The SaaS-style widget showcase lives on as examples/dashboard.rs:*
| Light | Dark |
|---|---|
There's no browser here, no webview, and no HTML or CSS parser. fenestra draws everything itself with [vello] on wgpu. It lays out with [taffy] (flexbox and grid) and shapes text with [parley].
On top of that sits a themed widget kit that looks like a polished modern web app: soft layered shadows, OKLCH color ramps, a real typographic hierarchy, transitions on hover and focus, and light and dark themes that both get first-class treatment.
Quickstart
use fenestra::prelude::*;
struct Counter { n: i64 }
#[derive(Clone)] enum Msg { Inc, Dec }
impl App for Counter { type Msg = Msg;
fn update(&mut self, msg: Msg) { match msg { Msg::Inc => self.n += 1, Msg::Dec => self.n -= 1 } }
fn view(&self) -> Element { col().p(SP6).gap(SP4).items_center().children([ text(self.n.to_string()).size(TextSize::Xl2).weight(Weight::Semibold), row().gap(SP3).children([ button("Decrement").variant(ButtonVariant::Secondary).on_click(Msg::Dec), button("Increment").on_click(Msg::Inc), ]), ]) } }
fn main() { fenestra::run(Counter { n: 0 }, WindowOptions::titled("Counter")) }
Run cargo add fenestra, paste that in, then cargo run. If you'd rather start from a template, cargo generate richer-richard/fenestra-template gives you one with a headless UI test and CI already set up.
The whole view is rebuilt, laid out and repainted on every redraw. There's no diffing and there are no macros, so everything autocompletes.
Agents can see what they build
Rendering (element tree, theme, size) to pixels is a pure function, and it runs without a window or display server:
use fenestra::shell::{SyntheticEvent, render_app, render_element};
// A picture of any element tree: let image = render_element(my_view(), &Theme::dark(), (800, 600)); image.save("preview.png")?;
// Or drive a full app with scripted input and look at the result: let image = render_app( &mut app, &[ SyntheticEvent::MouseMove { x: 50.0, y: 34.0 }, SyntheticEvent::MouseDown, SyntheticEvent::MouseUp, SyntheticEvent::Text("hello".into()), ], (800, 600), &Theme::light(), ); assert_eq!(app.value, "hello");
Headless rendering is deterministic (embedded fonts, fixed scale, reduced motion), which makes pixel-exact golden tests practical — fenestra's own widget kit is tested this way, on CI, with no GPU display attached.
The same pipeline backs a JSON authoring format called fenestra/1, for agents and tools that would rather not compile Rust. You describe a UI in JSON and fenestra-describe parses it into the same Element tree the builders produce. The format covers the whole kit: data tables, trees, popovers, command palettes, the OKLCH color picker, images, charts, and markdown.
From there you have a few ways in. fenestra render writes a PNG. fenestra preview opens a window that re-renders every time you save. And the fenestra-mcp server hands an agent the whole loop — render, query, interact, verify — as fourteen MCP tools, including render_a2ui. You can watch motion too, not just single frames: Harness::film (also fenestra film, also the MCP film_ui tool) captures a sequence with real motion turned on and composes it into one captioned filmstrip.
What a headless render does and doesn't cover. It renders a deliberate subset of what a live window shows. That subset is exactly what makes it deterministic, so it's worth knowing where the edges are.
Text uses the embedded fonts, so Latin comes out exact. The real monospace, CJK, emoji and RTL faces come from the OS, and those only show up in a real window. Motion is always forced to reduced. Pixels are referenced against macOS/Metal, with Linux/lavapipe allowed a wider tolerance. Scale isn't pinned — render_element_scaled runs the same two-pass pipeline at any device scale, so you can catch retina-only regressions like hairlines and blur radii headlessly as well.
Two things look different outside that path. The full Liquid-Glass optics (backdrop blur, edge lensing, adaptive vibrancy) only render in the headless golden path; a live single-pass window gives you the translucent tint plus the specular rim and sheen. On the web, copying out reaches the system clipboard but pasting in from other apps stays inside the app, glass matches the native live window, and AccessKit is still waiting on an upstream web adapter.
So headless is the right thing to trust for layout, semantics, color, and the large majority of pixels. Check non-Latin text, monospace, and full glass in a real window. ARCHITECTURE.md keeps the precise ledger.
Working with an AI agent? AGENTS.md is the manual for the build → render → look → verify loop (and llms.txt for context loaders).
Philosophy: web aesthetics without the web platform
The way the web *looks* — soft elevation, tinted neutrals, OKLCH ramps, spacing on a 4px grid, focus rings, easing in the 120–300ms range — is the best-tested visual language we have in software. The web *platform* is a heavy way to get hold of it.
So fenestra encodes that language as typed Rust values instead. A Theme is generated from a single accent hue. Spacing, radius, shadow and motion come from tokens. The builder vocabulary (row(), .p(SP4), .rounded(R_MD), .shadow(ShadowToken::Sm)) is small enough to memorize and regular enough that rust-analyzer — or a language model — can autocomplete it. Every widget routes every color through the theme, so flipping one Mode turns the whole app dark.
The kit
Every widget below ships in every state, in both themes.
Controls. Button, IconButton, Checkbox, Switch, Radio, Slider, SegmentedControl, Select, and a Color Picker with an OKLCH lightness×chroma pad, hue and alpha strips, and forgiving hex entry.
Text entry. TextInput (parley editing, clipboard, IME) and TextArea (multiline, auto-growing).
Surfaces and feedback. Tooltip, Modal (focus trap and backdrop), Toasts, Tabs, Card, StatCard, Badge, Avatar, StatusIndicator with a live pulse, Kbd key-caps, Skeleton loaders, Divider, Spinner, Table, Callout, and Progress — including a Material-3 Expressive wavy bar. Plus a vendored subset of Lucide icons.
Regenerate this corpus any time with cargo run --example gallery — it renders headlessly.
Motion
fenestra-motion renders frame-pure compositions headlessly, with no live window and no screen recorder involved. The same pipeline is what fenestra film and the MCP film_ui tool use to let an agent watch a transition play.
Below is a fenestra-charts bar chart, rebuilt every frame from rank-sorted, track-interpolated data:
cargo run -p fenestra-motion --example chart_race -- --mp4 renders this exact sequence — the lead changes hands partway through, verified structurally in the example itself, not just eyeballed. Two more shipped demos render the same way: a broadcast lower-third (examples/lower_third.rs) and a per-word title stagger (examples/title_stagger.rs).
Workspace
| Crate | Role |
|---|---|
fenestra | Facade: prelude, run(), examples |
fenestra-core | Element IR, theme/tokens, layout, text, paint, input, transitions |
fenestra-shell | winit + wgpu window runner and the headless renderer |
fenestra-kit | The themed widget kit, built only on core's public API |
fenestra-charts | Sparklines, line and bar charts — the reference third-party widget crate |
fenestra-markdown | CommonMark rendered as native fenestra elements |
fenestra-looks | Six ready-made design languages (product, editorial, terminal, console, warm-editorial, playful), applied in one call |
fenestra-describe | Parses fenestra/1 JSON into the same Element tree the builders produce |
fenestra-a2ui | A native Rust renderer for A2UI v0.9 — the open Agent-to-UI standard |
fenestra-render | The fenestra CLI: render, preview, film, query, verify, lint — from the command line |
fenestra-mcp | MCP server exposing render, query, interact, and verify as fourteen tools to AI agents |
fenestra-motion | Frame-pure motion graphics: timelines, headless frame/video rendering, temporal lints, the motion CLI |
fenestra-anim | Keyframe animation math — easing, springs, an exact rational timebase |
fenestra-anim is versioned on its own (0.1.x