WhatsApp MCP Server by Charlesagui
CharlesaguiLABSCO SUMMARY
A starter, and it says so.
The repository calls itself a demo and the shape follows: one provider, a hard-coded filter, a build step and an absolute path in your config. What it does show is worth understanding — actions are loaded from ActionKit at runtime for a specific Paragon user, so what the agent can do in Slack is exactly what that person authorised and nothing more.
What it is
A demo MCP server for ActionKit. It loads ActionKit's action catalogue for the signed-in Paragon user and filters it down to Slack; that filter lives in index.ts and can be removed to expose the rest.
What you get
- ActionKit's Slack actions available as tools, acting on behalf of the authenticated user
- Scope set by one line of code — remove the Slack filter in
index.tsand the other ActionKit actions come through - A visible check that it worked: a hammer icon listing the Slack tools and a plug icon showing the connection
Requirements
Paragon credentials in three environment variables — PARAGON_PROJECT_ID, SIGNING_KEY, and USER set to the user authenticated in the Paragon Connect Portal. That user has to have authorised Slack, or the Slack tools cannot act on their behalf. Clone the repository, npm install, npm run build, and point Claude Desktop at build/index.js with an absolute path.
Setup effort
Build from source — git clone https://github.com/jackmuva/mcp-actionkit.git
USE CASES
01
Posting to Slack from a conversation
Let the assistant use the Slack actions the connected user already authorised, without a bot token of its own.
02
Going beyond Slack
Drop the filter in the source to expose the rest of the ActionKit catalogue to the same session.
03
Confirming the connection is live
Check the tool and connection indicators in Claude Desktop before assuming the authorisation went through.
BEFORE YOU INSTALL
What to know first
Requires
- Node.js and npm
- Claude Desktop
- A Paragon project with ActionKit: PARAGON_PROJECT_ID, SIGNING_KEY, and a USER authenticated to Slack through the Paragon Connect Portal
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
This one is built from source rather than installed with a single command.
Server setup
TERMINAL
git clone https://github.com/jackmuva/mcp-actionkit.git
cd mcp-actionkit
npm install
npm run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"mcp-actionkit": {
"command": "node",
"args": [
"<YOUR_ABSOLUTE_PATH>/mcp-actionkit/build/index.js"
],
"env": {
"USER": "",
"PARAGON_PROJECT_ID": "",
"SIGNING_KEY": ""
}
}
}
}<YOUR_ABSOLUTE_PATH> is the full path of the folder that holds your mcp-actionkit clone. The empty env values are your Paragon credentials: PARAGON_PROJECT_ID and SIGNING_KEY from your Paragon project, and USER as the user authenticated in the Paragon Connect Portal — log in as that user at demo.useparagon.com and authenticate to Slack first.
