Transporeon Company Settings MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TP_SETTINGS_TOKEN_AC | Yes | Acceptance environment token | |
| TP_SETTINGS_TOKEN_IN | Yes | Integration environment token | |
| TP_SETTINGS_TOKEN_PD | Yes | Production environment token |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_company_settingsB | List all company settings from the Transporeon settings API. Returns settings formatted as Markdown with decoded values for encoded settings. |
| get_company_settingA | Get a specific company setting by key name. Returns the setting with decoded value if it was encoded. |
| search_in_settingA | Search for specific text within a company setting and return matching lines with surrounding context. |
| verify_environment_tokensA | Verify that all environment tokens (pd, in, ac) are valid by making test requests to each environment. This helps diagnose authentication issues. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Server Status | Current server status |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: listing all settings, retrieving a specific setting, searching within a setting, and verifying environment tokens. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern in snake_case (list_company_settings, get_company_setting, search_in_setting, verify_environment_tokens). The naming is predictable and readable.
With 4 tools, the set is well-scoped for a company settings server. Each tool covers a necessary operation without redundancy, and the count is within the ideal range.
The tool set covers the full lifecycle of reading and searching company settings, plus a diagnostic tool for environment tokens. No obvious missing operations are apparent for the stated purpose.