Quickstart: first MCP tool call in 5 minutes
When to use
Use this when validating connectivity
Use this flow when you need to confirm endpoint, authentication, and baseline tool discovery before building larger agent loops.
Step 0
Create an account and generate an API key
- Sign up for a free account — you'll get 300 credits ($3) to start.
- Go to the Developer Console and generate an API key. Copy it — it's shown only once.
- Store the key securely (e.g. in an environment variable or secret manager).
Step 1
List available tools
POST https://mcp.soundside.ai/mcp
{
"jsonrpc": "2.0",
"id": "1",
"method": "tools/list",
"params": {}
}Include Authorization: Bearer <your_api_key> in the request headers. A successful response returns all 11 tools and confirms your key is valid.
Response
Expected success shape
{
"jsonrpc": "2.0",
"id": "1",
"result": {
"tools": [
{ "name": "create_video", "inputSchema": { "type": "object" } }
]
}
}Step 2
Generate your first image
Now prove the full pipeline works. This call costs ~$0.04 (4 credits) and returns instantly.
POST https://mcp.soundside.ai/mcp
{
"jsonrpc": "2.0",
"id": "2",
"method": "tools/call",
"params": {
"name": "create_image",
"arguments": {
"provider": "minimax",
"prompt": "A futuristic city skyline at sunset, cinematic lighting"
}
}
}The response includes a resource_id (saved to your library) and a signed url for the generated image. You can chain this resource into create_video, edit_video, or analyze_media.
Error behaviors
Common failures during first call
- •
401Unauthorized: missing or invalid bearer token. - •
403Forbidden: OAuth client policy or tool tier restriction. - •
429Quota exceeded: respectRetry-Afterand retry window.
Operational notes
Production-minded defaults
- • Base URL is
https://mcp.soundside.ai/mcp. - • Prefer OAuth for third-party connectors.
- • All 11 tools are available to all users — no tier restrictions.