Verify your connection

After you connect an editor or agent, the Connect page can confirm your agent is actually reaching your design system, not just that our gateway is up.

Copy link to sectionWhy this exists

Setting up an MCP connector means pasting a command or config into your tool. That tells your tool where preset AI is, but nothing tells you it worked until your agent makes a real request. The Verify it's working section closes that gap.

Copy link to sectionHow to verify

1. On Connect, find Verify it's working, just below the Editors & agents list.
2. Copy the prompt and paste it to your AI agent (Claude Code, Cursor, Codex, and so on). It asks your agent to look up how you style a primary button using the preset tools.
3. When your agent runs it, a request reaches your design system. The section updates to Verified, showing which tool ran and when.

Running the prompt also shows you what the connection buys: your agent returns your real tokens, not generic ones.

Copy link to sectionWhat "Verified" means (and doesn't)

Verified means a real request reached your design system. It names the tool that ran (for example search_design_system) and when it arrived. Connections that use an API key also show which key; browser-authenticated connections (the default for Claude Code, Cursor, VS Code, and Gemini) have no key, so none is shown.

It does not name which editor sent the request. preset AI records the request and the tool, not the client application, so we never claim a specific editor is "connected". We only confirm that your design system received a genuine request.

Copy link to sectionIf nothing happens

If you don't see a request after a minute:

• Make sure your tool is actually running the preset MCP server. Restart it if you just added the config.
• Paste the prompt again.
• Check the status line at the top of Connect. If it doesn't say gateway online, the problem is the gateway or your network, not your setup, so retrying shortly usually resolves it.