recoup-platform-connect-account

Imported from recoupable/skills (skills/recoup-platform-connect-account/SKILL.md). Install upstream with npx skills add recoupable/skills --skill recoup-platform-connect-account. Copyright stays with the author.

Recoup — Connect Account

Connect through the host's Recoup MCP integration at https://api.recoupable.dev/mcp. The host handles OAuth, callbacks, credential storage and refresh. The plugin contains no account credentials.

Procedure

1. Discover the available Recoup tools. Tool prefixes vary by host; match their names, descriptions and schemas rather than assuming a fixed prefix.
2. If list_artists is available, call it to verify access. A successful empty list is a valid connection, not proof of a bad account. Never invent a roster.
3. If authentication is required, direct the user to the host's Recoup connection controls. In Claude Code, open /mcp and authenticate the plugin's Recoup server. On other hosts, use their MCP/plugin connection UI. Let the user complete browser sign-in and consent; never ask them to paste an OAuth token. If the customer does not have a Recoup account, say: "Create your Recoup account at https://chat.recoupable.dev, then come back here and connect Recoup." Preserve their original task and continue it after connection. Account creation is separate from a subscription or credit purchase; do not direct them to pricing, checkout or an upgrade as part of connecting.
4. For the full business catalog, approve mcp:tools in the consent flow. This covers accessible personal and organization workspaces and includes writes, deletion, messages, publication and paid generation. Existing limited grants do not expand silently: reconnect for broader consent and refresh tools.
5. Verify with list_artists again. Use the returned artist identifiers for the next task. If multiple workspaces could fit, clarify the intended workspace.
6. Report connection success only after the read succeeds. Continue the user's requested task without creating an extra account or asking for an API key.

REST-only or skills-only fallback

npx skills add installs instructions; it does not provision a host MCP connection. Configure the endpoint above in the host if MCP is supported.

Some REST operations and bundled scripts are not available through MCP. For those, use an existing RECOUP_API_KEY or host-provided RECOUP_ACCESS_TOKEN. Keep REST authentication separate from the MCP OAuth connection; never export MCP credentials, substitute its access token into curl, or claim all REST endpoints are covered by the MCP catalog.

If no separately configured REST credential exists, preserve the job and explain which REST-only capability is unavailable. Let the customer complete account and credential setup through Recoup's supported controls outside the conversation. Never solicit or process an emailed PIN, password, API key or OAuth token in chat. Do not create accounts or extract credentials through another connected tool. When a host supplies an authorized secret, verify with GET /api/accounts/id before continuing. Do not edit shell startup files or global agent instructions.

Existing entitlements only

Use the account's existing features and credit balance. On an entitlement or credit failure, retain the job and explain the unavailable feature neutrally. Do not display plans, link to checkout or upgrade pages, initiate subscriptions, save payment methods, buy credits or trigger automatic credit purchases.

Boundaries

• Missing environment variables do not invalidate a working MCP connection.
• Credentials, PINs and tokens never belong in the plugin, source control, or output.
• Tool availability is not permission to send, publish, delete or spend without the user's applicable authorization. Follow the tool's disclosed constraints.
• Connections remain usable until disconnected or revoked, subject to successful host token refresh. If refresh fails, use the host's reconnect flow.