Pica

io.github.withpicaPublished by GitHub account withpicav2.121.1Updated Nov 7, 2026

manage your music catalog through conversation — works, recordings, credits, agreements, royalties

VerifiedStreamable HTTPWeb executableBusiness & CommerceMedia & Design

Overview

AI-generated overview

withPICA MCP server that lets an assistant sign a user in or up so they can manage a music catalog — works, recordings, credits, agreements, royalties — by…

What you can do
  • Sign up for a withPICA account from inside the chat, returning a single-use signup link
  • Sign in to an existing account by email magic link, or sign out and clear saved credentials
  • Manage a music catalog through conversation once authenticated: works, recordings, credits, agreements and royalties
When to use it
Useful when someone wants to work on their music catalog — works, recordings, credits, agreements or royalties — through an assistant and needs to connect or create a withPICA account first. The catalog tools only appear after sign-in.
Requirements
Runs as a remote endpoint or as a local npm package over stdio. No API key or environment variables are declared; authentication happens through the signup or sign-in tools, which need the user's email address and access to their inbox to click the link.
Before you install
The server asks for the user's email address and sends magic links to their inbox; signup links are single-use and expire after 15 minutes. Sign-out clears saved credentials. Catalog data, exports and analyses are not reachable until the user is signed in, so do not promise them beforehand.

Installation

In SourceWeft

  1. Open Pica in the dashboard and add it to a workspace.
  2. 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/io.github.withpica%2Fpica/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.

{
  "mcpServers": {
    "pica": {
      "type": "http",
      "url": "https://withpica.com/api/mcp"
    }
  }
}

README

This repository has no README.

Tools

3

pica_sign_in

sign in to PICA

sign in to PICA with your email — sends a magic link to your inbox. use this to connect your music catalog. no API key needed.

Parametersemailrequired

pica_sign_out

sign out of PICA

sign out of PICA — clears your saved credentials

Takes no parameters.

pica_signup_start

start a withPICA signup (sends a magic link to verify email)

[settings] Sign up for withPICA from inside the agent, without leaving the chat. Use this when the user wants to create a new withPICA account / catalog and you're talking to them through an unauthenticated MCP connection (stdio without an API key, or HTTP without a Bearer token). The tool mints a single-use signup link valid for 15 minutes — surface the URL to the user as a clickable resource_link. The link opens a page that verifies their email by magic-link, creates their organisation, starts their free runway (a non-expiring usage allowance — no day-count trial), and (for stdio) shows a connection key to paste into Claude Desktop's MCP config or (for HTTP) resumes the OAuth flow. For existing users, prefer pica_sign_in.

Parametersemailrequiredpurposeorg_namereferral_code

Version history

8
  1. v2.121.1LatestNov 7, 2026
  2. v2.119.0Nov 4, 2026
  3. v2.118.0Nov 4, 2026
  4. v2.117.0Nov 3, 2026
  5. v2.116.0Nov 3, 2026
  6. v2.115.0Nov 3, 2026
  7. v2.113.0Nov 1, 2026
  8. v2.95.2Sep 16, 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 listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.