home / mcp / jumpseller mcp server

Jumpseller MCP Server

MCP Server generated by mcp.ag2.ai

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "ag2-mcp-servers-jumpseller-api": {
      "command": "python",
      "args": [
        "mcp_server/main.py",
        "stdio"
      ],
      "env": {
        "CONFIG": "{...json config...}",
        "SECURITY": "{...security settings...}",
        "CONFIG_PATH": "path/to/mcp_config.json"
      }
    }
  }
}

You run an MCP (Model Context Protocol) Server to expose a structured, context-aware API for a given OpenAPI specification. This server lets MCP clients connect via local stdio or other transports, enabling streamlined communication and tooling around the JumpSeller API model.

How to use

To run and use your MCP server, start it in stdio mode and connect your MCP client to the local process. You can switch between transport modes later if needed, but stdio is the simplest for local development and testing.

How to install

# prerequisites
python3.9+
pip  # ensure pip is available

# install the MCP server package in editable/dev mode if you have a repo checked out
pip install -e ".[dev]"

# alternative: use uv if you prefer running via uv
uv pip install --editable ".[dev]"

# run a local server in stdio mode (see next section for exact command)
python mcp_server/main.py stdio

Additional sections

Configuration and runtime behavior are controlled via environment variables. The standard options include paths to a configuration file or a JSON string containing the MCP configuration, as well as security-related settings like API keys. You can customize how the server starts by supplying these environment values before launching the process.

Build, linting, static analysis, and tests are supported through dedicated scripts. Use the following commands to keep code quality high during development. These steps are optional for basic usage but highly recommended if you contribute.

- Linting and formatting - ruff check - ruff format - Static analysis - ./scripts/static-analysis.sh - Running tests with coverage - ./scripts/test.sh - ./scripts/test-cov.sh - Pre-commit hooks - pre-commit install

Configuration details

{
  "name": "jumpseller",
  "type": "stdio",
  "command": "python",
  "args": ["mcp_server/main.py", "stdio"],
  "env": {
    "CONFIG_PATH": "path/to/mcp_config.json",
    "CONFIG": "{...json config...}",
    "SECURITY": "{...security settings...}"
  }
}

Security and access

Security-related environment variables can be set to control access to the MCP server. Provide API keys or tokens as needed by your deployment. Always keep sensitive values out of source control and load them from secure sources at runtime.

Troubleshooting

If the server fails to start, verify that Python 3.9+ is installed and that you are using python to invoke mcp_server/main.py. Ensure the required environment variables are set and that any paths referenced in CONFIG_PATH or CONFIG are correct. Check log output for hints about misconfigurations or missing dependencies.

Available tools

lint

Lint the codebase and ensure formatting conforms to project standards using ruff.

format

Automatically format code with ruff format to maintain consistent styling.

static-analysis

Run static analysis tools (mypy, bandit, semgrep) to catch issues early.

tests

Run test suite and generate a coverage report to verify correctness.

build

Build the MCP server package for distribution.

publish

Publish the built MCP server package to the configured registry.