aimarket-mcp-packager
This MCP server packages an AIMarket capability into a self-hosted MCP product.
package_capability: builds the Docker image name, MCP manifest, subscription/pricing tiers, and connection string for a capability.generate_dockerfile: generates a ready-to-build Dockerfile for the packaged MCP server image.generate_claude_desktop_config: produces aclaude_desktop_config.jsonmcpServerssnippet to register the Docker-run MCP server with Claude Desktop or compatible MCP hosts.
Generates Dockerfile templates and Docker run configurations for containerized deployment of packaged MCP servers.
AIMarket Hub Plugins
๐ Synced from the AI-Factory monorepo (append-only history). Pull requests are welcome โ merged PRs are imported back and re-synced here. Issues ยท Pull requests
Ecosystem: AICOM overview & live demos ยท Community: Discord ยท Pollux ยท Telegram ยท Castor
15 protocol plugins extend hub invoke, settlement, compliance, and data planes without forking core.
Verifiable math lives in the separate oracles monorepo (Platon, Chronos, Murmuration, Lumen, โฆ) โ listed on the hub like any capability. aimarket-reputation scores sellers; Lumen oracle supplies PageRank/EigenTrust-style trust artifacts agents can invoke and audit.
Install
PyPI: docs/install.md. All 15 protocol plugins are published; the
Hub's plugins extra installs the five core plugins.
Package | PyPI status |
| Published; Python 3.11+ |
| Published; included in |
| Published; install individually โ see the install guide |
Docker: all 15 plugins ship in the production hub image โ ./scripts/deploy_hub.sh from the factory monorepo.
Source: pip install -e plugins/aimarket-tee after cloning this repo.
Related MCP server: my-mcp-server2
TEE Escrow
Smart-contract escrow in a Trusted Execution Environment โ buyer funds stay held until attested invoke succeeds; seller is paid only on proof; failures refund on-channel.
What |
|
Why | Micropay scale with both-side protection โ no human escrow desk |
Deep dive |
MCP server โ aimarket-mcp-packager
One of the 15 plugins is a full Model Context Protocol server โ stdio transport, built on the official MCP Python SDK. aimarket-mcp-packager turns any AIMarket capability into a self-hosted MCP product (Docker image, MCP manifest, and a ready claude_desktop_config.json) that runs in Claude Desktop, Cursor, Glama, or any stdio MCP client.
Run |
|
Tools |
|
Registry | Listed on Glama (score badge above) โ see |
MCP server โ aimarket-oracle-gateway (standalone repo)
A second MCP server ships as its own satellite repo alexar76/aimarket-oracle-gateway for Glama indexing. aimarket-oracle-gateway exposes Platon randomness, Chronos VDF, and LUMEN reputation as agent-callable tools โ pay-per-call over AIMarket, every result independently verifiable.
Run |
|
Tools |
|
Registry |
|
Plugin index
Plugin | Role |
Pre-invoke policy, signed reject | |
TEE attestation, escrow hooks | |
W3C VC invoke receipts | |
Scores + stake bonds | |
USDT channel lifecycle | |
Price discovery | |
Multi-capability plans | |
Data-capability packaging | |
Dataset listings | |
MCP server (stdio) โ package capabilities as Docker + MCP manifest + Claude Desktop config | |
Capability NFTs | |
Seller personas | |
Promotions | |
Streaming invoke | |
ZK cohort proofs |
Hub loads plugins from aimarket-hub/plugins/ at runtime. Monorepo copies under plugins/ are the source-of-truth for docs and tests.
Demo
Related repos
Repo | Role |
Loads plugins at invoke time | |
Verifiable math capabilities (separate repo) | |
AI-Factory monorepo | |
Twin community agents โ MNEMOSYNE Q&A |
Community
The DIOSCURI twins answer questions from synced GitHub docs.
Channel | Twin | Best for |
Pollux | Help, ideas, show-and-tell | |
Castor | Releases, digests, quick news |
Ecosystem map: Alien Monitor ยท AICOM
Available Tools
3 toolsgenerate_claude_desktop_configA
Generate a claude_desktop_config.json snippet for the packaged MCP server.
Takes the same capability inputs as package_capability and returns the
mcpServers entry that registers the docker-run MCP server with Claude
Desktop (or any MCP host that reads this config format).
Returns:
A JSON object (string) containing an mcpServers block โ merge it into
the user's existing claude_desktop_config.json and restart the host.
Example: generate_claude_desktop_config( capability_id="translate.multi@v2", product_id="prod-translate", name="Lyra Translator", )
Inputs: name (required), product_id (required), capability_id (required), registry, +2 more. Returns: result
generate_dockerfileA
Generate a ready-to-build Dockerfile for the packaged MCP server.
Takes the same capability inputs as package_capability and returns the
Dockerfile text that builds the self-hosted MCP server image for it.
Returns:
The Dockerfile contents as plain text โ write it to Dockerfile and
run docker build to produce the image named in package_capability's
docker_image field.
Example: generate_dockerfile( capability_id="translate.multi@v2", product_id="prod-translate", name="Lyra Translator", )
Inputs: name (required), product_id (required), capability_id (required), registry, +2 more. Returns: result
package_capabilityA
Build a complete self-hosted MCP server package for an AIMarket capability.
Use this first. It assembles everything needed to ship the capability as a standalone MCP server: the Docker image name, the MCP manifest (server + tool definition), subscription/pricing tiers, and a connection string.
Returns:
A JSON object (string) with keys:
- docker_image: the image name to build/run.
- mcp_manifest: the full MCP manifest (server metadata + tools).
- subscription_tiers: pricing tiers derived for the capability.
- connection_string: how a client connects to the running server.
Example: package_capability( capability_id="translate.multi@v2", product_id="prod-translate", name="Lyra Translator", description="Translate text into multiple languages.", input_schema={"type": "object", "properties": {"text": {"type": "string"}}, "required": ["text"]}, )
Inputs: name (required), product_id (required), capability_id (required), registry, +2 more. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogโฆ
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: package_capability builds the package, generate_dockerfile produces the Dockerfile, and generate_claude_desktop_config outputs the config snippet. There is no overlap in functionality.
All tool names follow a consistent verb_noun pattern (package_capability, generate_dockerfile, generate_claude_desktop_config), making them predictable and easy to understand.
With 3 tools, the server is slightly small but well-scoped for its packaging purpose. Each tool serves a necessary step, and adding more would risk bloat.
The tool set covers the core packaging workflow: build the package, generate Dockerfile, and generate config. Minor gaps exist, such as lacking a validation or listing tool, but the main path is complete.
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yoโฆ
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
MCP server for Clipkit โ gives AI agents a video toolbox via the Clipkit schema.
Related MCP Servers
- AlicenseBqualityDmaintenanceAn educational implementation of a Model Context Protocol server that demonstrates how to build a functional MCP server for integrating with various LLM clients like Claude Desktop.1162MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server built with FastMCP that features dynamic tool loading and modular management via a dedicated tool directory. It supports both stdio and HTTP transport modes, enabling efficient development and deployment of custom MCP tools.-
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server built with the mcp-framework for developing and managing custom tools. It provides a structured foundation for building and integrating modular components like data processors and API clients into Claude Desktop.-
- AlicenseAqualityBmaintenanceLocal MCP server that wraps the headless Claude Code CLI as MCP tools, providing stateless access to Claude's coding capabilities through prompt-based interactions. It enables users to execute Claude Code commands with various prompt formats and structured outputs directly from MCP clients.3MIT