TrackForge MCP MCP server

A free remote MCP server that allows AI assistants to perform ISRC lookups, check song registrations against The MLC's data, retrieve ISWCs, identify songwriters and publishers with IPIs, and validate CWR files. It helps users determine if music royalties are unmatched or unclaimed by verifying links between recordings and registered works.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by TrackForge

MCP endpoint (Streamable HTTP)

https://api.trackforge.studio/api/v1/mcp

Vendor documentation

What you can do with it

Check if an ISRC is registered with The MLC and if shares are unclaimed
Retrieve songwriter, publisher, and ISWC details for a recording
Validate CWR files for errors and warnings before submission
Identify recordings with no linked work to prevent unclaimed royalties

Tools advertised by the last live check:

lookup_recording
check_catalogue
validate_cwr
request_full_report

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 a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http trackforge-mcp https://api.trackforge.studio/api/v1/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 trackforge-mcp --url https://api.trackforge.studio/api/v1/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable trackforge-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "trackforge-mcp": {
      "url": "https://api.trackforge.studio/api/v1/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "trackforge-mcp": {
      "type": "streamableHttp",
      "url": "https://api.trackforge.studio/api/v1/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start trackforge-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "trackforge-mcp": {
      "type": "http",
      "url": "https://api.trackforge.studio/api/v1/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 trackforge-mcp https://api.trackforge.studio/api/v1/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": {
    "trackforge-mcp": {
      "url": "https://api.trackforge.studio/api/v1/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": {
    "trackforge-mcp": {
      "serverUrl": "https://api.trackforge.studio/api/v1/mcp"
    }
  }
}

See all 1,583

Do you run TrackForge MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing