MCP Server
This project is an MCP (Model Context Protocol) Server for the given OpenAPI URL - https://api.apis.guru/v2/specs/openpolicy.local/0.28.0/openapi.json, auto-generated using AG2's MCP builder.
Prerequisites
- Python 3.9+
- pip and uv
Installation
- Clone the repository:
git clone <repository-url> cd mcp-server
- Install dependencies:
The .devcontainer/setup.sh script handles installing dependencies using
pip install -e ".[dev]". If you are not using the dev container, you can run this command manually.pip install -e ".[dev]"
Alternatively, you can useuv:uv pip install --editable ".[dev]"
Development
This project uses ruff for linting and formatting, mypy for static type checking, and pytest for testing.
Linting and Formatting
To check for linting issues:
ruff check
To format the code:
ruff format
These commands are also available via the scripts/lint.sh script.
Static Analysis
To run static analysis (mypy, bandit, semgrep):
./scripts/static-analysis.sh
This script is also configured as a pre-commit hook in .pre-commit-config.yaml.
Running Tests
To run tests with coverage:
./scripts/test.sh
This will run pytest and generate a coverage report. For a combined report and cleanup, you can use:
./scripts/test-cov.sh
Pre-commit Hooks
This project uses pre-commit hooks defined in .pre-commit-config.yaml. To install the hooks:
pre-commit install
The hooks will run automatically before each commit.
Running the Server
The MCP server can be started using the mcp_server/main.py script. It supports different transport modes (e.g., stdio, sse, streamable-http).
To start the server (e.g., in stdio mode):
python mcp_server/main.py stdio
The server can be configured using environment variables:
CONFIG_PATH: Path to a JSON configuration file (e.g., mcp_server/mcp_config.json).CONFIG: A JSON string containing the configuration.SECURITY: Environment variables for security parameters (e.g., API keys).
Refer to the if __name__ == "__main__": block in mcp_server/main.py for details on how these are loaded.
The tests/test_mcp_server.py file demonstrates how to start and interact with the server programmatically for testing.
Building and Publishing
This project uses Hatch for building and publishing. To build the project:
hatch build
To publish the project:
hatch publish
These commands are also available via the scripts/publish.sh script.
1 maintainer
Metadata
1 maintainer
Release files for mcp_server-shalini12345 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| mcp_server_shalini12345-0.0.1.tar.gz | 18.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_server_shalini12345-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 30.7 kB
Release files / mcp_server_shalini12345-0.0.1.tar.gz
| Download URL | mcp_server_shalini12345-0.0.1.tar.gz |
|---|---|
| Size | 18.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dc82f5eb69d2bec6d1c8d7a4bc6e7764727650e01fa6dba859d795fe2a50cfb1
|
|
BLAKE2b-256 checksum How to use checksums |
9c49e7144c74a3529176b8f497858a63a26298ec4a2bdfb247482db59f3f7a82
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-httpx/0.28.1
|
Release files / mcp_server_shalini12345-0.0.1-py3-none-any.whl
| Download URL | mcp_server_shalini12345-0.0.1-py3-none-any.whl |
|---|---|
| Size | 12.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
03192b5abed802a630d94b7af6378638bd95331a1314cec04821c38ae71be604
|
|
BLAKE2b-256 checksum How to use checksums |
e3a7f0d471fbde57bc3a258b9472102486584df5a1095d0272bdaaa6d1492d2d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-httpx/0.28.1
|
Security for mcp_server-shalini12345 0.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
