MCP Server Kalshi
by 9crusher
This is an MCP server designed to interact with the Kalshi REST API. It allows users to connect and utilize the Kalshi platform for trading and data retrieval.
Last updated: N/A
What is MCP Server Kalshi?
This is an MCP (Model Context Protocol) server that acts as an interface to the Kalshi REST API. It allows applications to interact with the Kalshi platform programmatically.
How to use MCP Server Kalshi?
The server can be configured using Claud Desktop (UVX or Docker) or for local development. Configuration involves setting environment variables for the Kalshi API key, private key path, and base URL. Refer to the README for detailed setup instructions for each environment.
Key features of MCP Server Kalshi
Integration with Kalshi REST API
Configuration via environment variables
Support for UVX and Docker deployment
Local development setup instructions
Demo account support
Use cases of MCP Server Kalshi
Automated trading on Kalshi
Data retrieval and analysis from Kalshi
Integration with other MCP-compatible applications
Building custom trading bots
Testing trading strategies in a demo environment
FAQ from MCP Server Kalshi
How do I get Kalshi API credentials?
How do I get Kalshi API credentials?
Follow the instructions provided in the Kalshi API documentation: https://trading-api.readme.io/reference/api-keys
How do I get a Kalshi test account?
How do I get a Kalshi test account?
Follow the instructions provided in the Kalshi API documentation: https://trading-api.readme.io/reference/creating-a-demo-account
What environment variables are required?
What environment variables are required?
The required environment variables are BASE_URL, KALSHI_API_KEY, and KALSHI_PRIVATE_KEY_PATH.
How do I run the server locally?
How do I run the server locally?
Create a .env file, install dependencies using uv pip install -e ., and run with uv run start.
How do I configure the server with Claud Desktop?
How do I configure the server with Claud Desktop?
You can configure the server using UVX or Docker. Refer to the README for the specific configuration details for each method.