Setup guide

Connect Soundcharts MCP to any compatible agent using a standard mcp.json configuration.

Compatible clients

You can connect Soundcharts MCP with these clients and other agents that support MCP JSON configuration.

Claude Codex Copilot Lovable n8n OpenClaw and others

Connection details

Use the Soundcharts MCP HTTP endpoint and provide your token through the Authorization header.

Field Value
Server URL https://mcp.soundcharts.com
Transport http
Authentication Authorization: Bearer YOUR_SOUNDCHARTS_MCP_TOKEN

mcp.json configuration

The MCP JSON format uses a mcpServers object. Each key is a server name, and each value describes how the client should connect to that server. Add Soundcharts as a remote HTTP server: 

{
  "mcpServers": {
    "soundcharts": {
      "type": "http",
      "url": "https://mcp.soundcharts.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_SOUNDCHARTS_MCP_TOKEN"
      }
    }
  }
}

Configuration fields

  • mcpServers: the root object used by MCP clients to declare available servers.
  • soundcharts: the local name of the server. You can rename it, but keeping soundcharts makes it easy to identify.
  • type: use http because Soundcharts MCP is exposed as a remote HTTP server.
  • url: the Soundcharts MCP endpoint.
  • headers.Authorization: your bearer token for authenticating requests.

Where to place it

The exact file location depends on your MCP client. Common locations include:

  • VS Code: workspace-level .vscode/mcp.json.
  • Cursor: user-level ~/.cursor/mcp.json.
  • Claude Desktop: user-level ~/.claude/claude_desktop_config.json.
  • Other MCP clients: use the client MCP settings file, or paste the same URL and headers if the client provides a form-based setup.

Some clients use slightly different field names or UI labels. The required values stay the same: server URL, HTTP transport, and the Authorization header.

Validate the connection

  1. Save the configuration in your MCP client.
  2. Restart or reload the client so it reads the new server configuration.
  3. Ask the client to list the available Soundcharts tools.
  4. Run a small request before using the tools in a larger workflow.

Next steps

Client-specific setup pages, screenshots, and app-store installation flows will be added later when the integration requires UI-based configuration.