AI SummaryRun this right after installing the Well plugin, or whenever the Well tools aren't responding. Walk the user through it conversationally — do not dump all steps at once if a step is already done. Installing the plugin auto-adds the MCP server (it is bundled in the plugin manifest). If the user just
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "connect" skill in my project. Please run this command in my terminal: # Install skill into your project mkdir -p .claude/skills/connect && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/connect/SKILL.md "https://raw.githubusercontent.com/WellApp-ai/Well/main/plugins/well/skills/connect/SKILL.md" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
Description
Connect and verify the Well MCP — authenticate, confirm the tools work, and show what to ask. Use when the user runs /well:connect, just installed the Well plugin, or says the Well connection/MCP "isn't working" / "nothing happened".
Connect to Well
Run this right after installing the Well plugin, or whenever the Well tools aren't responding. Walk the user through it conversationally — do not dump all steps at once if a step is already done.
1. Confirm the MCP server is registered
Installing the plugin auto-adds the well MCP server (it is bundled in the plugin manifest). If the user just installed it, make sure it's active: • Tell them to run /reload-plugins if they haven't since installing. • The server should now appear when they run /mcp.
2. Authenticate (one time, browser sign-in — no API key)
The Well MCP uses OAuth, so the first connection needs a one-time sign-in: > Run /mcp, select well, and choose Authenticate. A browser opens — sign in to your Well account and approve. No API key, no config. If /mcp shows well as already authenticated, skip this.
3. Verify it works
Call well_get_schema (no arguments) to confirm the connection is live. If it returns the list of roots (companies, invoices, transactions, ledger_accounts, …), the connection is working — tell the user "Connected ✓, N data types available." If it returns an auth error, send them back to step 2. If it returns a server error on the heavy roots, the connection is fine but the workspace data path may be temporarily unavailable — say so rather than implying the setup failed.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster