home / mcp / spinitron v2 api mcp server
MCP Server generated by mcp.ag2.ai
Configuration
View docs{
"mcpServers": {
"ag2-mcp-servers-spinitron-v2-api": {
"command": "python",
"args": [
"mcp_server/main.py",
"stdio"
],
"env": {
"CONFIG": "{...}",
"SECURITY": "YOUR_API_KEYS",
"CONFIG_PATH": "mcp_server/mcp_config.json"
}
}
}
}This MCP Server provides a controllable gateway to the Spinitron V2 API using the Model Context Protocol, allowing clients to interact with the API through a consistent MCP interface. It runs locally and can be started in a standard input/output (stdio) mode or other transport modes, enabling efficient development, testing, and integration with MCP clients.
Start the server in stdio mode to interact with it through your development environment. Run your MCP client against the local process, sending requests and receiving responses as you would with any MCP server. Use the environment configuration options to specify how the server should load its configuration and security parameters.
Prerequisites: Python 3.9+ and uv (or a compatible Python runtime with uvicorn-like capabilities). Ensure you have a working Python environment and a shell or terminal.
Install the server package and dependencies in editable/development mode when you are actively developing or testing features.
Steps to install and run the server in a typical development setup:
git clone <repository-url>
cd mcp_server
pip install -e ".[dev]"
# Alternative with uv if you prefer
uv pip install --editable ".[dev]"Configuration and running options are designed to be flexible for local development and testing. You can start the server in stdio mode, which runs a Python process that accepts MCP commands on standard I/O. The server reads configuration and security parameters from environment variables or a JSON configuration file.
Environment variables you may use to configure runtime behavior include the following:
Launch the MCP server in the desired transport mode (e.g., stdio) and load configuration from environment variables or a JSON config file.
Read and parse the MCP configuration from CONFIG_PATH or CONFIG to configure endpoints, security, and transport.