MCP Forge
Package and publish your MCP server to PyPI and the Official Registry in seconds.
MCP Forge is a CLI tool that takes the pain out of shipping a Python MCP server. It checks your package name for conflicts, scaffolds the required pyproject.toml and server.json, and gives you the exact commands to publish.
Why use it?
Publishing an MCP server is a multi-step process:
- Pick a PyPI package name that isn't taken.
- Write a pyproject.toml with the right entry points.
- Create a server.json that matches the Official Registry schema.
- Run mcp-publisher login and mcp-publisher publish.
MCP Forge automates the boring parts and verifies the name before you waste time building.
Installation
pip install mcp-forge-publisher
Usage
Check if a name is available on PyPI: mcp-forge check my-cool-server
Scaffold the config files: mcp-forge init my-cool-server my_cool_server your-github-username --output ./my-server
This generates:
- pyproject.toml (with the correct entry point)
- server.json (with your GitHub namespace pre-filled)
Publish
Follow the checklist printed by the CLI:
- python -m build
- twine check dist/*
- twine upload dist/*
- mcp-publisher publish server.json
License
MIT
Metadata
Release files for mcp-forge-publisher 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 | Actions |
|---|---|---|---|---|
| mcp_forge_publisher-0.1.1.tar.gz | 3.2 kB | Without provenance | Details for mcp_forge_publisher-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mcp_forge_publisher-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for mcp_forge_publisher-0.1.1-py3-none-any.whl |
Total release size: 7.6 kB
Release files / mcp_forge_publisher-0.1.1.tar.gz
| Download URL | mcp_forge_publisher-0.1.1.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1adbf0aa2c833f663469aa3d0aa42bc7d8c757791285ac6e6845c622ac51aff6
|
|
BLAKE2b-256 checksum How to use checksums |
db755ec7275ae252fdc61dd39388390cedc068808607d78eb7e556e3427eb1d0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.15.2
|
Release files / mcp_forge_publisher-0.1.1-py3-none-any.whl
| Download URL | mcp_forge_publisher-0.1.1-py3-none-any.whl |
|---|---|
| Size | 4.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bc9ea91538337c1d279be0343b2884642d2c9411bc55a748c37ef3040860e53b
|
|
BLAKE2b-256 checksum How to use checksums |
3122329608c40ef0394e7de2e34ed6197b1a65d205beebf676dbc2dfab4296ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.15.2
|
Security for mcp-forge-publisher 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.