Yamcs MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Yamcs MCP Server list the current alarms in the simulator instance"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Yamcs MCP Server
A comprehensive Model Context Protocol (MCP) server for Yamcs (Yet Another Mission Control System) that exposes Yamcs capabilities as standardized MCP tools and resources.
Overview
The Yamcs MCP Server enables AI assistants to interact with mission control systems through natural language by providing a bridge between MCP-compatible clients and Yamcs instances. It implements the MCP protocol using FastMCP 2.x with a modular component architecture.
Related MCP server: Planet MCP
Features
Mission Database (MDB): Access to parameters, commands, algorithms, and space systems
TM/TC Processing: Real-time telemetry monitoring and command execution
Link Management: Monitor and control data links
Object Storage: Manage buckets and objects in Yamcs storage
Instance Management: Control Yamcs instances and services
Alarm Management: Monitor and acknowledge alarms with summary statistics
Installation
Prerequisites
Python 3.12 or higher
Yamcs server instance (local or remote)
uv package manager (recommended) or pip
Using uv (recommended)
# Clone the repository
git clone https://github.com/PaulMRamirez/yamcs-mcp-server.git
cd yamcs-mcp-server
# Install dependencies
uv sync
# Run the server
uv run yamcs-mcpUsing pip
# Clone the repository
git clone https://github.com/PaulMRamirez/yamcs-mcp-server.git
cd yamcs-mcp-server
# Create virtual environment
python -m venv venv
source venv/bin/activate # On Windows: venv\Scripts\activate
# Install the package
pip install -e .
# Run the server
yamcs-mcpRunning Yamcs
You'll need a running Yamcs instance. The easiest way is using Docker:
docker run -d --name yamcs -p 8090:8090 yamcs/example-simulationThis will start Yamcs with a simulator instance that includes example telemetry data.
Configuration
The server can be configured using environment variables or a .env file:
# Yamcs connection settings
YAMCS_URL=http://localhost:8090
YAMCS_INSTANCE=simulator
YAMCS_USERNAME=admin
YAMCS_PASSWORD=password
# Server toggles
YAMCS_ENABLE_MDB=true
YAMCS_ENABLE_PROCESSOR=true
YAMCS_ENABLE_LINKS=true
YAMCS_ENABLE_STORAGE=true
YAMCS_ENABLE_INSTANCES=true
YAMCS_ENABLE_ALARMS=true
YAMCS_ENABLE_COMMANDS=true
# Server settings
MCP_TRANSPORT=stdio
MCP_HOST=127.0.0.1
MCP_PORT=8000Usage
With Claude Desktop
Add the server to your Claude Desktop configuration:
{
"mcp-servers": {
"yamcs": {
"command": "uv",
"args": ["--directory", "/path/to/yamcs-mcp-server", "run", "yamcs-mcp"],
"env": {
"YAMCS_URL": "http://localhost:8090",
"YAMCS_INSTANCE": "simulator"
}
}
}
}Important:
Replace
/path/to/yamcs-mcp-serverwith the actual path to your yamcs-mcp-server directoryThe
--directoryargument is required for uv to find the correct projectIf
uvis not in your PATH, use the full path to uv (e.g.,/Users/PaulMRamirez/.local/bin/uv)
Available Tools
The server exposes numerous tools organized by server:
MDB Tools
mdb_list_parameters- List available parametersmdb_describe_parameter- Get parameter detailsmdb_list_commands- List available commandsmdb_describe_command- Get command detailsmdb_list_space_systems- List space systemsmdb_describe_space_system- Get space system details
Processor Tools
processors_list_processors- List available processorsprocessors_describe_processor- Get processor detailsprocessors_delete_processor- Delete a processorprocessors_issue_command- Issue a commandprocessors_subscribe_parameters- Subscribe to parameter updates
Link Tools
links_list_links- List all data linkslinks_describe_link- Get detailed link informationlinks_enable_link- Enable a data linklinks_disable_link- Disable a data link
Instance Tools
instances_list_instances- List Yamcs instancesinstances_describe_instance- Get instance detailsinstances_start_instance- Start an instanceinstances_stop_instance- Stop an instance
Storage Tools
storage_list_buckets- List storage bucketsstorage_list_objects- List objects in a bucketstorage_upload_object- Upload an objectstorage_download_object- Download an object
Alarm Tools
alarms_list_alarms- List active alarms with summary countsalarms_describe_alarm- Get detailed alarm informationalarms_acknowledge_alarm- Acknowledge an alarmalarms_shelve_alarm- Temporarily shelve an alarmalarms_unshelve_alarm- Unshelve an alarmalarms_clear_alarm- Clear an alarmalarms_read_log- Read alarm history
Command Tools
commands_list_commands- List available commands for executioncommands_describe_command- Get detailed command informationcommands_run_command- Execute a command (supports dry-run)commands_read_log- Read command execution history
Available Resources
The server also provides read-only resources:
mdb://parameters- List all parametersprocessors://list- List all processors with detailslinks://status- Show status of all linksinstances://list- List all instances with detailsalarms://list- Show active alarms summary
Development
Setting up the development environment
# Install development dependencies
uv sync --all-extras
# Install pre-commit hooks
pre-commit install
# Run tests
uv run pytest
# Run linting
uv run ruff check .
# Run type checking
uv run mypy src/Testing
Run the test suite:
# Run all tests
uv run pytest
# Run with coverage
uv run pytest --cov=yamcs_mcp --cov-report=html
# Run specific test file
uv run pytest tests/test_server.py
# Run with verbose output
uv run pytest -vTesting Without a Yamcs Server
The server can run in demo mode without connecting to a real Yamcs server:
# Run in demo mode (will show a warning about connection failure but continue)
uv run python -m yamcs_mcp.server
# Or use the demo script
uv run python run_demo.pyProject Structure
yamcs-mcp-server/
├── src/
│ └── yamcs_mcp/
│ ├── server.py # Main server entry point
│ ├── servers/ # MCP servers
│ │ ├── base_server.py # Base class for all servers
│ │ ├── mdb.py # Mission Database
│ │ ├── processors.py # TM/TC Processing
│ │ ├── links.py # Link management
│ │ ├── storage.py # Object storage
│ │ ├── instances.py # Instance management
│ │ └── alarms.py # Alarm management
│ ├── client.py # Yamcs client management
│ ├── config.py # Configuration
│ └── types.py # Type definitions
├── tests/ # Test suite
├── scripts/ # Test scripts
└── CLAUDE.md # AI assistant guidanceTroubleshooting
Common Issues
"Input validation error" when executing commands
Problem: Getting errors like '{"voltage_num": 1}' is not valid under any of the given schemas
Solution: The commands/run_command tool now accepts both formats. The server will automatically parse JSON strings to objects.
Both formats are now supported:
✅ Args as object (preferred):
{
"command": "/YSS/SIMULATOR/SWITCH_VOLTAGE_OFF",
"args": {"voltage_num": 1}
}✅ Args as JSON string (automatically parsed):
{
"command": "/YSS/SIMULATOR/SWITCH_VOLTAGE_OFF",
"args": "{\"voltage_num\": 1}"
}✅ Command without arguments:
{
"command": "/TSE/simulator/get_identification"
}✅ Multiple arguments:
{
"command": "/YSS/SIMULATOR/SET_HEATER",
"args": {
"heater_id": 2,
"temperature": 25.5,
"duration": 300
}
}Connection to Yamcs fails
Problem: Server can't connect to Yamcs at startup
Solution:
Ensure Yamcs is running:
docker ps | grep yamcsCheck the URL is correct:
curl http://localhost:8090/apiThe server will continue in demo mode even if Yamcs is unavailable
Enum serialization errors
Problem: Errors about unable to serialize enum types
Solution: This has been fixed in the latest version. Update to the latest version of the server.
Contributing
Contributions are welcome! Please read our Contributing Guidelines before submitting pull requests.
License
This project is licensed under the MIT License - see the LICENSE file for details.
Acknowledgments
Available Tools
34 toolsalarms_acknowledge_alarmB
Acknowledge a specific alarm.
Inputs: alarm (required), sequence_number (required), comment, instance, +1 more. Returns: object
alarms_clear_alarmC
Clear a specific alarm.
Inputs: alarm (required), sequence_number (required), comment, instance, +1 more. Returns: object
alarms_describe_alarmA
Get detailed information about a specific alarm.
Inputs: alarm (required), instance, processor. Returns: object
alarms_list_alarmsB
List active alarms on a processor.
Inputs: instance, processor, include_pending. Returns: object
alarms_read_logC
Read alarm history from the archive.
Inputs: name, stop, lines, start, +2 more. Returns: object
alarms_shelve_alarmB
Shelve (temporarily suspend) an alarm.
Inputs: alarm (required), sequence_number (required), comment, instance, +1 more. Returns: object
alarms_unshelve_alarmB
Unshelve (reactivate) a previously shelved alarm.
Inputs: alarm (required), sequence_number (required), comment, instance, +1 more. Returns: object
commands_describe_commandB
Get detailed information about a command including arguments.
Inputs: command (required), instance. Returns: object
commands_list_commandsC
List available commands for execution.
Inputs: limit, search, system, instance. Returns: object
commands_read_logC
Read command execution history.
Inputs: lines, since, until, command, +1 more. Returns: object
commands_run_commandA
Execute a command on Yamcs.
To execute SWITCH_VOLTAGE_OFF with voltage_num=1, call this tool with: command="/YSS/SIMULATOR/SWITCH_VOLTAGE_OFF" args={"voltage_num": 1}
To execute with multiple arguments: command="/YSS/SIMULATOR/SOME_CMD" args={"arg1": "value1", "arg2": 123}
The args parameter should be a dictionary mapping argument names to values. If you pass a JSON string, it will be automatically parsed.
Inputs: command (required), args, comment, dry_run, +3 more. Returns: object
health_checkA
Check overall server health.
Returns: dict: Server health status
Inputs: no named parameters. Returns: object
instances_describe_instanceB
Get comprehensive information about a Yamcs instance.
Inputs: instance. Returns: object
instances_list_instancesA
List all Yamcs instances.
Returns: dict: List of instances
Inputs: no named parameters. Returns: object
instances_start_instanceC
Start a Yamcs instance.
Inputs: instance. Returns: object
instances_stop_instanceB
Stop a Yamcs instance.
Inputs: instance. Returns: object
links_describe_linkB
Get comprehensive information about a specific link.
Inputs: link (required), instance. Returns: object
links_disable_linkC
Disable a data link.
Inputs: link (required), instance. Returns: object
links_enable_linkC
Enable a data link.
Inputs: link (required), instance. Returns: object
links_list_linksB
List all data links.
Inputs: instance. Returns: object
mdb_commandsC
List commands from the Mission Database.
Inputs: search, system, instance. Returns: object
mdb_get_commandC
Get detailed information about a specific command.
Inputs: command (required), instance. Returns: object
mdb_get_parameterC
Get detailed information about a specific parameter.
Inputs: parameter (required), instance. Returns: object
mdb_parametersC
List parameters from the Mission Database.
Inputs: search, system, instance. Returns: object
mdb_space_systemsB
List space systems from the Mission Database.
Inputs: instance. Returns: object
processors_delete_processorB
Delete a processor.
Inputs: processor (required), instance. Returns: object
processors_describe_processorB
Get comprehensive information about a processor.
Inputs: processor (required), instance. Returns: object
processors_list_processorsA
List all processors.
Inputs: instance. Returns: object
storage_bucketsC
List storage buckets.
Inputs: instance. Returns: object
storage_create_bucketB
Create a new storage bucket.
Inputs: name (required), instance. Returns: object
storage_delete_objectC
Delete an object from storage.
Inputs: bucket (required), object_name (required), instance. Returns: object
storage_get_object_infoC
Get information about a specific object.
Inputs: bucket (required), object_name (required), instance. Returns: object
storage_objectsB
List objects in a bucket.
Inputs: bucket (required), limit, prefix, instance. Returns: object
test_connectionB
Test connection to Yamcs server.
Returns: dict: Connection test results
Inputs: no named parameters. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 34 tools
Each tool has a clearly distinct purpose, grouped by resource type (alarms, commands, instances, etc.) with specific actions (list, describe, run, etc.). No overlapping functionality.
Tool names consistently use snake_case and a prefix_group_verb_noun pattern, though the 'mdb' group mixes noun-only names (mdb_commands, mdb_parameters) with verb-noun names (mdb_get_command), creating minor inconsistency.
With 34 tools, the count exceeds the recommended range for coherence. While the server covers a broad domain, the large number may confuse agents and dilute focus.
The tool set covers major operations for alarms, commands, instances, links, MDB, processors, and storage. Missing creation tools for links and processors are notable but likely intentional given the domain.
Related MCP Connectors
Connects AI assistants to TrackingTime for querying time entries, projects, tasks, customers, and team data using natural language.
Manage uptime monitors and incidents and search logs, metrics and traces from an AI assistant.
Query your team's drift, vulnerability, and upgrade data from any AI assistant. OAuth 2.1, 51 tools.
Deploy, monitor, and manage your OpenClaw AI assistants via natural language.
Related MCP Servers
- AlicenseAqualityFmaintenanceProvides seamless integration with NASA's public APIs, enabling AI assistants to access space and astronomy data including APOD, Mars rover photos, Near-Earth Objects, space weather events, and Earth imagery.510 npmMIT

Planet MCPofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with the Planet API for satellite imagery ordering, subscriptions, and data management through natural language.18Apache 2.0- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with SpacetimeDB instances, query tables, call reducers, and manage database operations.4MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Argo CD applications, managing clusters, applications, and resources through natural language.Apache 2.0