home / mcp / kumpeapps api mcp server
MCP Server generated by mcp.ag2.ai
Configuration
View docs{
"mcpServers": {
"ag2-mcp-servers-kumpeapps-api": {
"url": "https://api.apis.guru/v2/specs/kumpeapps.com/5.0.0/openapi.json",
"headers": {
"CONFIG": "{ \"example\":\"config_json_here\" }",
"SECURITY": "YOUR_API_KEY_OR_SECRET",
"CONFIG_PATH": "path/to/mcp_config.json"
}
}
}
}You run an MCP Server that exposes an OpenAPI-based API context so clients can interact with a model-context protocol. This server automates the integration using a predefined OpenAPI URL and provides both a remote HTTP connection option and a local standard I/O (stdio) runtime for development and testing.
Connect with an MCP client to either the remote HTTP endpoint or the local stdio runtime. For the remote option, point your MCP client to the provided OpenAPI-based URL to fetch the API context and perform allowed actions. For development and testing, start the local stdio server and connect your MCP client to the local process. In both modes, your client can discover available contexts, actions, and data sources exposed by this MCP server and perform the supported operations in a structured, type-safe way.
Prerequisites: Python 3.9 or newer, and a working Python package manager (pip). You may also use uv as an alternative to start the server within the development workflow.
Step 1: Clone the repository and navigate into it.
Step 2: Install dependencies.
Step 3: Start the MCP server in stdio mode to run locally.
Configuration and security: You can configure the MCP server behavior through environment variables. The following variables are recognized by the runtime and can be set to customize the server’s configuration loading and security parameters. If you need to provide a full JSON-based configuration, you can also supply the JSON content directly via a string.
Environment variables used by the runtime include: CONFIG_PATH, CONFIG, and SECURITY. CONFIG_PATH should point to a JSON file containing the MCP server configuration. CONFIG can hold a JSON string with the configuration. SECURITY holds additional security-related parameters such as API keys. Provide placeholder values if you are just wiring up the environment for development.
Linting and formatting tool used to check code quality and enforce style across the project.
Static type checker to catch type errors before runtime.
Test framework used to run unit tests and generate coverage reports.
Build and publish tool used to package and publish the MCP server.
Pre-commit hooks configured to run linting, formatting, and basic checks before commits.