Tropicalia MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TROPICALIA_API_KEY | Yes | API key for authentication | |
| TROPICALIA_PROJECT | Yes | Project ID for this connection |
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 |
|---|---|
| searchA | Search documents in a Tropicalia project. Available Parameters:
Natural Language Examples:
|
| get_configB | Get current Tropicalia MCP configuration |
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 2 tools
The two tools serve completely different purposes: `search` performs document queries while `get_config` retrieves server configuration. There is no possible confusion between them.
Both names use imperative verbs, but one is a bare verb (`search`) while the other follows a verb_noun pattern (`get_config`). This is a minor deviation from a consistent pattern.
With only 2 tools, the server feels thin for a general-purpose 'Tropicalia MCP Server'. However, the tools cover the core search and configuration needs, so it is borderline rather than severely under-scoped.
The search tool is feature-rich with multiple strategies and options, and `get_config` covers configuration. Missing operations like listing indexes or managing documents are minor gaps that agents can work around.