Rinkel MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

Rinkel MCP by usefulapi is answering right now. Last checked 4 min ago. It exposes 27 tools. Last commit 25 Oct 2026.

Read Rinkel calls, voicemails, contacts and numbers; add call notes, edit contacts, block numbers.

Uptime history 26 hours of history

26 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

379 ms

Response time

average over 24h

Stars

last commit 25 Oct 2026

What changed 4

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 25 October 2026. No other catalogue keeps this.

25 Oct a tool changed version4 times that day

and 3 more, back to 25 October 2026

Nothing serious here today

Today is the operative word: we check Rinkel MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add rinkel --transport http https://rinkel.usefulapi.io/mcp

Settings → Connectors → Add custom connector, then paste this address

https://rinkel.usefulapi.io/mcp

~/.codex/config.toml

[mcp_servers.rinkel]
url = "https://rinkel.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "rinkel": {
      "url": "https://rinkel.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "rinkel": {
      "type": "http",
      "url": "https://rinkel.usefulapi.io/mcp"
    }
  }
}

Available tools 27

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

rinkel

rinkel_add_call_note

WRITE: add a note to a call record (visible to everyone in the account who sees the call). The id is the call record's `id`; if Rinkel answers 404, retry with the record's `callId`. Rinkel API: PUT /call-detail-records/{callId}/note.

rinkel_block_number

WRITE: block a number from calling ANY of the account's numbers. Accepts an E.164 number, 'anonymous', or a prefix wildcard such as '+31*' (a wildcard must end the value and include a country code; a broad wildcard blocks every caller from that country). Undo with rinkel_unblock_number. Rinkel API: POST /privacy/block-number.

rinkel_count_new_voicemails

Number of voicemails that have not been played yet. Rinkel API: GET /voicemails/new-count.

rinkel_create_contact

WRITE: create a contact. It is shared with everyone in the Rinkel account (all users see it and calls from its numbers show its name). Rinkel API: POST /contacts.

rinkel_delete_call_note

WRITE, irreversible: delete one note from a call record. Needs confirm=true after the user approved it. Rinkel API: DELETE /call-detail-records/{callId}/note/{noteId}.

rinkel_delete_contact

WRITE, irreversible: delete a contact for the whole account. Needs confirm=true after the user approved it. The Rinkel system contact cannot be deleted. Rinkel API: DELETE /contacts/{id}.

rinkel_find_contact_by_number

Find the contact that owns a phone number (E.164 such as +31612345678 works best). 404 when there is none. Rinkel API: GET /contacts/find-by-number/{number}.

rinkel_get_call

Get one call detail record by its Rinkel id (the `id` field of rinkel_list_calls): numbers, users, status, duration, notes, voicemail and call-recording ids, AI insights. Rinkel API: GET /call-detail-records/{id}.

rinkel_get_call_by_network_id

Get one call detail record by its network `callId` (the id Rinkel sends in webhook events), optionally with insights and notes. Rinkel API: GET /call-detail-records/by-call-id/{callId}.

rinkel_get_call_recording_url

Get a temporary URL (valid 3 hours) to stream or download a call recording. The id is `callRecording.id` of a call record. Append `download` as a query parameter to the URL to download instead of stream. Rinkel API: GET /call-recordings/{id}/stream.

rinkel_get_call_transcription

Get the raw transcription of a call by its network `callId` (needs Rinkel AI insights on the account; 404 when the call has none). Rinkel API: GET /call-detail-records/by-call-id/{callId}/transcription.

rinkel_get_contact

Get one contact by id. Rinkel API: GET /contacts/{id}.

rinkel_get_number

Get one Rinkel number with its full dial plan: greeting, business hours schedule, call forwarding targets and ring logic, voice menu, call recording and caller-id settings. Rinkel API: GET /numbers/{id}.

rinkel_get_user

Get one user by id, including preferences, notification settings, schedule and `deviceId`. Rinkel API: GET /users/{id}.

rinkel_get_voicemail_url

Get a temporary URL (valid 3 hours) to stream or download a voicemail. The id is `voicemail.id` of a call or voicemail record. Rinkel API: GET /voicemails/{id}/stream.

rinkel_list_calls

List call detail records (inbound and outbound calls) with date, direction, status (ANSWERED, MISSED, VOICEMAIL, ANSWERING_SERVICE), duration, external and internal number, the users involved, notes, and (when the account has Rinkel AI insights) the AI summary and sentiment. Use for 'who called today', 'which calls did we miss this week', 'calls longer than 5 minutes'. Newest first by default. Rinkel API: GET /call-detail-records.

rinkel_list_contacts

List the contacts shared with everyone in the account (plus the Rinkel system contact, tag 'system'): names, company, phone numbers, email. Rinkel API: GET /contacts.

rinkel_list_numbers

