Root Signals MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROOT_SIGNALS_API_KEY | Yes | Your Root Signals API key for authentication |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_pythonB | Execute Python code and return the output. Variables persist between executions. |
| list_variablesB | List all variables in the current session |
| install_packageB | Install a Python package using uv |
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 3 tools
Each tool has a clear, non-overlapping purpose: execute_python runs code, list_variables inspects session state, and install_package manages dependencies. There is no ambiguity in what each tool does.
All tool names follow the same verb_noun pattern with snake_case: execute_python, list_variables, install_package. The naming is perfectly consistent and predictable.
With only 3 tools, the server is tightly scoped to its purpose of providing a persistent Python execution environment. Each tool is essential and the count is well within the ideal range.
The server covers the core workflow of executing Python code, inspecting session variables, and installing packages. A minor gap is the lack of explicit session reset or variable removal, but these are not critical for typical usage.