SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to connect withPICA to Claude

Connect Claude Web, Desktop and Cowork to withPICA MCP. List all works missing songwriter credits, generate royalty report for last quarter, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
withPICA logowithPICA
Api Key

withPICA is a music rights and catalog platform for managing works, recordings, credits, agreements, royalties, collaborators, and related assets. Use it to track rights, automate royalty calculations, and manage collaborators across releases.

10 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your withPICA account to Claude via Composio Connect, enabling it to list all works missing songwriter credits, generate royalty report for last quarter, create agreement for new collaborator on track, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate withPICA with

ChatGPTHermesAtomic Agent

Connecting withPICA to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your withPICA account

Back in Claude, ask it to connect to withPICA or give it any withPICA-related task.

For example, ask Claude to:

  • "List all works missing songwriter credits"
  • "Generate royalty report for last quarter"
  • "Create agreement for new collaborator on track"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your withPICA account is ready to use.

What is the withPICA Claude Connector, and what's possible with it?

The withPICA MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your withPICA account. It provides structured and secure access to your music catalog, recordings, people, agreements, projects, and sessions, so your agent can review catalog health, browse musical works, search recordings, inspect agreements, and find collaborators on your behalf.

  • Catalog overview and priorities: Have your agent review your organisation, catalog totals, catalog health, and current priorities.
  • Works and recording discovery: Instruct your agent to browse musical works or search recordings by title, artist, or ISRC.
  • Agreement review: Let the agent find agreements by signature or expiry status and show the agreement templates available to your organisation.
  • People and collaborator lookup: Direct your agent to search your catalog for people and retrieve detailed information about a chosen collaborator.
  • Project and session visibility: Have your agent list projects and recording or creative sessions in your organisation.

Troubleshooting

1. Why does Claude not use the Composio connector for withPICA?

The connector can show as connected, but Claude must use it in each withPICA conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to withPICA again.

2. Why does Claude show an MCP server error before withPICA connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for withPICA.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect withPICA.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the withPICA authorization link not work?

The Composio connector is one server. Your withPICA account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the withPICA connection.
  • Composio creates a fresh withPICA authorization link.
  • Open that link in your browser and finish the withPICA sign-in.

4. Why do withPICA actions fail after they worked before?

The withPICA connection can expire or lose permission.

  • Ask Claude to inspect the withPICA connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the withPICA account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in withPICA.
  • If the action still fails with a permission error, check that the connected account has that permission in withPICA itself.

5. How do I switch to a different withPICA account?

Claude can manage the withPICA connection for you.

  • Ask Claude to disconnect or delete the current withPICA account.
  • Ask Claude to connect withPICA again.
  • Open the new Composio authorization link for withPICA.
  • Sign in with the other withPICA account in the browser.
  • After the account connects, ask Claude to retry the withPICA task.

6. Why is my withPICA connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your withPICA connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click ⋮ and click Clear cache.
  • If withPICA tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect withPICA.
TOOLS

Supported Tools

Every withPICA action and event your agent gets out of the box.

Get Current User

Return the connected withPICA user's profile and linked catalog person ID.

Get Person

Return detailed catalog information for one person by ID.

Get Workspace Context

Return the connected organisation, catalog counts, health summary, and current priorities.

List Agreements

Search and filter agreements, including signature and expiry states, one page at a time.

List Agreement Templates

Return the active and system agreement templates available to the organisation.

List People

Search and filter people in the organisation's catalog, returning one page and a continuation cursor.

List Projects

Return a bounded list of projects in the connected organisation.

List Sessions

Return a bounded list of recording or creative sessions in the connected organisation.

List Works

Return a bounded page of musical works in the organisation's catalog.

Search Recordings

Search recordings by title, artist name, or ISRC and return one result page with recovery guidance.

FRAMEWORKS

How to build withPICA MCP Agent with another framework

ChatGPT logo

ChatGPT

Use withPICA MCP with ChatGPT

Hermes logo

Hermes

Use withPICA MCP with Hermes

Atomic Agent logo

Atomic Agent

Use withPICA MCP with Atomic Agent

FAQ

Frequently asked questions

With a standalone withPICA MCP server, the agents and LLMs can only access a fixed set of withPICA tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from withPICA and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right withPICA tools.

Yes, absolutely. You can configure which withPICA scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your withPICA data and credentials are handled as safely as possible.

Start with withPICA.It takes 30 seconds.

Managed auth, hosted MCP servers, and every withPICA tool your agent needs.Free to start.

Start building