Skip to main content
Glama
alexar76

aimarket-mcp-packager

by alexar76
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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"]}, )

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", )

generate_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", )

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 3 tools

Disambiguation5/5

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.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (package_capability, generate_dockerfile, generate_claude_desktop_config), making them predictable and easy to understand.

Tool Count4/5

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.

Completeness4/5

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

ActivityMaintained
ResponsivenessUnresponsive

Resources