Platoona MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLATOONA_API_KEY | Yes | Your Platoona Connect API key. | |
| PLATOONA_BASE_URL | No | Custom API URL (for self-hosted). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search-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. |
| list-integrationsA | List available integrations/apps that can be connected. |
| list-connectionsA | List all active integration connections. Use this to see which integrations are already connected. |
| connect-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. |
| execute-toolB | Execute an integration action/tool. Requires an active connection for the integration. |
| disconnect-appA | Disconnect from an integration, revoking all connections. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.