Two narrow tools answer the useful questions.
The server deliberately exposes a small surface. An agent can retrieve the canonical product summary or list public resources by category without receiving private application state.
get_marketmaster_product
Returns MarketMaster's description, audience, six-step workflow, output formats, current monthly plan prices, and canonical links for structured data, pricing, and the Studio.
list_marketmaster_resources
Returns public product, planning, quality, and discovery resources. Clients can request one category or the complete directory.
Use the Streamable HTTP endpoint.
The protocol endpoint accepts MCP JSON-RPC requests for initialization, tool discovery, tool calls, notifications, and ping. It implements protocol version 2025-06-18.
- 1Endpoint
https://marketmaster.dev/api/mcp - 2Method
POSTwithContent-Type: application/json. - 3Authentication
None for the public read-only tools.
Choose the format that fits the client.
HTML remains the canonical human and search-engine page. Markdown gives language-model crawlers a compact text representation. MCP provides structured tool calls, and JSON exposes exact product and pricing fields.
marketmaster.dev/mcp
Canonical overview with visible explanations, boundaries, FAQs, and links.
marketmaster.dev/mcp.md
Compact documentation for text-first crawlers and retrieval systems.
marketmaster.dev/api/mcp
Structured, read-only JSON-RPC tool traffic for MCP-compatible clients. Send requests with POST.
marketmaster.dev/api/ai
Canonical product, plan, cap, annual-price, workflow, and documentation data.
marketmaster.dev/llms.txt
Prioritized map of product documentation, commercial pages, and free resources.
MCP server card
Transport, version, capability, authentication, and documentation metadata.
Discovery is public; actions stay in the Studio.
The MCP server can explain what MarketMaster is and point to public resources. It cannot create campaigns, read customer work, connect social accounts, publish content, start subscriptions, or move money. Those actions require an authenticated human session and the product's normal review flow.
What an agent can safely retrieve
- Current product description, intended audience, workflow, and output types.
- Public monthly prices and links to exact plan caps.
- Campaign planning templates, quality checklists, and testing tools.
- Machine-readable API, agent-skill, and MCP discovery documents.
Follow the MCP facts to the human-readable source.
The public tools point agents to the same pages people use to understand the product, verify plan limits, and evaluate the campaign workflow.
Understand the workflow.
See how MarketMaster researches a site, creates a coordinated package, reviews it, and keeps publishing under human control.
Verify public pricing.
Use the pricing page for current plan limits, billing cadence, promotion terms, and cancellation details.
Read the evidence-first system.
Use the content guide and distribution playbook when an agent needs practical planning context instead of product data alone.
MarketMaster MCP questions.
What is the MarketMaster MCP server?
It is a public, read-only Model Context Protocol endpoint that returns canonical MarketMaster product facts and links to campaign planning, quality, pricing, and discovery resources.
Does the MarketMaster MCP server require authentication?
No authentication is required for the two public read-only discovery tools. Campaign creation, publishing, billing, and account data are not exposed through this server.