grafty
App demosFor teamsFor ITFor engineeringHow it worksComparePricingBlog
Interactive demoBook a live demo

For engineering

Build from any agent. Ship on your own network.

The rest of the company builds in Grafty's shared chat. You don't have to leave your editor: Grafty's MCP server lets your agent find apps, pick up comments, request changes and publish, with a preview before anything goes live.

See the MCP server Book a technical demo

MCP server

Build from any agent. Ship on your own network.

Your developers already live in Codex, Claude Code and Cursor. Grafty includes an MCP server, so any MCP client can work with your Grafty instance directly: pick up a teammate's comment, fix it, reply on the thread and publish, without leaving the editor. Sign-in follows the MCP authorization spec (2025-11-25).

  • Read and reply to team comments, with the element each comment points at
  • Create apps and request changes, then wait on or cancel the build
  • Find apps, read their files and history, and use Team chat
  • Check GitHub sync status and resync
  • Preview first, then publish: Grafty returns a preview and a confirmation code, and nothing goes live until the agent sends that code back

Works with

  • Codex
  • Claude Code
  • Claude custom connectors
  • Gemini CLI
  • VS Code
  • Cursor
  • Devin
  • Pi
  • any MCP client

Feedback arrives as comments, not tickets.

Teammates pin comments on the live preview. Your agent reads each comment with the element it points at, makes the change and replies on the thread.

Code and history stay in your Git.

Source code and Git history live inside your network. Check GitHub sync status and resync from the agent you already use.

Your models, your keys.

Builds call the providers your company approved, with your keys: OpenAI, Anthropic, Google Gemini, OpenRouter or a self-hosted model.

Live preview

Point at it. Comment. Ship it.

Not everyone writes prompts. Click any element in the live preview to reference it in chat, or pin a comment on it, like Figma, but on a running app. Send to Builder turns the comment into a change, immediately.

  • Select any element and reference it in a prompt
  • Pinned comments with replies, Open/Resolved, team-only visibility
  • Desktop, tablet and mobile previews, and every revision kept
A dashboard card selected in the live preview and referenced in the chat composer
A pinned comment on the live preview with a reply and the Send to Builder action

Bring your own provider - or run fully local

  • OpenAI
  • Anthropic
  • Google Gemini
  • Mistral
  • DeepSeek
  • Moonshot Kimi
  • Meta Llama
  • xAI Grok
  • Cohere
  • Perplexity
  • Qwen
  • Hugging Face
  • Groq
  • Together AI

Start small

Start with one team.

You don't need a company-wide rollout to find out whether Grafty works for you. Prove it with one team, alongside your security review.

  • 1 instance
  • Up to 5 users
  • Per-user token budgets
  • Standard legal docs
Start a pilot
  1. 01

    Pick one team and one workflow.

    Start with the report, tracker or process that people rebuild by hand every week.

  2. 02

    Run Grafty in your environment.

    A pilot runs as one instance on a single server, connected to your own model keys.

  3. 03

    Build together, review together.

    The team builds real apps while your security team reviews models, budgets, access and the audit trail.