List the account's Rinkel phone numbers: id, label, number, status (ACTIVE, SUSPENDED, PENDING_PORTING_IN ...), activation date and the users assigned. Rinkel API: GET /numbers.

rinkel_list_recordings

List the uploaded audio recordings used in the dial plan (greetings, announcements, voice-over scripts): name, description, duration and where each is used. Not call recordings. Rinkel API: GET /recordings.

rinkel_list_users

List the account's users: name, email, phone number, role (ADMIN, USER, ANSWERINGSERVICE), availability schedule and status, and `fixed`/device info (`deviceId` is needed to start a call). Rinkel API: GET /users.

rinkel_list_voicemails

List voicemail messages (call records with status VOICEMAIL): caller, date, duration, whether new, and the voicemail id. Newest first. With is_new=true Rinkel ignores every other filter and returns only unplayed voicemails. Rinkel API: GET /voicemails.

rinkel_list_webhooks

List the webhook subscriptions (events incomingCall, outgoingCall, callStart, callEnd, callInsights) with URL and active flag. Webhooks need the Expert plan. Rinkel API: GET /webhooks.

rinkel_start_call

WRITE, COSTS CALL MINUTES: starts a real phone call. Rinkel rings the given user device first and, once it is answered, dials `to` using the chosen Rinkel number as caller id, so call charges apply to the account and the person called sees the number. Needs confirm=true, set only after the user explicitly asked to place this call. Get device_id from rinkel_list_users (`fixed`/device info or `deviceId`) and number_id from rinkel_list_numbers. Rinkel API: POST /dial.

rinkel_unblock_number

WRITE: remove a number (or the same wildcard pattern that was blocked) from the block list so it can call again. Rinkel API: DELETE /privacy/unblock-number.

rinkel_update_call_note

WRITE: replace the text of an existing note on a call record (the note id is in `notes[].id` of the call record). Rinkel API: PATCH /call-detail-records/{callId}/note/{noteId}.

rinkel_update_contact

WRITE: update a contact (PUT semantics). `numbers` is required and REPLACES all stored numbers, and an omitted default_outbound_number_id CLEARS it; omitted names, company and email keep their stored value. Read the contact first (rinkel_get_contact) and resend what must stay. The system contact cannot be changed. Rinkel API: PUT /contacts/{id}.

rinkel_validate_phone_number

Check a phone number for a country and return its normalised form. With check_inventory=true Rinkel also checks whether the number is available to order. Rinkel API: GET /misc/validate-phone-number.

Endpoints

URL	Transport	State	Latency	Checked
https://rinkel.usefulapi.io/mcp	streamable-http	answering	198 ms	4 min ago

Alternatives to Rinkel MCP by usefulapi

same job, measured the same way

Aircall MCP by usefulapi

by usefulapi

Read calls, contacts, users, teams and numbers; tag calls and create or update contacts.

25 tools answering

Nylas MCP by usefulapi

by usefulapi

MCP server for Nylas — read email, calendars, events and contacts, and send email or create events.

15 tools answering

Trumpia MCP by usefulapi

by usefulapi

Read Trumpia lists, subscribers, keywords and reports; add contacts and send SMS or email campaigns.

22 tools answering

Helpwise MCP by usefulapi

by usefulapi

Read Helpwise conversations, contacts, tags and reports; note, tag, assign, close; send one email.

21 tools answering

CharlieHR MCP by usefulapi

by usefulapi

Read CharlieHR team members, leave, allowances, offices, teams and salaries; add team member notes.

27 tools answering

Enginemailer MCP by usefulapi

by usefulapi

Read Enginemailer subscribers, lists and campaigns; add subscribers, create and send campaigns.

17 tools answering

Sarbacane MCP by usefulapi

by usefulapi

Read Sarbacane campaigns, stats, lists and blacklists; manage contacts and draft email campaigns.

19 tools answering

EmailOctopus MCP by usefulapi

by usefulapi

Manage lists, contacts and campaigns, and read campaign performance reports on EmailOctopus.

13 tools answering

Rinkel MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Rinkel MCP by usefulapi do?

It exposes 27 tools, read directly from the server on our last check. Among them: rinkel_add_call_note, rinkel_block_number, rinkel_count_new_voicemails, rinkel_create_contact, rinkel_delete_call_note, rinkel_delete_contact and 21 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Rinkel MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 379 ms. The bar chart above shows every period we have measured.

How do I connect Rinkel MCP by usefulapi?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Rinkel MCP by usefulapi need an API key?

No. Rinkel MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 27 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Rinkel MCP by usefulapi?

It answers our handshake in 379 ms on average, which is faster than 39% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Rinkel MCP by usefulapi open source?

The code is open source: it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at rinkel.usefulapi.io, which runs on its operator's own terms.