Model Context Protocol

Bring Pulse into your AI assistant.

Pulse runs as an MCP server, so any compatible assistant — Claude Desktop, Claude Code, Cursor, and others — can call it directly. For autonomous agents, configure a funded API key once; the agent can then estimate, analyze authorized audio, and poll results from banked tokens without Stripe Checkout on every job.

Autonomous agent setup (one-time human step)

  1. Create a Pulse account and buy token packs so banked_tokens is greater than zero.
  2. Paste your API key below and copy the MCP config with ?api_key= embedded in the connection URL.
  3. Give your agent a reusable rights policy, for example: "For this playlist/folder, I confirm lawful access to analyze these tracks with Pulse."
  4. Agent call order: get_token_balance → estimate_cost → analyze_track → get_job_status.

Machine-readable journey contract: /.well-known/pulse/agent-journey.json · Agent playbook: /for-agents

We'll stamp this into the snippets below as you type. Nothing is sent to a server — it lives only in this page. Don't have a key? Get one — it takes about ten seconds.

Heads up: the Pulse MCP currently accepts the API key only as a URL query parameter. Treat the URL as a secret — store it in a password manager, not in version control. Use YOUR_PULSE_API_KEY as the placeholder in public examples; only add your real key inside your own MCP client or trusted local environment. Header-based bearer auth is on the v1.1 roadmap.

Testing Pulse in a real workflow?

Estimates are always free. Qualified early users can request a small evaluation credit for a few authorized audio analyses before buying token packs. Evaluation credits are capped, time-limited, and intended for API/MCP workflow validation — not as a broad free tier.

Claude Desktop

Open Settings → Developer → Edit Config, then merge this entry into the mcpServers object:

{
  "mcpServers": {
    "studiosphere-pulse": {
      "type": "http",
      "url": "https://mcp.studiosphere.space/mcp?api_key=YOUR_PULSE_API_KEY"
    }
  }
}

Restart Claude Desktop. The Pulse tools (estimate_cost, analyze_track, get_job_status, etc.) will appear in any conversation.

Claude Code (CLI)

One command, no manual JSON edits. The --transport http flag tells Claude Code this is a remote server, not a stdio binary:

claude mcp add --transport http studiosphere-pulse https://mcp.studiosphere.space/mcp?api_key=YOUR_PULSE_API_KEY

Run claude mcp list to verify. Pulse tools are available in your next session.

Cursor

Add this to ~/.cursor/mcp.json (create the file if it doesn't exist):

{
  "mcpServers": {
    "studiosphere-pulse": {
      "type": "http",
      "url": "https://mcp.studiosphere.space/mcp?api_key=YOUR_PULSE_API_KEY"
    }
  }
}

Cursor picks up the change on next launch.

VS Code / GitHub Copilot

Add Pulse as a user or workspace MCP server. For a workspace, create .vscode/mcp.json:

{
  "servers": {
    "studiosphere-pulse": {
      "type": "http",
      "url": "https://mcp.studiosphere.space/mcp?api_key=YOUR_PULSE_API_KEY"
    }
  }
}

Open Copilot Chat, choose tools, and enable StudioSphere Pulse for prompts that need BPM, key, or waveform analysis.

After analysis, users who want to keep working on a track can save it to a StudioSphere vault and continue in project, listening, or collaboration workflows.

ChatGPT

In ChatGPT or another MCP-compatible client, add Pulse as a remote MCP server using this Streamable HTTP URL. If your client asks for authentication, use your Pulse API key. If it asks for a public example config, keep YOUR_PULSE_API_KEY as the placeholder — never a real key.

https://mcp.studiosphere.space/mcp?api_key=YOUR_PULSE_API_KEY

Recommended flow: estimate cost, show the price, confirm the user has rights or lawful access to the audio, analyze with an API key, then poll for results. If your ChatGPT plan does not expose MCP yet, the same contract is available through the Pulse REST API — see /llms.txt.

Raw transport details

For any MCP-aware client, the server uses Streamable HTTP transport:

The configured URL with your key embedded:

https://mcp.studiosphere.space/mcp?api_key=YOUR_PULSE_API_KEY

Verify it's working

After restarting your client, ask the assistant: "What's the BPM of https://example.com/track.mp3?" The assistant should call the estimate_cost tool first, confirm the price, then call analyze_track and read the result. First-time agents can also call start_trial for one short trial before account setup. Treat any returned trial key as private: copy it into the client or a trusted local environment, not public logs, screenshots, GitHub issues, or shared chats. If you are testing a real authorized workflow for a product, catalog, or agent integration, ask about an evaluation credit before buying token packs. If the assistant doesn't see Pulse tools, double-check the URL has your key on it and that you restarted after editing the config.

Need the short version?

The public quickstart keeps the agent workflow, rights confirmation, and canonical marketplace links in one place: Pulse MCP quickstart.

What your assistant gets

start_trialMint a temporary private trial key for one short URL analysis.
estimate_costQuote a price for a public audio URL.
analyze_trackRun analysis (BPM, key, waveform). Auth required.
request_payment_linkStripe Checkout link for one-off use after rights confirmation.
get_job_statusPoll a running job, fetch the result.
get_token_balanceCheck banked-token balance.
list_token_packsList token-pack tiers before purchase.
purchase_token_packCreate a Checkout link to add banked tokens (present to human).