Koskamo

withPICA MCP

An MCP server for music catalog management that allows AI agents to manage works, recordings, credits, agreements, and royalties through conversation. It supports both local stdio and remote HTTP transports, enabling agents to enrich metadata, reconcile identifiers, and prepare registration-ready exports for collection societies.

Visit withPICA

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

withPICA MCP logo, by withPICACommunity listingStreamable HTTPOAuth sign-inEndpoint checked 2026-11-01Published by withPICA
You need:create an API key in settings → connectionssign in with your withPICA loginadd a remote server with this address and sign in when asked
MCP endpoint (Streamable HTTP)
https://withpica.com/api/mcp
Vendor documentation

What you can do with it

  • Create and update music works and recordings
  • Manage credits, splits, and agreements
  • Enrich catalog data from global sources like ISNI and MusicBrainz
  • Export registration-ready data for collection societies

Source and maintenance

Community listingRegistry 2.113.0
mcp-registry: io.github.withpica/pica@2.113.0Source repository
Maintenance checked

Protocol and capabilities

Server
pica-http-lobby 2.113.0
MCP protocol
2025-06-18
Tools
Sign-in required
Resources
Sign-in required
Resource templates
Sign-in required
Prompts
Sign-in required
Server-advertised capabilities
{
  "tools": {},
  "prompts": {},
  "resources": {}
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

You are connected to withPICA but no user is authenticated yet. - New to withPICA? Ask for the user's email, then call pica_signup_start. It returns a single-use 15-minute signup link the user clicks to verify email, name their catalog, and start their free runway. - Already have a withPICA account? Signing in happens OUTSIDE this chat: the user must add withPICA as a connector in their AI app's settings (Claude: Settings → Connectors; ChatGPT: Settings → Connected apps) and approve the OAuth prompt. There is no in-chat sign-in tool on this transport — do not promise one. Do not promise catalog data, exports, or analyses until the user is connected — none of those tools are reachable from this lobby. After signup or connecting, the connection's tool surface refreshes automatically; ask the user what they want to do next.

Tools

Sign-in required

No tool definitions available.

Prompts

Sign-in required

No prompt definitions available.

Resources

Sign-in required

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
1713 ms
95th percentile latency
1713 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 1713 ms · metadata changed · refuses unauthenticated tools/list (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http withpica-mcp https://withpica.com/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add withpica-mcp --url https://withpica.com/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable withpica-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "withpica-mcp": {
      "url": "https://withpica.com/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "withpica-mcp": {
      "type": "streamableHttp",
      "url": "https://withpica.com/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start withpica-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "withpica-mcp": {
      "type": "http",
      "url": "https://withpica.com/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http withpica-mcp https://withpica.com/api/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "withpica-mcp": {
      "url": "https://withpica.com/api/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "withpica-mcp": {
      "serverUrl": "https://withpica.com/api/mcp"
    }
  }
}

Let your agent find its tools

Find servers like withPICA MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 4,318