We and selected third parties use cookies or similar technologies for technical purposes and, with your consent, to analyze how the site is used.

You can freely give, refuse or withdraw your consent at any time.

apisapp WhatsApp

MCP server by api-supp

Send WhatsApp messages and read chats, contacts and message status across every number linked to your apisapp account.

OAuth sign-in (You sign in with the vendor the first time you connect)Streamable HTTP

Connect to apisapp WhatsApp

apisapp WhatsApp needs sign-in. Connect with its own URL:

https://app.api-supp.com/api/mcp

Your client opens api-supp’s sign-in the first time you use it. The token stays between your client and api-supp.

Share this server

Opens this page, with the URL and setup steps.

mcp.tc/i/apisapp-whatsapp

About

Connects an assistant to a managed WhatsApp service where numbers are linked by scanning a QR code. It can list numbers, send texts, polls, contact cards, buttons and link buttons, manage contacts, and read chats, messages and delivery status. It is a hosted backend, not Meta's official Cloud API.

The hosted endpoint runs over streamable HTTP and needs nothing installed. Users sign in to their apisapp account through OAuth and approve access. A manually generated bearer token is available for apps that cannot sign in. Files, voice notes and media download need the separate local MCP client.

What you can do

  • List linked WhatsApp numbers and their status
  • Send text, polls, contact cards, buttons and lists
  • Search, save and update contacts
  • Read chats, messages and surrounding context
  • Check delivery and read status of sent messages
  • Sync history and contacts from WhatsApp

Tools

apisapp WhatsApp lists its tools only after you sign in, so we can’t show them here. Your client lists them once you’re connected.

Example prompts

  • List my WhatsApp numbers

  • Send from the Sales line: your order has shipped

  • Show the last messages in my chat with +14155550132

  • Did my last message to Anna get delivered and read?

Set up

Every client connects to app.api-supp.com, and api-supp asks you to sign in the first time. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http apisapp-whatsapp https://app.api-supp.com/api/mcp
  1. Start Claude Code, type /mcp, pick apisapp-whatsapp and choose Authenticate. A browser window opens for the api-supp sign-in.

Add --scope user to make it available in every project, not just this one.

Claude Desktop

  1. Open Customize → Connectors, click + Add, then Add custom connector.
  2. Name it apisapp WhatsApp and paste this URL:
https://app.api-supp.com/api/mcp
  1. Click Add, then Connect, and sign in when api-supp asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

claude.ai

  1. Open the connector form on claude.ai. This button fills in the name and URL for you:
  1. Check that the URL reads https://app.api-supp.com/api/mcp and click Add.
  2. Click Connect and sign in when api-supp asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.

ChatGPT

  1. On chatgpt.com, go to Plugins, select +, then Add custom MCP server.
  2. Enter a name for the server.
  3. Under Connection, paste https://app.api-supp.com/api/mcp as the server URL, then for authentication choose OAuth. ChatGPT sends you to api-supp to sign in.
  4. Check I understand and want to continue, then select Create as a plugin.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "apisapp-whatsapp": {
      "url": "https://app.api-supp.com/api/mcp"
    }
  }
}

Cursor shows Needs authentication next to the server. Click the button beside it to sign in.

VS Code

Or from a terminal:

code --add-mcp '{"name":"apisapp-whatsapp","type":"http","url":"https://app.api-supp.com/api/mcp"}'

Or commit it to the repo in .vscode/mcp.json:

.vscode/mcp.json
{
  "servers": {
    "apisapp-whatsapp": {
      "type": "http",
      "url": "https://app.api-supp.com/api/mcp"
    }
  }
}

VS Code asks you to sign in the first time the server starts.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "apisapp-whatsapp": {
      "serverUrl": "https://app.api-supp.com/api/mcp"
    }
  }
}
  1. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.

Codex

codex mcp add apisapp-whatsapp --url https://app.api-supp.com/api/mcp
codex mcp login apisapp-whatsapp

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.apisapp-whatsapp]
url = "https://app.api-supp.com/api/mcp"

Gemini CLI

gemini mcp add --transport http apisapp-whatsapp https://app.api-supp.com/api/mcp

Then, inside Gemini CLI, run /mcp auth apisapp-whatsapp to sign in.

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.

{
  "mcpServers": {
    "apisapp-whatsapp": {
      "type": "http",
      "url": "https://app.api-supp.com/api/mcp"
    }
  }
}

Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.

Client only starts local servers? Bridge it with npx -y mcp-remote https://app.api-supp.com/api/mcp.

Embed

Show apisapp WhatsApp in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge

Badge preview, lightBadge preview, dark
Markdown
[![apisapp WhatsApp on mcp.tc](https://mcp.tc/i/apisapp-whatsapp/badge.svg)](https://mcp.tc/i/apisapp-whatsapp)
HTML
<a href="https://mcp.tc/i/apisapp-whatsapp"><img src="https://mcp.tc/i/apisapp-whatsapp/badge.svg" alt="apisapp WhatsApp on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/apisapp-whatsapp.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/apisapp-whatsapp" title="apisapp WhatsApp on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/apisapp-whatsapp.json

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the apisapp WhatsApp card to your site.

Markdown
Add the mcp.tc card for apisapp WhatsApp, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

```html
<script src="https://mcp.tc/w/apisapp-whatsapp.js" async></script>
```

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="apisapp-whatsapp"><a href="https://mcp.tc/i/apisapp-whatsapp">apisapp WhatsApp on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![apisapp WhatsApp on mcp.tc](https://mcp.tc/i/apisapp-whatsapp/badge.svg)](https://mcp.tc/i/apisapp-whatsapp)
```

Reference: https://mcp.tc/embed

Change history

Its tools are behind a sign-in, so we can’t read them. Edits by its owner show up here.

Follow apisapp WhatsApp and we’ll email you when something changes.

Nothing recorded yet. Edits by the server’s owner will show up here.

FAQ

Can I paste mcp.tc/i/apisapp-whatsapp into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://app.api-supp.com/api/mcp, so your client talks to apisapp WhatsApp directly. The sign-in token only works there anyway. The quick link is for sharing: it opens this page, with setup steps for every client.

Does apisapp WhatsApp need an API key or a sign-in?

Yes, you need a api-supp account. The first time your client connects, it opens api-supp’s sign-in page. The token goes straight to the server’s own URL, never through mcp.tc.

Is apisapp WhatsApp a remote or a local server?

Remote. api-supp hosts it at https://app.api-supp.com/api/mcp, and it speaks Streamable HTTP. There’s nothing to install.

What can apisapp WhatsApp do?

You can list linked WhatsApp numbers and their status, send text, polls, contact cards, buttons and lists and search, save and update contacts.

Which clients can use it?

Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.

Does mcp.tc track changes to apisapp WhatsApp?

Partly. apisapp WhatsApp’s tools are behind a sign-in, so its History tab shows only edits by its owner. Follow the listing to get an email when it changes.

Who wrote this page?

mcp.tc’s robot read apisapp WhatsApp’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

mcp.tc isn’t affiliated with api-supp. This page was built from apisapp WhatsApp’s public metadata, last checked on 18 Nov 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.