home / mcp / subscriptions api v3 mcp server
MCP Server generated by mcp.ag2.ai
Configuration
View docs{
"mcpServers": {
"ag2-mcp-servers-subscriptions-api-v3": {
"command": "python",
"args": [
"mcp_server/main.py",
"stdio"
],
"env": {
"CONFIG": "{...} (JSON string with your MCP config)",
"SECURITY": "API keys or other security parameters",
"CONFIG_PATH": "mcp_server/mcp_config.json"
}
}
}
}You run an MCP server that connects to a predefined API and exposes a stable, protocol-driven interface for clients to interact with the Subscriptions API v3. This server helps you manage context-aware requests and keeps interactions decoupled from specific client implementations, making integration straightforward across languages and platforms.
Start the server in stdio mode to run locally and interact with your MCP client. The server reads its configuration from environment variables or a JSON configuration file. To begin, launch the server and point your MCP client at the local process.
Prerequisites: Install Python 3.9 or newer. Ensure you have pip and a runner available as needed.
# Prerequisites
python3 --version
# Should be Python 3.9+
pip --version
# Optional: install uv for local testing
pip install --editable .Configuration and security are handled through environment variables or a JSON config file. The built-in options let you specify where to load configuration from, as well as security parameters to control access.
Run command for the MCP server in stdio mode:
``text
``
The server supports loading configuration from a file or inline JSON. Use CONFIG_PATH to point at a file path or CONFIG to provide a JSON string. You can also supply SECURITY-specific variables to control access to the MCP endpoints.
If the server fails to start, verify Python 3.9+ is installed, the required dependencies are installed, and that the environment variables CONFIG_PATH or CONFIG are correctly set. Check for clear error messages indicating missing files or invalid JSON.
Ruff is used for linting and formatting to enforce consistent code quality.
Static analysis tools (mypy, bandit, semgrep) are run to catch type issues and potential security risks.
Pytest is used to run tests and generate coverage reports.
Pre-commit hooks help ensure code quality before each commit.