start_trial — StudioSphere Pulse — Audio Intelligence MCP Tool Mutating
start_trial
(start trial) is one of 8 tools on the
StudioSphere Pulse — Audio Intelligence
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call start_trial from your client
- Claude Code StudioSphere Pulse — Audio Intelligence start_trial run in your project directory
- Claude Desktop StudioSphere Pulse — Audio Intelligence start_trial ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor StudioSphere Pulse — Audio Intelligence start_trial ~/.cursor/mcp.json
- VS Code StudioSphere Pulse — Audio Intelligence start_trial .vscode/mcp.json
- Zed StudioSphere Pulse — Audio Intelligence start_trial ~/.config/zed/settings.json
- Windsurf StudioSphere Pulse — Audio Intelligence start_trial ~/.codeium/windsurf/mcp_config.json
- Cline StudioSphere Pulse — Audio Intelligence start_trial ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI StudioSphere Pulse — Audio Intelligence start_trial ~/.gemini/settings.json
- Grok StudioSphere Pulse — Audio Intelligence start_trial .mcp.json (in your project root)
- ChatGPT StudioSphere Pulse — Audio Intelligence start_trial Settings → Connectors → Advanced → Developer mode
- Claude.ai StudioSphere Pulse — Audio Intelligence start_trial Settings → Connectors → Add custom connector
- LangChain StudioSphere Pulse — Audio Intelligence start_trial pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http pulse https://mcp.studiosphere.space/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.