Recoup: AI agents for the music industry

dev.recoupablePublished by recoupable.devOfficial publisherv1.0.0Updated Nov 6, 2026

Music industry tools for AI agents: artist research, catalogs, release plans and content.

VerifiedStreamable HTTPWeb executableBusiness & CommerceMedia & Design

Overview

AI-generated overview

Remote Recoup MCP server giving AI assistants music-industry tools for artist research, catalogs, release plans and content.

What you can do
  • Research artists and music-industry information
  • Work with catalogs and release plans
  • Produce and manage music-related content
  • Connect to Recoup's artist, account, chat and agent workflows through an OAuth-protected API
When to use it
Useful when an assistant needs to work on music-industry tasks such as researching artists, organizing catalogs or drafting release plans and content, without building your own integration to Recoup.
Requirements
A remote MCP endpoint at api.recoupable.dev using streamable HTTP; OAuth authentication is required, so a Recoup account and consent flow are needed. No environment variables or headers are declared.
Before you install
Access is delegated through OAuth, so the assistant acts on your Recoup account; review what scopes you grant. The README mentions x402 payment integration and protected routes, so some routes may involve payments or spending. Data is exchanged with Recoup's hosted service.

Installation

In SourceWeft

  1. Open Recoup: AI agents for the music industry in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.recoupable%2Frecoup/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "recoup-ai-agents-for-the-music-industry": {
      "type": "http",
      "url": "https://api.recoupable.dev/mcp"
    }
  }
}

README

Recoup API

Next.js 16 API service for Recoup's artist, account, chat and agent workflows. Routes live in app/api/; domain logic lives in lib/. Database access belongs in lib/supabase/.

Local development

Use Node.js 22 and pnpm 9 (the Node 22 compatibility workflow uses pnpm 9). From this repository:

sh
pnpm install --frozen-lockfilepnpm dev

Configure only the services required by your work through an ignored local environment file or your deployment's secret configuration. This repository is an API service, not the old x402 example workspace: no parent-directory build or Ethereum wallet is required just to install dependencies. Starting routes that import service clients can require their configuration and connect to providers.

For the coding-agent integration, follow Coding-agent setup before starting or exposing its routes. That guide covers Slack, GitHub, optional WhatsApp, Redis state and the existing Trigger.dev callback contract.

Commands

These are the scripts in package.json:

CommandPurpose
pnpm devBuild the MCP extension, then start Next.js development mode
pnpm buildBuild the extension and Next.js, then check the OAuth provider build
pnpm testBuild the extension, then run Vitest
pnpm test:watchBuild the extension, then start Vitest watch mode
pnpm lint / pnpm lint:checkRun ESLint with / without fixes
pnpm format / pnpm format:checkFormat / check supported source and Markdown files

Architecture and guides

  • Contributor instructions: authentication, validation, database boundaries and PR workflow. New PRs target main; the old test staging flow is retired.
  • Coding-agent setup: current webhook, callback and shared-state behavior.
  • MCP OAuth runtime: OAuth discovery, consent and delegated access.
  • Response contracts: shared schemas and published contract checks.
  • proxy.ts and lib/x402/: request middleware and x402 payment integration. Consult these sources for protected routes and payment behavior.

New background/scheduled platform work uses Vercel Workflows inside this API. The coding-agent and update-pr integrations documented here still call existing Trigger.dev tasks; documenting them does not migrate or deploy those workers.

Source: README.md at commit 3bd97f4

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 6, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.