What Tamer Prompt Marketplace MCP server does
Tamer Prompt Marketplace MCP server connects MCP-compatible agents to Tamer’s agent marketplace. It provides a catalog of prompts that agents can inspect before making a purchase. The catalog includes each prompt’s title, price, and purchase URL. Tamer also offers a separate web shop at https://tamer-ai.ir for human users, while the agent-facing marketplace is available at https://agents.tamer-ai.ir.
The repository describes prompts as products for both agents and humans. The MCP interface is intended for discovery; the prompt itself is obtained through a paid endpoint after the agent selects a catalog item.
How it works
The server is available through a Streamable HTTP MCP endpoint at https://agents.tamer-ai.ir/mcp. An MCP client connects to that URL and can call list_tamer_prompts. The tool returns enough information for an agent to compare available prompts and identify the relevant purchase URL.
Each prompt is exposed through an endpoint under /agent/prompt/{key}. The initial request returns HTTP 402 Payment Required together with x402 payment details. The client then retries with a payment signature. If the payment is accepted, the endpoint returns the prompt content. Payments use USDC on Base and are final, so the product should be checked before payment.
Setup and configuration
Connect the MCP endpoint with a client configuration such as:
claude mcp add --transport http tamer https://agents.tamer-ai.ir/mcp
The equivalent server entry is:
{
"mcpServers": {
"tamer": {
"type": "http",
"url": "https://agents.tamer-ai.ir/mcp"
}
}
}
No environment variables or local service configuration are documented. The repository also publishes a free catalog at https://agents.tamer-ai.ir/agent/catalog and an OpenAPI document at https://agents.tamer-ai.ir/openapi.json.
Tools and capabilities
Tamer Prompt Marketplace MCP server documents one MCP tool:
list_tamer_prompts: Lists the prompt catalog with titles, prices, and purchase URLs.
The tool supports selection and discovery. Purchasing is handled through the prompt’s paid HTTP endpoint and the x402 payment flow rather than through a second documented MCP tool.
Limitations and notes
The catalog tool does not, according to the provided documentation, return prompt contents directly. Content retrieval requires a purchase request to the corresponding /agent/prompt/{key} endpoint. x402 payment support and USDC on Base are therefore relevant prerequisites for paid retrieval.
Payments are final. Agents should inspect the catalog information and confirm the intended product before submitting payment. The provided material does not document refunds, subscriptions, prompt editing, seller management, or additional MCP tools.