Context7
Up-to-date docs for AI agents
作者による説明(英語の原文)
Search MakerRadar's launched products: details, alternatives, comparisons, weeks.
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
MAKERRADAR_TOKEN「秘密」と表示された値は、あなたのアカウントの鍵です。絶対に人に教えたり、チャットに貼り付けたりしないでください。
必要なもの
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
ウェブ、デスクトップ、モバイルのClaudeで使えます:
https://api.makerradar.io/mcpClaude Desktop → Settings → Developer → Edit Config を開き、claude_desktop_config.json にこれを貼り付けます
{
"mcpServers": {
"makerradar": {
"command": "npx",
"args": [
"-y",
"makerradar",
"mcp",
"serve"
],
"env": {
"MAKERRADAR_TOKEN": "your-value"
}
}
}
}ターミナルでこれを実行します
claude mcp add --transport http makerradar https://api.makerradar.io/mcpclaude mcp add makerradar --env MAKERRADAR_TOKEN=your-value -- npx -y makerradar mcp serve動かす前に、空欄の値を入力してください。
プロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"makerradar": {
"url": "https://api.makerradar.io/mcp"
}
}
}プロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"makerradar": {
"command": "npx",
"args": [
"-y",
"makerradar",
"mcp",
"serve"
],
"env": {
"MAKERRADAR_TOKEN": "your-value"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
プロジェクトの .vscode/mcp.json に貼り付けます
{
"servers": {
"makerradar": {
"type": "http",
"url": "https://api.makerradar.io/mcp"
}
}
}プロジェクトの .vscode/mcp.json に貼り付けます
{
"servers": {
"makerradar": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"makerradar",
"mcp",
"serve"
],
"env": {
"MAKERRADAR_TOKEN": "your-value"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
ChatGPTがつなげるのは、インターネット上のサーバーだけです:
https://api.makerradar.io/mcpメニューの名前は、プランや時期によって少し違うことがあります。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
ツールの名前と説明は、サーバーが2026年11月6日に返したそのままの内容です。書いたのは作者で、私たちではありません。プレーンテキストとして表示しています。
search_productsSearch 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.
get_productGet the full public details of one product by its slug.
list_current_launchesList 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_productsList the most-upvoted products on MakerRadar of all time (the Top 100 board).
list_categoriesList MakerRadar's categories, each with how many listed products it has and its page, most products first.
get_alternativesList 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_productsCompare two products (by their slugs): each one's public details side by side, which has more community upvotes, and the comparison page.
get_launch_weekGet 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.
draft_listingDraft 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 r
connect_accountAsk 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_finishAfter 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 on every call.
get_my_accountWho 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_listingsThe 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_listingSubmit 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 i
get_my_listingOne 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 t
update_listingChange 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, audie
get_launch_optionsThe launch weeks open to a listing: Free (with spots left per week) and Premium. Use before choose_launch. Needs launches:write.
choose_launchChoose 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_checkStart 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 list
verify_ownershipCheck 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_imageAdd 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_optionsEverything 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 s
set_quick_answersReplace 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
remove_listing_photoRemove one photo from a listing's gallery, by its id from get_my_listing. It's gone at once. Needs listings:write.
set_listing_coverMake one of a listing's photos (by its id from get_my_listing) the cover its page leads with. Needs listings:write.
get_badge_snippetThe 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.
get_pricingWhat 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.
start_checkoutStart 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
list_my_ordersThe 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.
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月6日にチェック
レジストリ名はドメイン makerradar.io で確認済みです(レジストリがドメインの所有を確認しています)
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
430ミリ秒で応答(HTTP 200)
サインイン不要
29件のツールの説明を読み、AIへの隠れた指示は見つかりませんでした
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック3項目のうち3項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
入力が必要なもの:MAKERRADAR_TOKEN
どちらでも使えます。パソコンにインストールしても、クラウド版につないでもかまいません。
GitHubリポジトリの最終更新は–、最新バージョン(1.0.0)がレジストリに届いたのは一昨日です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URLでつながるので、リモートMCPサーバーに対応したアプリ(開発者モードのChatGPTなど)でも使えます。
同じカテゴリには:Context7, Codebase Memory, Exa
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
The official command-line client for MakerRadar, the launch platform and product directory. Search the directory, follow the weekly launch board, draft a listing for your product and manage your listings from the terminal, by hand or from a script or an AI agent.
npx makerradar search "invoicing"
makerradar login connects with a code you approve in the browser. The CLI never sees your password, can't vote, comment or review, and never pays.--json prints the API's own JSON, errors are JSON on stderr, and exit codes are stable.Docs: makerradar.io/cli · API reference: makerradar.io/developers · MCP server: makerradar.io/mcp
Needs Node.js 20 or newer.
npm install -g makerradar
makerradar --help
Or run it without installing: npx makerradar .
| Command | What it does |
|---|---|
makerradar search [query] | Search listed products, newest first. Filters: --category, --platform, --audience, --use-case, --country, --updated-since; pages: --limit (≤ 100), --cursor |
makerradar product | One product in full: website, pricing, upvotes, rating, tags, links |
makerradar alternatives | Listed alternatives to a product, ranked as on its alternatives page |
makerradar categories | Every category, with how many products it has |
makerradar launches [week] | This week's launch board, or another week's: 45, 2026-W45 or week-45-2026 |
makerradar pricing | What's on sale (Premium launch, featured weeks, ads…), with prices |
makerradar draft | Draft a listing for your product. You get a link to review and submit it: nothing is public until you do, and every listing is reviewed first |
| Command | What it does |
|---|---|
makerradar login | Connect the CLI to your account: open the link, sign in, approve. --scope (repeatable) limits what it may do: listings:read, listings:write, launches:write, billing:checkout |
makerradar whoami | The account the CLI acts for, and what it may do |
makerradar listings [id] | Your listings, or one of them in full |
makerradar logout | Forget the saved token on this machine (revoke it in Dashboard › AI agents) |
| Command | What it does |
|---|---|
makerradar mcp [client] | Connect an AI assistant to MakerRadar's MCP server: claude-code, claude-desktop, cursor, vscode, windsurf, stdio |
makerradar mcp serve [--account] | Run the MCP server over stdio for a client that can only start a local command (see below) |
makerradar api | Call any public API endpoint and print its JSON. --data takes JSON, @file or - (stdin); your token is sent when you're logged in |
makerradar search crm --platform ios --limit 5
makerradar product https://makerradar.io/p/acme-analytics makerradar launches 2026-W45 --json makerradar draft https://acme.example --tagline "Invoices in one click" makerradar api PATCH /me/listings/prd_123 --data '{"tagline":"Invoices in one click"}' makerradar mcp claude-code npx -y makerradar mcp serve # the MCP server over stdio
MakerRadar's MCP server lets an AI assistant search the directory and, signed in, manage your listings. It's remote — nothing to install — and this repository is its public home: the registry entry (io.makerradar/mcp), the setup for every client, and a stdio bridge.
| Server | URL | Sign-in |
|---|---|---|
| Public | https://api.makerradar.io/mcp | none — search, products, alternatives, comparisons, categories, launch weeks, draft_listing |
| Account | https://api.makerradar.io/mcp/account | OAuth (a "Connect" button), or an agent token — your listings, launches, ownership proof, images, checkout |
Both speak Streamable HTTP (protocol 2025-06-18 and later); the server card is at /.well-known/mcp/server-card.json and the docs at makerradar.io/mcp. Every tool carries a title and a read-only / write annotation. No tool votes, comments or reviews; a checkout hands the person a payment page — the agent never pays.
Set it up in one line. makerradar mcp prints the exact config for your client:
npx makerradar mcp claude-code # runs the two `claude mcp add` commands to copy
npx makerradar mcp cursor # ~/.cursor/mcp.json npx makerradar mcp vscode # .vscode/mcp.json npx makerradar mcp windsurf # ~/.codeium/windsurf/mcp_config.json npx makerradar mcp claude-desktop # Settings › Connectors › Add custom connector
A client that can only start a local command (or a catalog that lists installable servers) runs the bridge instead. It relays each JSON-RPC message to the remote server and prints every answer — nothing is interpreted locally:
{
"mcpServers": { "makerradar": { "command": "npx", "args": ["-y", "makerradar", "mcp", "serve"] } } }
Add "--account" to the arguments (and sign in with makerradar login, or set MAKERRADAR_TOKEN) to serve /mcp/account with your token so the assistant can manage your listings.
Tools on the public server: search_products, get_product, get_alternatives, compare_products, list_categories, list_current_launches, get_launch_week, top_products, draft_listing, get_pricing, connect_account / connect_account_finish. On the account server, also: get_my_account, list_my_listings, get_my_listing, submit_listing, update_listing, get_listing_options, set_quick_answers, add_listing_image, remove_listing_photo, set_listing_cover, get_launch_options, choose_launch, start_ownership_check, verify_ownership, get_badge_snippet, start_checkout, list_my_orders.
As a plugin. The repository is also an Agent Plugin: plugin.json, mcp.json (both servers) and skills/makerradar/SKILL.md (when and how an agent should use MakerRadar). A plugin-aware client, or the Cursor directory, installs it straight from this repo.
Found it in a directory? Listings on the MCP Registry, Glama, the Claude and ChatGPT directories and friends all point here. A listing that says something this README doesn't is stale: open an issue.
makerradar login uses the device flow: it prints a link and a short code, you open the link, sign in to MakerRadar, check the code and approve. The CLI then gets an agent token for your account (mr_…). It's never your password or session, and you can revoke it any time in Dashboard › AI agents.
The token is saved to ~/.config/makerradar/config.json (%APPDATA%\makerradar\config.json on Windows), readable only by you, and written atomically, so a crash never leaves half a file. Tokens are kept per API URL, so a staging login never stands in for production. In CI or for an agent, pass a token with MAKERRADAR_TOKEN instead.
Where a token goes:
MAKERRADAR_TOKEN is sent only to the API the environment names (MAKERRADAR_API_URL, or production). An --api-url pointing anywhere else doesn't get it; pass --token for that API.http, except to this machine (localhost, 127.0.0.1, [::1]). login needs https for the same reason.--json prints exactly what the API answered ({ "data": … }, plus nextCursor on lists).--json it's JSON: {"error":"not_found","status":404,"message":"…","hint":"…","docs":"…"}.0 done · 1 the API refused, or couldn't be reached · 2 a usage mistake (unknown command or option, missing argument). A usage mistake never calls the API.| Variable | Default | |
|---|---|---|
MAKERRADAR_API_URL | https://api.makerradar.io/v1 | The API to use (--api-url) |
MAKERRADAR_TOKEN | An agent token (--token) for the API above only; otherwise the one login saved | |
MAKERRADAR_CONFIG | ~/.config/makerradar/config.json | Where login saves the token |
NO_COLOR | Plain output (no-color.org) |
The CLI's API client is exported too:
import { createClient } from "makerradar";
const mr = createClient({ userAgent: "my-script/1.0" }); const { data } = await mr.call("listProducts", { query: { q: "invoicing", limit: 5 } });
npm test # unit tests: a fake API, never the network
npm run test:contract # every endpoint the CLI calls still exists in the live API description npm run sync:server-json # after a version bump: server.json names the package at its new version
server.json is the MCP Registry entry (mcp-publisher publish sends it; npm version keeps its package version in step), glama.json names the maintainers for Glama's index, and mcpName in package.json is how the registry checks the npm package is ours. Pushing a vX.Y.Z tag publishes both — npm, then the registry — through the release workflow.
No dependencies. The CLI calls only MakerRadar's public, versioned API (/v1). Every endpoint it uses is listed in src/operations.js, and the contract test checks each one against the published OpenAPI document every day.
Bugs and ideas: open an issue.
MIT