The native desktop app
Mac and Windows. Chat to build, design, and read analytics. Auth and AI run in the app — no subscription, no setup.
- Builder · Design Studio · Dashboard
- Design preview + Open in Studio
- Hosted AI — nothing to configure
Work inside the MCPWing app, or point your own AI at it. Either way you drive the same projects, designs, tickets, and releases.
Add MCPWing to Claude Code, Cursor, or the Claude app. You approve the connection right in the desktop app — then your AI has Wing's 30 tools and your full project context.
An app wants to access your MCPWing project context on your behalf. Access is scoped to projects you can already see.
Build is a project-scoped agent. Watch it pick a project, link the subproject, design and ticket, attach a local folder, ship the feature, push the git changes, and open the code — all in one chat.
Scope a subproject, link its design, then iterate in plain English. Approve and it uploads as a new version — comments and all.
Stop building a dashboard for every team. Every system you own already has an API — MCPWing turns each into an MCP tool your AI speaks, so anyone can just ask: usage, tool calls, trends, answered with live tool responses.
Everything the agent touches, you can drive by hand — projects and subprojects, the kanban board, design versions, org members and budgets, MCP keys, audit. Browse a design version and hand it straight to the AI designer with Open in Studio.
Briefs, designs, builds, releases, analytics — every stage of a feature, in the same place. No more handoff folders, no Slack threads to find the spec, no "wait, who owns this?"
Anyone in the org can drive a feature end-to-end. Roles control access, not capability — and admins fund an org budget in USD, then grant per-user agentic access from a shared pool.
Owns members, teams, SSO, audit, billing, and every project. The customer-side power user.
Sets vision and writes the brief on any project they can read. Aligns Product, Design, and Engineering.
Creates projects (forced Org-wide by default), uploads designs, ships builds, owns work end-to-end.
Six pieces that compose into one workspace. Use any subset — they share the same org, role, budget, and audit model.
Beyond driving MCPWing, you can publish your own APIs as MCP. Your Postman or OpenAPI spec becomes a hosted server every LLM can call. We orchestrate. You own the API and the data.
Every outbound call sandboxed against private IPs, DNS rebinding, and internal-net hops. Per-tenant rate limits.
Drop in your example responses. We auto-detect OTP → verify, JWT extraction, OAuth, session-ID propagation. No glue code.
Rotatable mcpw_<id>_<secret> tokens, scoped to one project. Invocation logs are metadata-only — never payloads.
We tell you what you can use today, what’s a few weeks out, and what we’re building toward. No vapourware.
Download the app and connect Wing MCP free. Turn on hosted AI by funding an org budget — usage-metered, no subscription.