Tranna MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Development, test, or production | production |
| LOG_LEVEL | No | Debug, info, warn, or error | info |
| HEALTH_HOST | No | Interface for health checks | 0.0.0.0 |
| HEALTH_PORT | No | Health HTTP port for native execution | 3000 |
| HEALTH_ENABLED | No | Enables the health HTTP server | true |
| SERVICE_VERSION | No | Version returned in server status | 0.1.0 |
| HOST_HEALTH_PORT | No | Host port mapped by Docker Compose | 3000 |
| META_CONNECTOR_ENABLED | No | Enables the real Meta connector after all required META_* values are supplied | false |
| EXAMPLE_CONNECTOR_ENABLED | No | Enables the fake demonstration connector and its fake-data MCP tool | false |
| META_ALLOW_WRITE_OPERATIONS | No | Allows publishing, campaign creation, campaign state changes, and budget updates | false |
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 |
|---|---|
| tranna_get_service_statusA | Returns the server's runtime readiness, authentication placeholder status, and registered connector statuses. No platform data is accessed. |
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 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clearly stated as a status check.
The single tool name 'tranna_get_service_status' follows a clear verb_noun pattern in snake_case, making it descriptive and internally consistent, though there are no other tools to compare.
A single status-check tool is far too few to constitute a substantive MCP server, feeling like a placeholder or stub rather than a useful collection.
The tool only returns status information and explicitly accesses no platform data, leaving no operations for actual work, which is severely incomplete for any practical use.