TemPolor MCP Server
November 21, 2026
Table of contents
- useapi.net vs TemPolor’s developer API
- Endpoint and authorization
- Setup
- Use it in the Claude app or ChatGPT
- Tools
- Long-running work
- Example prompts
- Limits and notes
The useapi.net TemPolor MCP server lets an AI assistant such as the Claude app, ChatGPT, Claude Code, Cursor or VS Code Copilot make royalty-free music with TemPolor on your own TemPolor accounts. It is a hosted Model Context Protocol server with 17 tools: write songs with vocals in TemPolor v4.8, from your lyrics or lyrics TemPolor writes, sung by an artist voice or a voice you clone, or built on your MIDI file, make instrumentals with i4 in the key, tempo and chords you set, download every track as mp3, wav or stems, split your own audio into stems, and manage your tracks, voices and MIDI files. Each tool calls the TemPolor API, so the same rules and limits apply. Nothing needs to be installed or hosted.
Is there a TemPolor MCP server? Yes, through useapi.net, a third-party service not affiliated with TemPolor: a hosted server at https://api.useapi.net/v1/tempolor/mcp with 17 tools for v4.8 songs, i4 instrumentals, cloned voices, MIDI files and stems, on your TemPolor subscription. TemPolor has no MCP server of its own, so this is only available through useapi.net, and at volume it costs less than TemPolor’s developer API (comparison).
See all useapi.net MCP servers on Model Matrix & MCP.
useapi.net vs TemPolor’s developer API
TemPolor has no MCP server of its own: none is listed in the official MCP Registry or found on GitHub. Its developer API docs have an MCP button, which gives a coding assistant the API documentation, not tools that make music. What the useapi.net server gives you (as of November 21, 2026):
| useapi.net TemPolor MCP | TemPolor developer API | |
|---|---|---|
| A hosted MCP server for Claude, ChatGPT, Cursor and other assistants | Yes, 17 tools, and the Claude app and ChatGPT sign in with OAuth | No MCP server |
| Price at volume | Runs on your TemPolor subscription: Ultra at $29.99 a month has unlimited songs and stem splits | $0.04 a song, $0.05 when it writes the lyrics, $0.05 a 4-stem split, from prepaid packages of $100 |
| Songs in a voice you clone | Yes, tempolor_clone_voice | No voice cloning in its docs |
| Songs built on your MIDI file | Yes, tempolor_upload_midi | No MIDI input for songs (it only converts audio to MIDI) |
| Instrumentals in the key, tempo and chords you set | Yes, tempolor_create_instrumental | No key, tempo or chord setting |
Light use costs less on the developer API: Ultra comes out ahead past about 750 songs or 600 stem splits a month. useapi.net is a third-party service, not affiliated with TemPolor.
Endpoint and authorization
https://api.useapi.net/v1/tempolor/mcp
- Transport: Streamable HTTP.
- Authorization: your useapi.net API token in the
Authorization: Bearer …header, see Setup useapi.net. The Claude app and ChatGPT sign in with OAuth instead, see Use it in the Claude app or ChatGPT. - You need at least one TemPolor account added with Setup TemPolor. Adding and removing accounts is not available over MCP: use the setup page or POST accounts.
Setup
Replace YOUR_API_TOKEN with your useapi.net API token.
Claude Code
claude mcp add --transport http useapi-tempolor https://api.useapi.net/v1/tempolor/mcp --header "Authorization: Bearer YOUR_API_TOKEN"
Cursor
In ~/.cursor/mcp.json:
{
"mcpServers": {
"useapi-tempolor": {
"url": "https://api.useapi.net/v1/tempolor/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_TOKEN"
}
}
}
}
VS Code
In .vscode/mcp.json:
{
"servers": {
"useapi-tempolor": {
"type": "http",
"url": "https://api.useapi.net/v1/tempolor/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_TOKEN"
}
}
}
}
Windsurf and other clients
Any client that supports remote MCP servers over HTTP with custom headers works. The usual JSON shape:
{
"mcpServers": {
"useapi-tempolor": {
"serverUrl": "https://api.useapi.net/v1/tempolor/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_TOKEN"
}
}
}
}
Some clients name the address field url instead of serverUrl.
Test it with curl
curl -s https://api.useapi.net/v1/tempolor/mcp \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"1"}}}'
curl -s https://api.useapi.net/v1/tempolor/mcp \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/list"}'
The first call answers with the server’s name useapi-tempolor and its instructions for the assistant, the second with the 17 tools.
Use it in the Claude app or ChatGPT
The Claude app (claude.ai and Claude Desktop) and ChatGPT can add this server as a custom connector. They sign in with OAuth: you give the app the URL, it opens a useapi.net page, and you paste your useapi.net API token there once. Both work on their Free plans. The API-token setups above for Claude Code, Cursor, VS Code and other clients keep working as before.
https://api.useapi.net/v1/tempolor/mcp
Claude app
- Open Settings → Connectors and click Add custom connector.
- Enter a name, for example
useapi TemPolor, and the URL above, then click Add. - Click Connect. Claude opens the useapi.net sign-in page.
- Paste your useapi.net API token and click Allow.
Claude asks before each tool call unless you choose Always allow. The Free plan allows one custom connector.
ChatGPT
- Open Plugins, click Add and choose Add custom MCP server.
- Enter a name and the URL above, and set Authentication to OAuth.
- Tick ChatGPT’s “I understand and want to continue” box, then click Create as a plugin.
- Click Connect. ChatGPT opens the useapi.net sign-in page.
- Paste your useapi.net API token and click Allow.
ChatGPT asks you to confirm each tool call that creates or changes something. The Free plan works without developer mode (as of October 25, 2026).
How the sign-in works
- Your API token is in your welcome email, see Setup useapi.net. The useapi.net page links there too.
- Each connection is for one MCP server. Connect each server you want to use on its own.
- The app gets an access token that lasts 1 hour and renews it on its own. A connection you don’t use for 90 days lapses, and you connect again.
- Resetting your API token disconnects every app connected with it.
- Results come back as public links, so they open right in the app.
Tools
Every song and instrumental is a job with a job_id, read with tempolor_get_music. Without user_id, a job runs on one of your accounts with a free slot within its maxJobs, and a song with a cloned voice or a MIDI file runs on the account that holds it. With more than one account connected, the uploads and lists need user_id. The create tools also take maxJobs, wait, and a webhook with replyUrl and replyRef.
Songs, instrumentals and stems
| Tool | What it does | Main parameters |
|---|---|---|
tempolor_create_song | Writes a song with vocals with TemPolor v4.8, up to 5 minutes in more than 30 languages, from a style prompt and your lyrics or lyrics TemPolor writes. It can be sung by an artist voice or your cloned voice, or built on your MIDI file, one of these at most. Older model names run on v4.8. | prompt, lyrics, model_song, artistVoiceItemId, clonedVoiceItemId, midiItemId, user_id |
tempolor_create_instrumental | Makes an instrumental with TemPolor i4 from a prompt, in the key, tempo (50 to 190 BPM) and chord progression you set. Older model names run on i4. | prompt, model_instrumental, tonality, bpm, chords, user_id |
tempolor_split_stems | Splits your own MP3, WAV, M4A or FLAC file, up to 50 MB, into vocal and instrument stems and returns a ZIP of them. Stem splitting is on TemPolor Pro and Ultra. | url or contentBase64, mimeType, user_id |
The parameters match POST music/song, POST music/instrumental and POST music/stems-splitter. A long file whose stems take more than about a minute goes to POST music/stems-splitter directly, which waits up to 120 seconds.
Tracks
| Tool | What it does | Main parameters |
|---|---|---|
tempolor_get_music | Reads one song or instrumental, and with wait: true waits for it to finish. A finished track comes with its title, cover, musical details and a temporary mp3 link. | job_id, wait |
tempolor_list_music | Lists one account’s songs or instrumentals, those made in the TemPolor web app too, with each one’s status, style, key, tempo, length and model, a page at a time. | user_id, type, cursor |
tempolor_download_music | Gives a temporary download link for a finished track as mp3, wav, or stems as a ZIP of the separated vocals and instruments. | job_id, file_format |
tempolor_delete_music | Deletes one song or instrumental from its TemPolor account. It cannot be undone. | job_id |
The parameters match GET music/job_id, GET music, GET music/download/job_id and DELETE music/job_id.
Voices and MIDI files
| Tool | What it does | Main parameters |
|---|---|---|
tempolor_list_artist_voices | Lists TemPolor’s ready-made artist voices, each with its itemId, name, labels and a sample, a page at a time. | user_id, cursor |
tempolor_clone_voice | Clones a voice from your MP3, WAV, M4A or FLAC sample, up to 50 MB, and saves it on a TemPolor account. Returns its clonedVoiceItemId. TemPolor keeps up to 4 cloned voices on Lite, 10 on Pro and 50 on Ultra. | name, url or contentBase64, mimeType, user_id |
tempolor_list_cloned_voices | Lists the voices cloned on one account, those cloned in the TemPolor web app too, with each one’s status and sample. | user_id, cursor |
tempolor_delete_cloned_voice | Deletes one cloned voice, which frees a place under the plan’s cap. It cannot be undone. | clonedVoiceItemId |
tempolor_upload_midi | Uploads a MIDI file under 5 MB to a TemPolor account to build songs on. Returns its midiItemId, ready at once. | name, url or contentBase64, mimeType, user_id |
tempolor_list_midi | Lists the MIDI files uploaded to one account, those from the TemPolor web app too. | user_id, cursor |
tempolor_delete_midi | Deletes one uploaded MIDI file. It cannot be undone. | midiItemId |
The parameters match GET music/artist-voices, POST music/cloned-voices, GET music/cloned-voices, DELETE music/cloned-voices, POST music/midi, GET music/midi and DELETE music/midi.
Jobs and accounts
| Tool | What it does | Main parameters |
|---|---|---|
tempolor_list_running_jobs | Lists the songs and instrumentals the API is tracking now, and your healthy accounts with how many free slots each has. The first check after a 429. | |
tempolor_stop_tracking | Stops tracking a running job and frees its slot on the account. It does not cancel the job at TemPolor: the track is still made and tempolor_get_music still reads it, but its webhook calls stop. It cannot be undone. | job_id |
tempolor_list_accounts | Lists your TemPolor accounts as stored: user_id, maxJobs and any stored account error, without calling TemPolor. | user_id |
The parameters match GET scheduler/available, GET scheduler, DELETE scheduler/job_id, GET accounts and GET accounts/user_id.
The full input schema of every tool comes from tools/list.
Long-running work
MCP clients usually give up on a tool call after about a minute, so a tool waits up to about 50 seconds:
- A quick track can come back from
tempolor_create_songortempolor_create_instrumentalitself, with its mp3 link. - Otherwise the tool returns the
job_id, andtempolor_get_musicwithwait: truepicks it up. Ask the assistant to keep checking untilstatus_finalis true: the track is thenCOMPLETEDorFAILED. wait: falseon a create tool returns thejob_idat once.- A job just submitted can read as not listed by TemPolor yet for up to 10 minutes. That is not a failure: check again.
Clients that ask for progress notifications get one about every 10 seconds while a tool waits.
The mp3 link of a finished track is temporary. tempolor_download_music gives a fresh one, a wav file, or the stems as a ZIP, which TemPolor prepares on request in about a minute, so a stems call can run out of time before the ZIP is ready. A track can read COMPLETED a few seconds before its file is ready, so a download that answers 404 right then works when asked again.
Example prompts
- “Write an upbeat synth-pop song about a road trip along the coast, and give me the mp3.”
- “Make a 90 BPM lo-fi hip hop instrumental in A minor with the chords Am F C G.”
- “Show me TemPolor’s artist voices and sing my lyrics in the warmest female voice.”
- “Clone my voice from this recording and use it on a slow acoustic ballad.”
- “Upload this MIDI file and build a cinematic pop song on it.”
- “Split this song into vocal and instrument stems.”
- “Give me the wav and the stems of the last track.”
- “Which of my TemPolor accounts are busy right now?”
Limits and notes
- The tools use your TemPolor accounts and the same rules as the REST API, such as
maxJobs(default 10 jobs at once per account). On Lite and Pro each song or instrumental counts against the plan’s monthly tracks, and Ultra has no track limit, see Pricing. - Files sent to
tempolor_clone_voiceandtempolor_split_stemscan be up to 50 MB through this server, and MIDI files under 5 MB. Send a public httpsurl, or the file ascontentBase64with itsmimeTypefor small files. - A 429 means your accounts are busy or TemPolor asks to wait: check
tempolor_list_running_jobsand retry after 30 seconds. A 596 means TemPolor signed the account out: add it again on the setup page. - A client may send up to 20 JSON-RPC requests in one batch.
- If the client sends an
MCP-Protocol-Versionheader, it must be one of the supported versions:2025-11-25,2025-06-18,2025-03-26or2024-11-05.