Integration / Claude Code
Sign up and sign in to websites from Claude Code
Connect Trusty Squire to Claude Code, then describe the website outcome you want. The installer merges the squire server into Claude's existing MCP configuration.
npx @trusty-squire/mcp connect --target=claude-codeInstallation guide →Ask for the outcome
“Add Google OAuth in one prompt.”
“Add Stripe payments in one prompt.”
“Go live: deploy, custom domain, and SSL.”
How it works
- 01
Run the Claude Code target
The connect command opens the Trusty Squire sign-in flow and writes an MCP server named squire to ~/.claude.json.
- 02
Restart Claude Code
A fresh session loads the new MCP server and its website-operation and credential tools.
- 03
Ask for the finished outcome
Name the website and what your project needs. Claude can plan the job and drive Trusty Squire one browser step at a time.
What to know
Files the installer updates
Claude Code reads MCP servers from ~/.claude.json. The installer merges a squire entry into that file and preserves the other server entries it can read. It also adds safe, frequently used credential tools to ~/.claude/settings.json. Destructive or exposing paths stay on Claude Code’s normal confirmation behavior.
Reconnect without rebuilding the config
Running the same connect command again refreshes the Trusty Squire entry. If the browser identity is stale or you need to switch accounts, rerun it with --force-relogin. Restart Claude Code after a config change so the server is loaded again.
Claude plans; the squire operates
Claude keeps the development goal in context. Trusty Squire supplies the scoped browser and credential boundary needed to finish work on the real website. You can observe progress and step in when a site needs a decision that should be yours.