Integration / Cursor
Sign up and sign in to websites from Cursor
Add Trusty Squire to Cursor, restart it, and ask for the signup, configuration, or credential outcome your app needs.
npx @trusty-squire/mcp@latest connect --target=cursorInstallation guide →Ask for the outcome
“Sign me up for Resend and save the API key.”
“Configure PostHog and Sentry for this app.”
“Give this deployed app revocable API access.”
How it works
- 01
Run the Cursor target
The connect command signs the machine in and merges a squire server into ~/.cursor/mcp.json.
- 02
Restart Cursor
Close and reopen Cursor so its MCP client loads the server and exposes the Trusty Squire tools.
- 03
Ask from the coding task
Tell Cursor what website outcome the project needs. It can plan the steps and use Trusty Squire to act on the real site.
What to know
Cursor’s MCP file is merged, not replaced
Cursor reads this server from ~/.cursor/mcp.json. The installer reads the existing mcpServers map, updates the squire entry, and writes the other entries back with it. You do not need to paste a JSON block into Cursor by hand.
Rerun connect when the session changes
The same command can refresh the Cursor configuration. If the browser login is stale or you want to use a different connected account, rerun it with --force-relogin, then restart Cursor once more.
Website work stays part of the coding task
Cursor can move from implementing an integration to requesting the provider setup it needs without sending you to hunt through dashboards. Trusty Squire supplies the browser session and the credential-safe path; Cursor remains the planner for the project outcome.