New Practice lessons are live in the Playground.See what you can learn
← All posts

Guides · Nov 12, 2026

Add an MCP UI check to Cursor or Claude Code

Connect to Xpensiv over MCP, check a public app URL, and bring the findings into your coding session before you edit.

To add a UI check to Cursor or Claude Code, connect Xpensiv at https://mcp.xpensiv.si, authenticate, and ask your coding agent to check a public app URL. The MCP tools are check_app, get_check and list_checks. Your agent can read the findings in the same session where you work on the code.

Sign in to the console and open Connect your agent for the ready-made configuration for your client. The API docs describe OAuth metadata and API-key authentication for developer clients. If you use an API key, copy it when it appears; it is shown only once. Keep it in your client's authentication settings.

Once connected, ask the agent to run check_app on the deployed page you want to inspect. Read the returned findings and screenshots before asking for edits. Xpensiv checks public pages, so use a URL the service can open in its browser.

Choose a finding and ask the coding agent to make that specific change in a branch. Inspect the diff and the rendered page before approving the change. Xpensiv returns findings; you control the edits in your coding tool and the decision to merge.

After deploying the edit, check the updated URL again and compare the finding with its earlier screenshot. If you prefer an HTTP integration, the API docs provide separate requests to start a check, poll its status and fetch the result.

Product details: /docs/api · /how-it-fits-your-workflow · /you-approve-every-change