Kion MCP Server
OfficialClick 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., "@Kion MCP Server What are my total cloud costs this month?"
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.
Kion MCP Server
Installation
For more detailed installation and usage instructions, please see oursupport documentation
Claude Desktop Extension
uv is currently a requirement for the desktop extension. Please see installation instructions
Once uv is installed, the Claude Desktop Extension can be installed by downloading the .dxt archive from the releases section, and then the archive can be installed via the extension settings in Claude Destkop, double clicking the file, or dragging the file onto the extension settings.
Dockerhub
Releases are published to the kionsoftware/kion-mcp repository, and can be run directly using docker.
Pypi
This package can be installed via pip.
pip install kion-mcp-server
Related MCP server: AWS Billing
Development Setup
Install uv
Install uv using homebrew with brew install uv
Install an MCP client
An MCP server needs an MCP client to run it. For development - the mcp inspector is a great tool for getting up and running with the server.
Add this server as a tool
For your MCP client there should be a json file defining what MCP Servers it has access to. Look up where this file is for your client and add something similar to this to it (json objects vary slightly by client check your client's documentation for the exact required JSON. MCP inspector has fields that can be configured directly.):
"KionMcp": {
"command": "uv",
"args": [
"--directory",
"<absolute path to this folder>",
"run",
"kion-mcp-server"
]
}NOTE: sometimes you will need to give an exact path to uv for some clients to work properly. Just run which uv and put the output of that as the command in the JSON
Available Tools
2 toolscheck_config_statusA
Call this tool AFTER manually updating the config file to activate API tools. ONLY call this tool if the setup_kion_config tool required manual config and the user says they've completed those steps. DO NOT CALL IT ON SUCCESSFUL CONFIGURATION.
This tool verifies the configuration is valid and activates all Kion API tools. Only needed if setup_kion_config required manual configuration steps.
After calling this tool, all Kion API tools should be available. If you don't see them, ask the user to send another message.
Inputs: no named parameters. Returns: result
setup_kion_configA
REQUIRED SETUP: This Kion MCP Server is missing required configuration.
Call this tool to begin setup. It will try to collect your Kion instance URL and authentication details.
After calling this tool:
If it returns "Configuration completed successfully!" and says tools should now be available, then all Kion API tools are ready. If you don't see them, ask the user to send another message.
If it requires manual configuration, follow the instructions provided, then call check_config_status to activate the API tools.
Once setup is complete, you can use this server to help the user report on their cloud spend, cloud compliance, Kion org chart and budgeting management, and other Kion features.
Inputs: no named parameters. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: setup_kion_config initiates configuration, check_config_status verifies after manual steps. No overlap.
Both tools follow a consistent verb_noun pattern using snake_case (setup_kion_config, check_config_status).
The server advertises features like cloud spend and compliance, but only provides two setup tools. The count is far too low for the stated scope.
The actual API tools for reporting and management are absent. The current tools only handle setup, leaving core functionality missing.
Maintenance
Related MCP Connectors
Query OneLens cloud-cost data in natural language: breakdowns, trends, cost centers. Read-only.
Ask about your Kodem Security data and act on findings in plain language, with your permissions.
FinOps assistant: query AWS, GCP and Azure cost, commitments, budgets and reports.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables natural language analysis of AWS cloud costs, waste audits, and budget insights across multiple profiles and regions.MIT
- AlicenseNot gradedqualityDmaintenanceEnables read-only AWS cost exploration, forecasting, and anomaly detection through natural language using user-connected IAM credentials.MIT
- FlicenseNot gradedqualityAmaintenanceEnables natural-language querying of AWS spending and Amazon Bedrock usage data, with breakdowns by day, region, service, instance type, user, and model, including optional cross-account analysis.-
- FlicenseNot gradedqualityAmaintenanceEnables natural-language queries of AWS spending by service, region, day, and instance type, and of Amazon Bedrock usage from CloudWatch model-invocation logs, including optional cross-account cost analysis.-