Tap MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 242 installs a week from npm.
Music PR campaign management -- contacts, pitches, campaigns, and outcomes.
The linked repository no longer exists on GitHub — it was deleted or made private.
We have not read this server's code yet
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
пакет @totalaudiopromo/tap-mcp ссылается на chrisschouk/total-audio-platform
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add tap-mcp -e 'TAP_SUPABASE_URL=<TAP_SUPABASE_URL>' -e 'TAP_SUPABASE_KEY=<TAP_SUPABASE_KEY>' -- npx -y @totalaudiopromo/tap-mcp
{
"mcpServers": {
"tap-mcp": {
"command": "npx",
"args": [
"-y",
"@totalaudiopromo/tap-mcp"
],
"env": {
"TAP_SUPABASE_KEY": "<TAP_SUPABASE_KEY>",
"TAP_SUPABASE_URL": "<TAP_SUPABASE_URL>"
}
}
}
}
[mcp_servers.tap-mcp]
command = "npx"
args = ["-y", "@totalaudiopromo/tap-mcp"]
env = { TAP_SUPABASE_URL = "<TAP_SUPABASE_URL>", TAP_SUPABASE_KEY = "<TAP_SUPABASE_KEY>" }
{
"mcpServers": {
"tap-mcp": {
"command": "npx",
"args": [
"-y",
"@totalaudiopromo/tap-mcp"
],
"env": {
"TAP_SUPABASE_KEY": "<TAP_SUPABASE_KEY>",
"TAP_SUPABASE_URL": "<TAP_SUPABASE_URL>"
}
}
}
}
{
"servers": {
"tap-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@totalaudiopromo/tap-mcp"
],
"env": {
"TAP_SUPABASE_KEY": "<TAP_SUPABASE_KEY>",
"TAP_SUPABASE_URL": "<TAP_SUPABASE_URL>"
}
}
}
}
Put your own values in place of
<TAP_SUPABASE_URL> (Supabase project URL for your TAP workspace), <TAP_SUPABASE_KEY> (Supabase service role key for your TAP workspace).
The author’s registry entry marks them as required.
WhatsApp Business MCP: send messages, manage contacts, campaigns, and AI agents.
WhatsApp Business CRM: send messages, manage contacts, campaigns, and AI agents.
Manage contacts, campaigns, senders, and deliverability via SuperSend API
Manage Wati WhatsApp and Instagram contacts, chats, campaigns and templates, plus Astra AI agents.
Manage influencer campaigns, negotiations, contracts, and creator content on 1stCollab.
Google Ads management for AI agents — diagnose, optimize, and manage campaigns.
Cold email outreach: manage prospects, campaigns, replies and webhooks in Anymail.
Telegram CRM: manage contacts, conversations, tickets, campaigns and analytics.
Answers built from our own checks of this server.