Connect an agent

Use this URL in your agent's remote MCP settings:

https://api.recoupable.dev/mcp

Select OAuth. Recoup supports published client metadata (CIMD) and automatic registration (also called Dynamic Client Registration or DCR). Sign in to your existing Recoup account and allow the requested access. No API key or client secret needs to be copied.

What your agent can do

Request mcp:tools for the full catalog: a scope-dependent catalog covering artists and socials, catalogs, chats, scheduled tasks, research/search, Spotify, YouTube revenue, image/audio/video operations, files, Context, Sites, email and support.

The consent screen explains that this permission includes reading, creating, editing and deleting data, sending messages, publishing content, and using paid generation tools. It covers personal and organization workspaces your account can access. Resource ownership is checked on each call. Private conversations and scheduled tasks remain account-bound.

Existing limited grants do not expand automatically. Reconnect with mcp:tools, review the broader permission, and refresh your client's tool catalog. Clients requesting the mcp:read + mcp:write pair keep the five-tool experience.

OAuth never exposes get_api_key: it does not return bearer credentials to the model. Composio integrations and sandbox execution are separate from the registered Recoup MCP catalog.

Email uses the same recipient restrictions as the API and checks any referenced conversation's owner. Review recipients and content before sending. create_knowledge_base and generate_txt_file publish to permanent public Arweave storage: use only content explicitly approved for that destination, never confidential material. Video generation returns an account-bound id; pass that entire value as video_id to the retrieval tools. Older raw provider video IDs cannot be used with OAuth. Task-run status requires verifiable caller ownership and returns status fields, not raw provider payloads or logs.

The platform verification results below describe the original five-tool catalog unless explicitly stated otherwise. They do not establish full-catalog production verification.

New connections stay authorized until you disconnect them, including when inactive. Five-minute access tokens renew through rotating refresh tokens. Disconnect an agent from Connected agents to revoke its access and refresh tokens immediately.

Connections approved under the previous 30-day policy keep their original expiration. Reconnect once to approve access until disconnected.

Claude

1. Open Customize → Connectors → Add custom connector.
2. Name it Recoup and enter the MCP URL above.
3. Choose Sign in now. Register automatically uses DCR; published identity uses CIMD. The production client tests below used DCR.
4. Connect, sign in to Recoup, and select Allow access.
5. In a new chat, ask Claude to list your Recoup artists. Review individual tool-use approvals when prompted.

Claude web was tested against production on October 7, 2026: connection, five-tool discovery, artist read, temporary artist creation/update/readback, artist socials, and another read after access-token expiry passed. The temporary artist was removed afterward.

Claude Desktop 2.26454.0 was also tested on October 7, 2026 using the same authorized connector: tool discovery, artist listing, temporary artist creation/update/readback passed. The test artist was removed afterward. Separate disconnect/reconnect checks are still pending. Local stdio configuration is a different transport. See Claude's remote connector guide.

ChatGPT

In the interface tested on October 7, 2026:

1. Open Plugins → Add → Add custom MCP server.
2. Enter Recoup, the MCP URL, and OAuth.
3. Under advanced OAuth settings, confirm Dynamic Client Registration (DCR) and request mcp:tools for full access.
4. Create the plugin, connect it, and complete Recoup consent.
5. Start a chat with Recoup enabled and request an artist list.

ChatGPT web was tested against production on October 7, 2026: OAuth login, artist listing, and temporary artist creation/update/readback passed. The temporary artist was removed afterward. Refresh and disconnect/reconnect checks are pending. Workspace policy and account access may limit custom integrations. UI labels can differ; see OpenAI's MCP setup documentation.

Codex

codex mcp add recoup --url https://api.recoupable.dev/mcp
codex mcp login recoup --scopes mcp:tools

Complete the browser sign-in and consent, then ask Codex to list your Recoup artists. Codex CLI 0.161.0 passed production OAuth login and an actual list_artists call on October 7, 2026. Version 0.145.0 failed issuer-response validation; upgrade if using that version. Writes, refresh, and disconnect/reconnect remain unverified in Codex. Desktop and IDE surfaces must be verified separately. See Codex MCP configuration.

Cursor

Add a remote server to your project's .cursor/mcp.json:

{
  "mcpServers": {
    "recoup": {
      "url": "https://api.recoupable.dev/mcp"
    }
  }
}

Open Cursor's MCP settings and authenticate. Cursor Desktop passed production OAuth connection, five-tool discovery, and an actual list_artists call on October 7, 2026. Writes, refresh, disconnect/reconnect, and Cursor web/agent journeys remain unverified. See Cursor's MCP guide for the current setup and workspace restrictions.

Other agents and callbacks

Use a remote Streamable HTTP MCP client supporting OAuth discovery, authorization code flow with PKCE S256, and DCR. Recoup publishes:

• Resource metadata: https://api.recoupable.dev/.well-known/oauth-protected-resource/mcp
• Authorization-server metadata: https://api.recoupable.dev/.well-known/oauth-authorization-server/api/oauth
• Resource: https://api.recoupable.dev/mcp

Register the exact callback used by your client. Registration binds callbacks to that client; there is no shared wildcard callback list. Hosted callbacks use HTTPS. Native clients use validated loopback callbacks. Do not substitute localhost for 127.0.0.1 or edit a callback after registration.

A generic MCP SDK client has passed production reads, writes, refresh rotation, and revocation. That does not prove every agent surface. CIMD uses the same consent and permissions; see CIMD requirements and verification status. Full-tool consent includes accessible organization workspaces; the original limited grants remain personal-only.

Additional client setup paths

The following paths were reviewed in official client documentation on October 7, 2026. They have not been tested end to end against Recoup. Use automatic registration and request mcp:tools for full access, or mcp:read / mcp:write for the limited personal tools. The client registers its callback; you do not need a Recoup platform-specific callback allowlist.

Documented compatibility is a setup starting point. A successful connection still needs an actual tool call before it can be considered verified. Refresh and disconnect/reconnect should be checked before relying on unattended access.

Disconnect

Open Connected agents and disconnect the selected agent. Future requests and refreshes stop; already completed changes remain. Other connections are independent. Reconnect from the agent when you want to grant access again.

Troubleshooting

For clients without OAuth, API-key authentication remains available. Keep keys out of model prompts and shared configuration. A stdio-only client needs a separately maintained adapter; the remote URL is not itself a stdio command.

For help, contact agent@recoupable.dev. Include the client name, time, and error text; never include tokens, passwords, or API keys.

Full OAuth MCP calls currently share account-level limits of 120 calls per minute and 30 calls per tool per minute across connected clients. See the pinned rate-limit implementation. The compact_chats MCP tool accepts up to 50 chats per call under the pinned MCP guard; this is an MCP limit, not a claimed REST request limit.