hexagram-mcp-server
A minimal, production-friendly sample MCP server project with PyPI publishing support.
Features
- Minimal MCP server implementation
- Tool + Resource examples
- Modern Python packaging with
pyproject.toml - Console entry point (
hexagram-mcp-server) - Build and publish workflow for PyPI
Quick Start
-
Create and activate a virtual environment.
-
Install dependencies:
pip install -e .[dev]
-
Run the server:
hexagram-mcp-server
Example MCP API
- Tool:
get_hexagram() -> str
Build Package
python -m build
After building, artifacts are generated in the dist/ directory.
Publish to PyPI
-
Create a PyPI API token from your PyPI account.
-
Configure your token (recommended):
set PYPI_TOKEN=pypi-xxxxxxxxxxxxxxxx
-
Upload:
python -m twine upload -u __token__ -p %PYPI_TOKEN% dist/*
For TestPyPI, use:
python -m twine upload --repository-url https://test.pypi.org/legacy/ -u __token__ -p %PYPI_TOKEN% dist/*
Publish with GitHub Actions
This template includes .github/workflows/publish.yml and supports PyPI Trusted Publishing.
- Create your package on PyPI first.
- In PyPI project settings, configure a Trusted Publisher for your GitHub repository.
- Create a GitHub Release (
published), then workflow will build and publish automatically.
If you prefer token-based upload in CI, you can replace the publish step with twine upload and store token in GitHub Secrets.
Notes Before Publishing
-
Update
name,authors, and project URLs inpyproject.toml. -
Ensure version is bumped before each release.
-
Verify package contents:
python -m twine check dist/*
License
MIT
Metadata
Release files for hexagram-mcp-server 0.1.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 | |
|---|---|---|---|---|
| hexagram_mcp_server-0.1.1.tar.gz | 4.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hexagram_mcp_server-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.7 kB
Release files / hexagram_mcp_server-0.1.1.tar.gz
| Download URL | hexagram_mcp_server-0.1.1.tar.gz |
|---|---|
| Size | 4.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fec2c155c8dc2bef1b5c5ac5f433f83e2aa6ac9c77be988a74a927593c3db2bf
|
|
BLAKE2b-256 checksum How to use checksums |
793b96127948bd1884b03005e8fa8e7e13eee37d0c77e35f94e939d46e3a9f8a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.14 {"installer":{"name":"uv","version":"0.11.14","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / hexagram_mcp_server-0.1.1-py3-none-any.whl
| Download URL | hexagram_mcp_server-0.1.1-py3-none-any.whl |
|---|---|
| Size | 4.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1359af6644dec78a005873a537178ce81bad9f1b6e2f8baa8d5b11edc989e73a
|
|
BLAKE2b-256 checksum How to use checksums |
4356aead0c89da4c90ff5788b7a4de518481ba0e1a67ee2e27b1f639a197ca9e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.14 {"installer":{"name":"uv","version":"0.11.14","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for hexagram-mcp-server 0.1.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.