← Browse

@wellapp-ai/connect

A

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".

skillclaude

Install

agr install @wellapp-ai/connect --target claude

Writes 1 file into .claude/skills/, pinned to git-eb7d7216.

  • .claude/skills/connect/SKILL.md

Document


name: connect 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". disable-model-invocation: false

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.

4. Show what to ask

Once connected, offer 3 concrete starting prompts so the user gets value immediately:

  • "Summarize last month's cash flow"
  • "List my unpaid invoices over €5,000"
  • "Build my compte de résultat for the last quarter"

Mention the deeper skills are available too: /well:reconciliation, /well:vat-summary, /well:ar-aging, /well:month-end-close, /well:compte-de-resultat, /well:balance-sheet, /well:cash-flow-forecast.

Note on billing

Tool calls use Well credits, billed to the workspace plan. Mention this once if the user asks about cost — do not interrupt every call.

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-eb7d7216d7822026-07-31