aimarket-mcp-packager — MCP server
Quality score: glama.ai/mcp/servers/alexar76/aimarket-plugins/score ·
This repository ships a Model Context Protocol (MCP) server that packages AIMarket capabilities into self-hosted MCP server products (Docker image metadata, MCP manifest, Claude Desktop config).
Transport: stdio (aimarket_mcp_packager/stdio_server.py). Built with the official MCP Python SDK (mcp package, FastMCP).
Compatible hosts: Claude Desktop, Cursor, Glama, and any MCP client that supports stdio servers.
MCP server in this repo
| Item | Location |
|---|---|
| MCP entrypoint | aimarket_mcp_packager/stdio_server.py |
| MCP SDK dependency | Installed by default — mcp>=1.6,<2 |
| Glama / Docker run | Dockerfile, glama.json, docs/GLAMA.md |
| Tool implementation | aimarket_mcp_packager/packager_core.py |
Run locally:
pip install -r requirements-mcp.txt
pip install -e .
python -m aimarket_mcp_packager.stdio_server
Or with Docker (stdio MCP server):
docker build -t aimarket-mcp-packager .
docker run --rm -i aimarket-mcp-packager
MCP tools
The server exposes 3 tools (no MCP resources or prompts):
| Tool | Description |
|---|---|
package_capability |
Build an MCP server package: Docker image name, mcp_manifest, subscription tiers, connection string |
generate_dockerfile |
Generate a self-contained Dockerfile with a working stdio capability relay |
generate_claude_desktop_config |
Generate a claude_desktop_config.json snippet (mcpServers) for docker-run MCP |
Example tool call (conceptual):
{
"name": "package_capability",
"arguments": {
"capability_id": "translate.multi@v2",
"product_id": "prod-001",
"name": "Lyra",
"description": "Multilingual translator",
"input_schema": { "type": "object", "properties": { "text": { "type": "string" } }, "required": ["text"] }
}
}
input_schematakes a JSON Schema object (a JSON string is also tolerated for backward compatibility). Every tool parameter is documented in the server's tool schema for MCP clients.
The generated Dockerfile includes the server source and installs its runtime; build it
with the image tag returned by package_capability. Both client-config generators use
attached docker run --rm -i so MCP messages travel over stdio. Set AIMARKET_HUB_URL
and, for capabilities on another provider, AIMARKET_SOURCE_HUB. An optional
AIMARKET_API_KEY pays calls through the Hub; these environment variables are forwarded
at runtime and are never embedded in the image. The example subscription tiers are
metadata only: this relay does not implement subscription billing or license checks.
MCP resources
This server does not register MCP resources or prompts — only the tools above. Output is JSON text returned from each tool call.
Client configuration
Claude Desktop
{
"mcpServers": {
"aimarket-mcp-packager": {
"command": "python",
"args": ["-m", "aimarket_mcp_packager.stdio_server"]
}
}
}
Compat path (what Glama's admin form historically used — keep the shim file):
{
"mcpServers": {
"aimarket-mcp-packager": {
"command": "python",
"args": ["plugins/aimarket-mcp-packager/mcp_stdio_server.py"]
}
}
}
Docker variant (see generate_claude_desktop_config tool output):
{
"mcpServers": {
"aimarket-mcp-packager": {
"command": "docker",
"args": ["run", "--rm", "-i", "aimarket-mcp-packager:latest"]
}
}
}
Cursor
Add the same stdio server under Settings → MCP (command + args pointing at aimarket_mcp_packager/stdio_server.py or the Docker image above).
Python library (optional)
The same packaging logic is available as a library and as an AIMarket Hub plugin (PyPI package coming soon — for now pip install -e . from this directory, or use the AIMarket Hub Docker image). Hub HTTP routes are optional; the MCP server runs standalone via aimarket_mcp_packager/stdio_server.py.
from aimarket_mcp_packager.mcp_packager import MCPPackager
packager = MCPPackager()
pkg = packager.package(
capability_id="translate.multi@v2",
product_id="prod-001",
name="Lyra",
description="Multilingual translator",
input_schema={"type": "object", "properties": {"text": {"type": "string"}}},
price_per_call_usd=0.40,
)
print(pkg.docker_image)
print(pkg.mcp_manifest)
print(packager.generate_claude_desktop_config(pkg))
When to use
- Distribute AI capabilities as self-hosted MCP servers (Docker + manifest)
- Generate Claude Desktop / Cursor MCP client configs
- Enterprise on-prem deployment with subscription tiers
Subscription tiers (packaged products)
| Tier | Calls/month | Price |
|---|---|---|
| Starter | 100 | $9.99 |
| Pro | 1,000 | $49.99 |
| Enterprise | 10,000 | $299.99 |
Documentation
| Document | Description |
|---|---|
| User guide | Install, Hub plugin, verify loaded |
| User cases | Personas and cross-plugin workflows |
| SDK integration | Code examples and hook behavior |
License
MIT · Maintained by AI-Factory
Metadata
Release files for aimarket-mcp-packager 2.1.3
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 |
|---|---|---|---|---|
| aimarket_mcp_packager-2.1.3.tar.gz | 14.4 kB | Without provenance | Details for aimarket_mcp_packager-2.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aimarket_mcp_packager-2.1.3-py3-none-any.whl | Python 3 | none | any | Details for aimarket_mcp_packager-2.1.3-py3-none-any.whl |
Total release size: 26.5 kB
Release files / aimarket_mcp_packager-2.1.3.tar.gz
| Download URL | aimarket_mcp_packager-2.1.3.tar.gz |
|---|---|
| Size | 14.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2d46323f1490d2422c01fdf27fde93aaef24889931f1da421f8a29997a1e6eb8
|
|
BLAKE2b-256 checksum How to use checksums |
bd184cc8c1e4bcb12dc6a7175454e3c1149228342b57a94c7e5109321c5c28a3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Release files / aimarket_mcp_packager-2.1.3-py3-none-any.whl
| Download URL | aimarket_mcp_packager-2.1.3-py3-none-any.whl |
|---|---|
| Size | 12.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
50ec95b7c194b1b2cb4012d236ff38c8d8d4f2008725235e0dd927574e788ea8
|
|
BLAKE2b-256 checksum How to use checksums |
2f874e36504a38fab8cf9dba6637969fdb4324431ab2120f9166742d24f89ade
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Security for aimarket-mcp-packager 2.1.3
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.