RaiseKit vs MCP Server

A side-by-side look at the RaiseKit and MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

R
RaiseKitCommunication
CRM for VC fundraising. Pipeline, Gmail drafts, deck signals, VC intel — from your AI.12EmergingAuth: not declared
MCP Server logoMCP ServerCommunication · Local subprocess (stdio)244 WhatsApp Business tools: send messages, automate workflows, run campaigns, and manage CRM. Streamable HTTP + stdio.43FairAuth: api key required

Verdict: choose RaiseKit for communication work; choose MCP Server for communication as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

R
Choose RaiseKit when

  • You need dedicated capabilities in the Communication domain.
Explore RaiseKit

MCP Server logoChoose MCP Server when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: WAZION_API_KEY.
Explore MCP Server

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
R
RaiseKit
MCP Server logoMCP Server
CategoryCommunicationCommunication
Quality signal12/100 · Emerging43/100 · Fair
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredBYOK (pay the provider)
Required env varsNone listedWAZION_API_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars—2
Directory activity 1 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

RaiseKit tools

No tool names declared yet. Check the project README from the listing page.

MCP Server tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

RaiseKit

No confirmed install command for RaiseKit yet — follow the setup steps linked from its listing page rather than a guessed package name.

MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "wazionapps-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@wazion/mcp-server"
      ],
      "env": {
        "WAZION_API_KEY": "YOUR_WAZION_API_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

RaiseKit is categorized under Communication and uses an install path we have not confirmed yet. MCP Server belongs to Communication and uses a local stdio subprocess. Pick RaiseKit for communication work and MCP Server for communication.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. RaiseKit has no confirmed install command yet — follow its own setup instructions.

RaiseKit has no declared pricing — check the project's own site. MCP Server is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add raisekit and wazionapps-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, RaiseKit has a quality signal of 12/100 (Emerging) with 1 views, 0 installs and 0 GitHub stars. MCP Server has 43/100 (Fair) with 5 views, 0 installs and 2 GitHub stars.