Recoup MCP server
Commit Nov 14, 2026Enables AI agents to perform artist research, manage music catalogs, create release plans, and handle music industry content workflows.
Also known as recoupable/api, api
- Stars
- 2
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.0.0
- Last commit
- Nov 14, 2026
- License
- —
What is Recoup MCP?
Recoup enables AI agents to perform artist research, manage music catalogs, create release plans, and handle music industry content workflows.
Summary generated from the project's README
About Recoup MCP server
Recoup provides a specialized API service designed to connect AI agents with music industry workflows. It enables automated tasks such as artist research, music catalog management, and the creation of release plans. Developers can use this server to integrate agents into existing professional environments, including Slack, GitHub, and WhatsApp.
The system architecture relies on a Next.js 16 framework and uses Supabase for database access. To set up a local development environment, you need Node.js 22 and pnpm 9. The service manages complex state and background tasks through Redis and Trigger.dev callback contracts. It also includes specific integration capabilities for coding agents and handles delegated access through an MCP OAuth runtime. Users must configure specific services via local environment files or deployment secrets to connect to necessary providers.
What you can do with it
- 1Workflow Automation via Slack or GitHubAn agent can interact with music industry content workflows through communication and version control platforms.
Written from the project's README. Every use case is checked against a quote from it.
How to install Recoup MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Recoup MCP in Claude Code
$ claude mcp add --transport http api https://api.recoupable.dev/mcpInstall Recoup MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"api": {
"url": "https://api.recoupable.dev/mcp"
}
}
}Install Recoup MCP in VS Code
.vscode/mcp.json
{
"servers": {
"api": {
"type": "http",
"url": "https://api.recoupable.dev/mcp"
}
}
}Install Recoup MCP in VS Code CLI
$ code --add-mcp '{"name":"api","type":"http","url":"https://api.recoupable.dev/mcp"}'Install Recoup MCP in Codex
$ codex mcp add api --url https://api.recoupable.dev/mcpInstall Recoup MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.api] url = "https://api.recoupable.dev/mcp"
Install Recoup MCP in Gemini CLI
$ gemini mcp add -s user --transport http api https://api.recoupable.dev/mcpInstall Recoup MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"api": {
"url": "https://api.recoupable.dev/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablerecoupable/api is public and reachablegithub.com/recoupable/api ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-11-13github.com/recoupable/api ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubRecoup 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:
pnpm install --frozen-lockfile
pnpm 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:
| Command | Purpose |
|---|---|
pnpm dev |
Build the MCP extension, then start Next.js development mode |
pnpm build |
Build the extension and Next.js, then check the OAuth provider build |
pnpm test |
Build the extension, then run Vitest |
pnpm test:watch |
Build the extension, then start Vitest watch mode |
pnpm lint / pnpm lint:check |
Run ESLint with / without fixes |
pnpm format / pnpm format:check |
Format / check supported source and Markdown files |
Architecture and guides
- Contributor instructions: authentication, validation, database boundaries and PR workflow. New PRs target
main; the oldteststaging 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.
- Data ingestion: private bronze/silver/gold processing, API/MCP operations and external database delivery.
- 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.
Recoup MCP questions
How do I add Recoup MCP to Claude Code?
Run claude mcp add --transport http api https://api.recoupable.dev/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Recoup MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How do I set up the coding-agent integration?
You should follow the Coding-agent setup guide, which covers Slack, GitHub, WhatsApp, Redis state, and Trigger.dev callback contracts.
Does the server support OAuth?
Yes, the server includes an MCP OAuth runtime for discovery, consent, and delegated access.