Skip to content
MakerRadar

Developers

MakerRadar MCP server

A Model Context Protocol server for MakerRadar's directory: AI assistants search launched products, read a listing, find alternatives and compare tools as function calls. Reading needs no key; acting for a person needs their approval.

On this page

Connect

The server is at https://api.makerradar.io/mcp — Streamable HTTP, JSON-RPC 2.0, stateless, no key. In Claude Code:

claude mcp add --transport http makerradar https://api.makerradar.io/mcp

In Claude.ai or ChatGPT (custom connectors), Cursor, VS Code or any client with a Connect button, add https://api.makerradar.io/mcp/account instead: the client signs in with OAuth and the person approves it on MakerRadar, so the account tools work too. Any other MCP client that supports remote HTTP servers takes https://api.makerradar.io/mcp as is.

Tools

Open to every agent, no key:

  • search_products (Search products) — Search MakerRadar's directory of launched products by keyword (matches name and tagline), ranked by all-time upvotes. Narrow it by platform, audience, use case or the country it's based in (combined, a product matches them all); an unknown value is an error naming the valid ones. Omit everything to list the most-upvoted products.
  • get_product (Get a product) — Get the full public details of one product by its slug.
  • list_current_launches (This week's launches) — List the products on MakerRadar's live launch board (this ISO week's, or the last week until the new one opens), ranked by upvotes.
  • top_products (Top products of all time) — List the most-upvoted products on MakerRadar of all time (the Top 100 board).
  • list_categories (List categories) — List MakerRadar's categories, each with how many listed products it has and its page, most products first.
  • get_alternatives (Alternatives to a product) — List the alternatives to one product (by its slug) in the order its alternatives page ranks them: editor's picks first, then makers' own declarations, then by relevance and upvotes.
  • compare_products (Compare two products) — Compare two products (by their slugs): each one's public details side by side, which has more community upvotes, and the comparison page.
  • get_launch_week (A launch week's results) — Get one launch week's full results (by its week, e.g. week-41-2026), ranked by upvotes — any week since MakerRadar began, not only the live one.
  • get_pricing (Prices) — What a listing can buy on MakerRadar — Premium launch, featured and boosted weeks, ads, newsletter sponsorship, done-for-you submissions — each with its id, today's price and what it gets. Use before start_checkout. No sign-in needed.

Also open, and the only ones that store anything — a draft a person must sign in and submit before anything is published:

  • draft_listing (Draft a listing for a person to submit) — Draft a listing on MakerRadar for the person you're helping: give their product's website and, optionally, a name, tagline and description. Returns reviewUrl, a link the person opens to sign in, check the listing and submit it; nothing is published until they do (and MakerRadar reviews it). If the site is already listed, returns its page instead. No sign-in needed.
  • connect_account (Connect to a person's account) — Ask the person you're helping to let you act for their MakerRadar account. Returns a short code and a link: show them both, they sign in and approve you on MakerRadar. Then call connect_account_finish with deviceCode until it returns your token. No sign-in needed to start.
  • connect_account_finish (Finish connecting) — After connect_account: trade deviceCode for your agent token once the person has approved. Returns status pending (ask again after `interval` seconds), denied, expired, or approved with the token — shown once; send it as Authorization: Bearer <token> on every call.

For an agent acting for a person (they approve it first — see below):

  • get_my_account (Your account) — Who you're acting for on MakerRadar: the account an agent token belongs to, whether it's ready to list products, and what the token may do. Needs an agent token (Authorization: Bearer mr_…).
  • list_my_listings (Your listings) — The listings of the account you act for on MakerRadar, newest first: each one's status (draft, in review, live…), its page once public, and where its maker manages it. Needs an agent token with listings:read.
  • submit_listing (Submit a listing) — Submit a product as a draft listing on MakerRadar, owned by the person you act for: its website and, optionally, a name, tagline and description (we fill in the rest from the site). Already listed sites come back as listed instead. Then get_my_listing, and choose_launch to send it for review. Needs listings:write.
  • get_my_listing (One of your listings) — One listing of the person you act for, by id: everything you can edit (copy, category, pricing, price from, where it's based, best for, demo video, technologies, platforms, audiences, tags, links elsewhere, quick answers, logo and photos with their ids), its status, what's left to make it complete, and whether it can be sent for review. Needs listings:read.
  • update_listing (Edit a listing) — Change any of a listing's details: name, tagline, description, category, pricingModel, priceFrom, basedIn, bestFor, demoVideo, technologies, platforms, audiences, tags, links. Send only what changes; null or an empty list clears a field. Categories, technologies, platforms, audiences and tags are slugs from get_listing_options. A demo video must be a YouTube, Vimeo, Loom or Arcade link to a real, public video. Links are the listing's pages elsewhere (X, GitHub, LinkedIn, App Store, Google Play, Product Hunt, YouTube channel, Discord, Instagram), one per kind. A draft changes at once; on a live listing a new name, category, video or link, or a rewrite, waits for review. Needs listings:write.
  • get_launch_options (Launch weeks with room) — The launch weeks open to a listing: Free (with spots left per week) and Premium. Use before choose_launch. Needs launches:write.
  • choose_launch (Choose a launch and send for review) — Choose Free or Premium (and optionally a week, as get_launch_options names it) and send the listing for review. MakerRadar reviews every listing before it goes live. Needs launches:write.
  • start_ownership_check (Start proving the site is theirs) — Start proving the person controls a listing's website: method dns_txt, html_file or meta_tag returns a token and exactly where to put it. If you can deploy the site or edit its DNS, place it, then call verify_ownership. A proven owner can't have the listing taken over. Needs listings:write.
  • verify_ownership (Verify the site is theirs) — Check the token from start_ownership_check is in place; if it is, the person becomes the listing's verified owner. DNS can take a few minutes to show. Needs listings:write.
  • add_listing_image (Add a logo or photo) — Add a listing's logo (kind logo, replaces the old one) or a photo (kind photo) from a public https image URL. We fetch and check it like an upload; on a live listing it waits for review. Needs listings:write.
  • get_listing_options (What a listing's fields accept) — Everything update_listing accepts: the categories, technologies, platforms, audiences and tags to pick from (by slug), the pricing models, currencies and price periods, the demo video hosts, the link kinds with an example of each, and each field's limits. Call it before editing so you never guess a value. Needs listings:read.
  • set_quick_answers (Set a listing's quick answers) — Replace a listing's quick answers (the questions buyers ask, answered by the maker): up to 6, each a question of 8–140 characters and an answer of 2–600. An empty list removes them. On a live listing, answers that add a link or are mostly rewritten wait for review. Needs listings:write.
  • remove_listing_photo (Remove a photo) — Remove one photo from a listing's gallery, by its id from get_my_listing. It's gone at once. Needs listings:write.
  • set_listing_cover (Choose the cover photo) — Make one of a listing's photos (by its id from get_my_listing) the cover its page leads with. Needs listings:write.
  • get_badge_snippet (The badge for their site) — The HTML badge for the listing's own website: put it on the homepage and, while it's there, the listing earns what MakerRadar's badge earns (the answer says what). Needs listings:read.
  • start_checkout (Start a checkout for them to pay) — Start a checkout for the person you act for: an item from get_pricing for one of their listings (a placement needs the listing approved first). Returns checkoutUrl, the payment page: give it to the person to pay — you never pay, and nothing is charged until they do. We also email them the link. Holds a week's spot while they pay. Needs billing:checkout.
  • list_my_orders (Your orders) — The orders of the person you act for, newest first: what each bought, for which listing and week, and whether it's paid. Use after start_checkout to see when they've paid. Needs billing:checkout.

Try it

One call, straight from a terminal:

curl -s https://api.makerradar.io/mcp -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search_products","arguments":{"query":"analytics","limit":5}}}'

Tool results put what makers wrote under makerProvided, labelled “maker-provided, unverified”, with links and other sites' addresses taken out — so an agent can tell a listing's claims from our facts.

Acting for a person

The account tools list and launch a person's own products and start checkouts for them to pay. They need an agent token (mr_…), scoped and revocable, which the person approves — never their session, and no token can vote, comment or review:

  • A client with a Connect button signs in with OAuth at https://api.makerradar.io/mcp/account.
  • Any other agent calls connect_account, shows the person a short code to approve at https://makerradar.io/connect, then collects its token with connect_account_finish.
  • Or the person makes a key in Dashboard › AI agents.

The steps, for agents: /auth.md.

How agents find it