Platoona MCP Server
OfficialAllows sending messages to Slack channels and interacting with Slack integration actions.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Platoona MCP Server Search for tools to send a Slack message"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Platoona MCP Server
An MCP (Model Context Protocol) server that connects AI assistants like Claude Code, Cursor, and others to 10,000+ SaaS integrations through Platoona Connect.
Features
search-tools - Semantic search (RAG) for 10K+ integration actions
list-integrations - Browse available integrations
list-connections - View your active connections
connect-app - Connect to integrations (OAuth or API key)
execute-tool - Execute integration actions
disconnect-app - Disconnect from integrations
Related MCP server: Catalyst MCP Server
Prerequisites
A Platoona Connect account
Your Platoona API key (get it from Platoona Connect Portal)
Node.js 18+
Installation
Option 1: Install from npm (recommended)
npm install -g @platoona/mcpOption 2: Install from source
git clone https://github.com/platoona/platoona-mcp.git
cd platoona-mcp
npm install
npm run buildConfiguration
Environment Variables
Variable | Required | Description |
| Yes | Your Platoona Connect API key |
| No | Custom API URL (for self-hosted) |
Note: User ID is automatically derived from your API key using a deterministic hash. This ensures consistent identification across sessions - same API key always produces the same user ID (mcp_<hash>).
Usage with Claude Code
Add to your Claude Code configuration (~/.claude/claude_desktop_config.json):
{
"mcpServers": {
"platoona": {
"command": "npx",
"args": ["@platoona/mcp"],
"env": {
"PLATOONA_API_KEY": "platoona_xxx..."
}
}
}
}Or if installed globally:
{
"mcpServers": {
"platoona": {
"command": "platoona-mcp",
"env": {
"PLATOONA_API_KEY": "platoona_xxx..."
}
}
}
}Usage with Cursor
Add to your Cursor MCP settings:
{
"mcpServers": {
"platoona": {
"command": "npx",
"args": ["@platoona/mcp"],
"env": {
"PLATOONA_API_KEY": "platoona_xxx..."
}
}
}
}Available Tools
search-tools
Search for integration tools using semantic/RAG search.
Input:
- query: "send a message to slack"
- integrationFilter: "slack" (optional)
- limit: 10 (optional)
Output:
- List of matching tools with IDs, descriptions, and similarity scoreslist-integrations
List available integrations that can be connected.
Input:
- search: "email" (optional)
- limit: 20 (optional)
Output:
- List of integrations with IDs, names, and slugslist-connections
List all active connections for your MCP user.
Input: (none required)
Output:
- List of connections with IDs, status, and expirationconnect-app
Connect to an integration.
Input:
- integration: "slack" or UUID
- apiKey: "..." (for API key integrations)
- scopes: ["read", "write"] (for OAuth)
Output:
- For API key: connectionId and status
- For OAuth: authUrl to complete authorizationexecute-tool
Execute an integration action.
Input:
- action: "slack:send-message" or UUID
- parameters: { channel: "#general", text: "Hello!" }
- timeout: 30000 (optional)
Output:
- Execution result with output datadisconnect-app
Disconnect from an integration.
Input:
- integration: "slack" or UUID
Output:
- Success confirmationExample Workflow
Search for tools:
"Search for tools to send a Slack message"Check connections:
"List my Slack connections"Connect if needed:
"Connect to Slack" (will return OAuth URL)Execute the tool:
"Send a Slack message to #general saying Hello!"
API Endpoints Used
This MCP uses the dedicated /mcp/* endpoints for simplified integration:
Endpoint | Purpose |
| RAG search for integration tools |
| Connect to integration (OAuth or API key) |
| Execute an integration action |
| List active connections |
| Disconnect from integration |
| List available integrations |
Development
# Install dependencies
bun install
# Run in development mode
bun run dev
# Build for production
bun run build
# Start production server
bun startLicense
MIT
Support
Available Tools
6 toolsconnect-appConnect AppA
Connect to an integration/app. For API key integrations, provide the API key directly. For OAuth integrations, this will return an authorization URL for the user to complete.
Inputs: integration (required), apiKey, scopes. Returns: status, authUrl, message, connectionId
disconnect-appDisconnect AppA
Disconnect from an integration, revoking all connections.
Inputs: integration (required). Returns: message, success
execute-toolExecute ToolB
Execute an integration action/tool. Requires an active connection for the integration.
Inputs: action (required), parameters (required), timeout. Returns: error, output, status, success, +1 more
list-connectionsList ConnectionsA
List all active integration connections. Use this to see which integrations are already connected.
Inputs: no named parameters. Returns: connections, totalConnections
list-integrationsList IntegrationsA
List available integrations/apps that can be connected.
Inputs: limit, search. Returns: totalFound, integrations
search-toolsSearch ToolsA
Search for available integration tools/actions using semantic search (RAG). Use this to discover what tools are available for a specific task or integration.
Inputs: query (required), limit, integrationFilter. Returns: tools, totalFound
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool has a clearly distinct role: search-tools for discovering actions, list-integrations for available apps, list-connections for active connections, connect-app for establishing connections, execute-tool for running actions, and disconnect-app for revoking connections. No two tools overlap in purpose.
All tools follow a consistent verb-noun pattern with lowercase hyphenation: search-tools, list-integrations, list-connections, connect-app, execute-tool, disconnect-app. The naming is uniform and predictable.
With six tools, the set is well-scoped for an integration management server. Each tool covers a necessary part of the connection lifecycle without unnecessary redundancy or bloat.
The tool surface covers the full integration lifecycle: discovery (search-tools), catalog (list-integrations), status (list-connections), connection establishment (connect-app), usage (execute-tool), and teardown (disconnect-app). No obvious gaps exist for the stated purpose.
Maintenance
Related MCP Connectors
Connect any AI agent to 1,000+ apps and 27,000+ actions through one remote MCP server (OAuth).
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
Unified MCP Server is a remote MCP connector for AI agents and vertical AI products that provides access to 22,000+ authorized SaaS tools across 400+ integrations and 24 categories directly inside LLMs (Claude, GPT, Gemini, Cohere). Tools operate only on explicitly authorized customer connections, enabling agents to safely read and write against live third-party systems.
One MCP server for the services your AI needs: memory, files, Microsoft 365, kanban and more.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA comprehensive MCP server providing over 390 tools across 66 providers, including major SaaS platforms like GitHub, Slack, and Stripe. It enables AI assistants to interact directly with a wide array of public APIs and utility services through a single interface.-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that loads and serves Knowledge Packs to connect AI assistants with business systems like databases, DevOps tools, and APIs.1-
- AlicenseBqualityDmaintenanceA comprehensive MCP server that connects AI assistants to GoHighLevel CRM, enabling management of contacts, conversations, calendars, pipelines, payments, and more through 60+ tools.6437 npm1MIT
- FlicenseNot gradedqualityDmaintenanceA single MCP server that exposes safe, permission-checked tools for AI assistants to reach file systems, databases, APIs, Git, cloud services, and business applications.-