How to integrate withPICA MCP with Atomic Agent

Connect Atomic Agent 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.

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

Atomic Agent is an open-source AI agent that runs on your machine and supports local models through llama.cpp. Connect it to 1,500+ apps through Composio, including withPICA.

This guide uses Atomic Agent's built-in Composio integration. You need Atomic Agent v0.5.6 or later, your own Composio API key, and a withPICA account. See the Atomic Agent documentation for installation instructions.

Also integrate withPICA with

How Atomic Agent connects to withPICA

Atomic Agent connects to Composio's Tool Router over Streamable HTTP MCP. It discovers the tools needed for your request, and Composio handles account authentication.

Execution and account-connection tools follow Atomic Agent's configured approval policy. Review any approval prompt before allowing an action on your connected account.

Connect withPICA to Atomic Agent

  1. Sign up or sign in to the Composio dashboard. Copy your API key.
  2. In Atomic Agent, open the Integrations tab and select Composio. Select API key, press e, paste the key, and press Enter. The tools become available immediately, without a restart.
  3. Ask Atomic Agent to do something in withPICA. It searches Composio for the right tool.
  4. On first use, open the sign-in link returned in the chat. Connect your withPICA account, then return to Atomic Agent to continue.

Headless setup

Add the following line to ~/.atomic-agent/.env, replacing YOUR_COMPOSIO_API_KEY with your key. Start Atomic Agent after saving the file.

bash
COMPOSIO_API_KEY=YOUR_COMPOSIO_API_KEY

What is the withPICA MCP server, 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.

Use withPICA from Atomic Agent

With your account connected, ask Atomic Agent to work with withPICA in natural language. You can connect more apps through the same Composio integration as you need them.

Visit the Atomic Agent website or inspect the Atomic Agent source code.

Troubleshooting

Why is my API key rejected?

Copy the key directly from the Composio dashboard. Atomic Agent requires ASCII characters because it sends the key in an HTTP header. Remove any extra characters introduced when copying.

Why are Composio tools unavailable after saving a key?

Check that you use Atomic Agent v0.5.6 or later and that Composio is enabled in your configuration. A "composio": { "enabled": false } setting disables the integration while keeping the saved key on disk.

Does Composio have a free plan?

The Hobby plan includes 100,000 tool calls per month. Composio-managed OAuth apps have a lower included allowance. See Composio pricing for the current limits that apply to your connection.

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.

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. Atomic Agent 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