プロトタイプ · プレビュー版:公式レジストリのすべてのサーバーを掲載し、30分ごとに同期しています。Google でログインするとレビューを書けます。
PopNx MCPAIを使う人のためのMCPサーバー · やさしい言葉で解説

Bitroad

作者:bitroadaiバージョン 1.0.0i★ 0iクラウドで動く
レジストリ名ai.bitroad/bitroad

インストール方法

概要

作者による説明(英語の原文)

Marketplace for AI agents: buy goods and services under spending caps, with returns and disputes.

できること

このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。

  • 接続方法: クラウドで動く
  • トランスポート: Streamable HTTP
  • カテゴリ: ネットショップ・決済

インストール

使っているAIアプリを選んで、設定をコピーしてください。

チェック 5/5 合格 · 質問内容は提供元のサーバー(app.bitroad.ai)を通ります

まず:どの AI を使っていますか?

使っているアプリを選ぶと、下に手順が表示されます。

Claude につなげます · 約 2 分

キー不要、インストール不要 · claude.ai かデスクトップアプリで一度設定すれば、チャットで使えます · 無料アカウントは 1 つまで

  1. Claude の Connectors ページを開く

    CustomizeConnectors

    CustomizeConnectors1+ Add2https://…3Add4
  2. 「+ Add」→「Add custom connector」を押し、この 2 つを入力

    ここからコピーして Claude の同じ名前の欄に貼り付け、Continue を押します

    Name · 名前Bitroad
    Remote MCP server URL · アドレスhttps://app.bitroad.ai/api/v1/mcp

    Authentication は Claude が検出したままにして Add を押します

  3. チャットで有効にする

    +ConnectorsBitroad

  4. 試してみる

    Bitroad を使って、私に何ができるか教えて、1 つやってみせて

    ✓ Claude が Bitroad を使っていると言うか、回答に Bitroad のツール名が出れば接続成功です

メニュー名は 2026年11月11日 に Anthropic のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります

ChatGPT は法人向けプランのみ接続できます

Web 版 ChatGPT Business・Enterprise・Edu で、ワークスペースの管理者かオーナーが追加します · Free・Plus・Pro の場合:あなたの ChatGPT プランではまだ MCP を自分でつなげません

  1. Web 版 ChatGPT で MCP の追加ページを開く

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. 名前とアドレスを入力

    名前を入れ、Connection にアドレスを貼り付け、注意事項にチェックして Create as a plugin を押します

    Name · 名前Bitroad
    Connection · アドレスhttps://app.bitroad.ai/api/v1/mcp
  3. チャットで Bitroad を選ぶ

    新しいチャットを開き、入力前にプラグインの一覧から Bitroad を選びます

  4. 試してみる

    Bitroad を使って、私に何ができるか教えて、1 つやってみせて

    ✓ ChatGPT が Bitroad を使っていると言うか、回答に Bitroad のツール名が出れば接続成功です

メニュー名は 2026年11月11日 に OpenAI のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります

Claude Code につなげます · 約 2 分

キー不要、インストール不要

  1. ターミナルを開く

    Mac:Command+スペースで Terminal と入力 · Windows:PowerShell を開く

  2. このコマンドを貼り付けて Enter

    claude mcp add --transport http bitroad https://app.bitroad.ai/api/v1/mcp
  3. Claude Code で /mcp と入力

    Bitroad が一覧にあり、接続済みと表示されれば OK です

  4. 試してみる

    Bitroad を使って、私に何ができるか教えて、1 つやってみせて

    ✓ Claude Code が Bitroad を使っていると言うか、回答に Bitroad のツール名が出れば接続成功です

メニュー名は 2026年11月11日 に Anthropic のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります

Cursor につなげます · 約 2 分

キー不要、インストール不要

  1. このボタンで Cursor を開く

    Cursor で開く

    Cursor がインストールの確認をするので Install を押します

  2. Cursor の AI チャットを Agent モードで開く

  3. 試してみる

    Bitroad を使って、私に何ができるか教えて、1 つやってみせて

    ✓ Cursor が Bitroad を使っていると言うか、回答に Bitroad のツール名が出れば接続成功です

メニュー名は 2026年11月11日 に Cursor のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります

VS Code につなげます · 約 2 分

キー不要、インストール不要

  1. このボタンで VS Code を開く

    VS Code で開く

    VS Code がインストールの確認をするので Install を押します

  2. VS Code の AI チャットを Agent モードで開く

  3. 試してみる

    Bitroad を使って、私に何ができるか教えて、1 つやってみせて

    ✓ VS Code が Bitroad を使っていると言うか、回答に Bitroad のツール名が出れば接続成功です

メニュー名は 2026年11月11日 に VS Code のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります

Windsurf、Zed、Gemini CLI など MCP を使える他のアプリは追加方法がそれぞれ違います。アプリ一覧で確認してください

MCP を使えるアプリをすべて見る →

Web 経由でつなぐアプリ用のアドレス

アドレスhttps://app.bitroad.ai/api/v1/mcp

JSON 設定は下の「開発者向け」にあります

つまずいたら?Bitroad を使っている人に聞いてみましょう💬 ディスカッション →
開発者向け:ターミナルのコマンドと JSON 設定

Web 経由

Claude Code

claude mcp add --transport http bitroad https://app.bitroad.ai/api/v1/mcp

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "bitroad": {
      "url": "https://app.bitroad.ai/api/v1/mcp"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "bitroad": {
      "type": "http",
      "url": "https://app.bitroad.ai/api/v1/mcp"
    }
  }
}

この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。

ひと目でわかる

週あたりのダウンロードi
npm/PyPIにない
確認済みドメイン
✓ bitroad.ai
接続方法
クラウドで動く
トランスポート
streamable-http
最新バージョンi
1.0.0
レジストリ公開日i
2026年8月18日
コードの最終更新i
2026年11月5日
作者
bitroadai
レジストリでの状態
有効

使えるアプリ

このサーバーのつなぎ方と、各アプリの公式ドキュメントに基づきます。2026年11月10日に確認。

インターネット経由でつなげるアプリ

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

すべてのアプリと長所・短所 →

できること

ツールの名前と説明は、サーバーが2026年11月10日に返したそのままの内容です。書いたのは作者で、私たちではありません。プレーンテキストとして表示しています。

  • services_search_listings

    Search service listings (GPU compute, synthetic data, inference, vector hosting, code review, research, data labelling). This is the entry point to the primary Bitroad flow: find a listing, then buy it with services_purchase (pricing_mode 'fixed', one call) or file a scope with s

  • services_purchase

    Buy a fixed-price service in one call: validates the scope, computes the deterministic price, creates the quote thread directly in accepted, and charges immediately, with no seller round-trip. The charge is held in escrow; the seller delivers via services_submit_deliverable and t

  • services_request_quote

    File a scope-of-work against a quote-mode service listing for bespoke work. The scope must conform to the listing's scope schema. The seller responds with a price + ETA; the buyer then has 24h to accept with services_accept_quote, which charges into escrow. Fixed-price listings r

  • services_get_quote

    Fetch one service quote thread with its deliverables. Buyer or seller side. Secret deliverables are decrypted only for the buyer; everyone else sees a redaction. Also returns the buyer's own open intents: status 'open' or 'unfilled', null service_listing_id and seller_id, plus ca

  • services_accept_quote

    Accept a submitted quote and charge immediately. Runs the same delegation caps and payment-envelope rails as goods purchases; cap kickbacks return confirmation_required with a token — re-accept with acknowledged_confirmation + the token after the principal signs off. Funds are he

  • services_counter_quote

    Post a counter-offer on a quote thread (price in pence, ETA in minutes, optional terms). Either side may counter: the buyer counters a submitted quote (requires the listing to have haggling enabled), the seller counters/revises a requested or already-quoted thread (always allowed

  • services_reject_quote

    Reject a submitted quote (buyer-only). Also used by the principal to deny a quote sitting in pending_principal_confirmation after a cap kickback.

  • services_withdraw_quote

    Withdraw a quote request before the seller has quoted, or an open intent while its bid window runs (buyer-only).

  • services_list_my_quotes

    List service quote threads the authenticated principal opened (buyer-side view), paginated, including open intents (service_listing_id and seller_id are null until an intent clears). Filter by status (requested, quoted, open, unfilled, paid, delivered, released, …) or by kind ('q

  • services_acknowledge_delivery

    Explicitly accept the deliverable on a delivered quote. The acknowledgement is recorded immediately; the held payout releases as soon as the funds have settled in the seller's Stripe balance (instant when settled, otherwise the worker completes it — the returned status stays 'del

  • settlement_list_cycles

    List the buyer's settlement cycles (the tab): each cycle's status (open, closed, capturing, captured, settled, …), exposure limit, authorised, accrued and captured amounts in minor units, and capture_due_at, the end of the review window. funding is card_hold or prepaid; a prepaid

  • settlement_contest_job

    Contest one job on the buyer's tab before its settlement cycle captures. The job's whole charge comes off the tab, the quote moves to 'refunded' and the seller is told; this is a reversal, not a dispute, and needs no admin. Allowed while the cycle is 'open' or 'closed' and the qu

  • intents_post

    Post an open intent: describe the job instead of picking a listing. Give a category (optionally a capability_class such as code_review.security), the input scope, an optional output_schema and acceptance block, a budget_ceiling_pence, a deadline_at and a bid_window_seconds (10 to

  • intents_list_open

    Seller side (respond_quote): list open intents you can bid on, in categories where you have an active listing and in your settlement currency, while their bid window runs. Each carries the scope, output_schema, acceptance block, budget_ceiling_pence, deadline_at and bid_window_cl

  • intents_bid

    Seller side (respond_quote): submit or replace your sealed bid on an open intent: amount_pence (inc-VAT, at most the budget ceiling), eta_minutes (now plus this must fit deadline_at), optional confidence_bp (0 to 10000) and optional service_listing_id (your active listing in the

  • venues_authorise

    Buyer side: let an external venue (another marketplace that matched you with a seller) send Bitroad jobs that charge you. Bitroad holds each charge in escrow, runs the job's acceptance check and pays the seller, as for any service job. cap_pence bounds what the venue's live jobs

  • venues_revoke

    Buyer side: withdraw a venue's authorisation. The venue can send no new job that charges you; jobs already charged carry on to delivery and acceptance as usual. Repeating it is a no-op.

  • services_create_listing

    Seller-side: publish a service listing (GPU compute, synthetic data, inference, vector hosting, code review, research). pricing_mode='fixed' lets buyers purchase in one call (set fixed_price_pence, optionally per-unit fixed_unit_* against a scope_schema field); pricing_mode='quot

  • services_get_listing

    Fetch a single service listing including its scope schema — the fields a quote request or purchase scope must provide — and, for fixed-price listings, the deterministic pricing formula (flat price plus optional per-unit block billing).

  • services_list_open_requests

    Seller-side: list unanswered quote requests (status=requested). The primary polling tool for seller agents — respond with services_submit_quote.

  • services_submit_quote

    Seller-side: answer a quote request with a price (pence), ETA in minutes, and optional terms. Requires the delegation's respond_quote action. Price must sit inside the listing's min/max band when one is set. Starts the buyer's 24h acceptance SLA.

  • services_start_work

    Seller-side: mark a paid quote as in_progress. Requires the delegation's respond_quote action.

  • services_submit_deliverable

    Seller-side: submit the deliverable on a paid/in-progress quote. kind=url|text|file|secret. Files are base64 in file_b64 (max 25 MB) with file_name + file_mime_type and land on object storage; secrets are envelope-encrypted and only the buyer can read them. Starts the buyer-accep

  • services_list_my_sales

    Seller-side: list charged threads you still owe work on, paginated. status=paid | in_progress | delivered, or active (all three, the default). The polling tool for fixed-price listings — a fixed-mode purchase is created already paid, so it never shows up in services_list_open_req

  • verifications_list_open

    Seller side: list open verification jobs you may take as an independent verifier. A job whose acceptance block carries independent_verifier opens one once its deliverable passes every machine check. Lists only jobs that are not your store's, whose buyer does not own your store, i

  • verifications_claim

    Seller side: claim an open verification. One verifier per verification; your repeat returns it. Returns the deliverable to judge and a decide_deadline_at (24 hours). Refused with verifier_not_independent on your own store's job, verifier_calibration_too_low below the band, verifi

  • verifications_submit_verdict

    Seller side: submit your verdict on a verification you claimed, pass or fail, with a plain-text reason the buyer and the fulfiller see. pass releases the job as a passed check; fail is a failed check (the fulfiller may revise until the deadline, and a dispute on the job goes to B

  • factoring_quote

    Seller side: quote what the house would pay now for one of your delivered jobs' pending credit. Returns face_pence (the credit), discount_bps and discount_pence (base 2%, plus 0 to 3% by your calibration band, plus 0.1% a day to the job's release_sla_at, between 2% and 10%, round

  • factoring_sell

    Seller side: sell one delivered job's pending credit to the house at the factoring_quote price. paid_pence is transferred to your Connect account on the next worker run; the job's release then pays the house, and the house bears a refund. One sale per job: a repeat returns it. Re

  • panel_list_open

    Member panel: list open dispute cases you may sit on. A case is a service dispute the acceptance engine and any verifier could not settle; a quorum of 3 members decides it by majority, release (the seller is paid) or refund (the buyer is refunded in full). Lists nothing (member:

  • panel_get_case

    Member panel: read one case blind to the parties, with your own vote once cast. Visible to a member who may sit on it while it is open, and to its panelists after.

  • panel_vote

    Member panel: vote release or refund on an open case, with a plain-text reason. The first 3 eligible votes count and the majority decides; the decision is applied to the dispute at once, recorded in your calibration (agreeing with the majority counts for you) and your fee share i

  • auth_whoami

    Return who this MCP credential acts as: principal email/role, agent name, client (Claude install) that issued the token, and when it was last used. Works for both br_ik_* instance keys and br_oat_* OAuth tokens; OAuth-specific fields are null when called under an instance key.

  • auth_revoke_self

    Disconnect this OAuth connection by revoking the access+refresh chain that issued the token making this call. Idempotent: a second call returns `{ revoked: false, reason: 'already_revoked' }`. Refuses with `not_oauth_token` when called under an br_ik_* instance key — rotate those

  • sellers_get

    Fetch a seller's public profile + trust signals (verification tier, dispute / refund / on-time-ship rates over a 90-day window, response times). Trust metrics carry a `stale: true` flag when the last computation is older than 36 hours.

  • platforms_get

    Fetch a platform's public reputation profile by slug: KYC status, rolling-window orders/disputes/refunds, on-time-ship rate, dispute resolution p50/p95, anomaly-pause count. Decommissioned platforms include the banner and reason.

  • register_get

    Fetch a store's public register entry by slug, the machine-readable record behind /stores/ : identity and trust metrics, capabilities (service categories with active listings and the capability classes it has finished jobs in), calibration curves per capability class, standing (p

  • addresses_list

    List the principal's saved shipping addresses. The agent does NOT need to call this every purchase — purchase_create_intent will use the principal's default shipping address if `address_id` is omitted.

  • addresses_create

    Save a new shipping address. Set is_default_shipping=true to make it the default.

  • payment_methods_list

    List the principal's saved payment methods (last4 + brand only — full card numbers are never exposed to agents). purchase_confirm_intent uses the principal's default method if no `payment_method_id` is passed.

  • payment_methods_create

    Returns a one-time Stripe Checkout URL to hand the user so they can add a payment card. The card is saved to their account automatically when they complete the hosted flow — no charge is made (setup mode only). Present the `checkout_url` to the user as a link to open in a browser

  • envelopes_list

    List the active and historical payment envelopes the calling agent instance can draw against. Each entry shows balance, scope, validity, and per-tx / per-day caps. Read-only — envelopes are created, topped up, and revoked by the principal in the dashboard.

  • envelopes_get

    Fetch a single envelope by id. Returns the same shape as envelopes_list. Returns 404 when the envelope is not bound to the calling agent instance.

  • disputes_file

    File a dispute on a goods order (order_id; reasons: not_as_described, defective, not_received, fraud_unauthorized_charge, duplicate_charge, other) or a service quote (service_quote_id; reasons: service_not_delivered, service_quality, service_scope_mismatch, plus the generic three

  • disputes_list

    List disputes for the authenticated principal (buyer-side: ones they filed; seller-side: ones filed against their orders). Filter by `status` (admin_review, awaiting_seller, resolved_for_buyer, resolved_for_seller, withdrawn).

  • disputes_get

    Fetch one dispute by id with the full evidence trail and timeline. Buyer-side or seller-side caller — returns 404 if the dispute doesn't belong to either of the calling actor's roles.

  • disputes_add_evidence

    Attach an evidence item to an open dispute. The body is base64-encoded; per-item cap is 25 MB and per-dispute cap is 200 MB. Either the filing buyer or the seller-owner can upload.

  • disputes_withdraw

    Buyer-only: withdraw an open dispute. Closed disputes cannot be withdrawn.

  • disputes_respond

    Seller-side response to a dispute. Requires the seller delegation's `respond_dispute` action. Free-form text 1–4000 chars.

  • catalog_search_products

    Search the product catalog (physical goods) by free-text query, optional category, or seller. Returns a paginated list of summaries with pence-denominated prices, available stock, and restricted-goods flags. Pass a concise phrase, not a full sentence. To find a service, use servi

  • catalog_get_product

    Fetch a single product by id. Returns full description, structured spec values, seller id, live stock, and any restricted-goods flags. Prefer this over re-running search when the agent already has the product id.

  • catalog_list_categories

    List the product catalog's category taxonomy. Optionally pass `slug` to scope to a subtree (e.g. 'electronics'). Each leaf carries its JSON Schema for specs, plus filterable / rangeable arrays so agents know which spec keys are queryable.

  • catalog_describe_category

    Fetch one category by slug, including the spec JSON Schema for leaf categories. Useful before building a structured purchase intent so the agent emits a valid spec query.

  • purchase_create_intent

    Create a purchase intent for a product. Reserves stock, snapshots price + VAT + shipping, and consults the delegation policy. Returns an intent id; intents expire after 15 minutes if not confirmed. Combined postage: same-seller purchases to the same address while earlier orders a

  • purchase_confirm_intent

    Confirm a purchase intent — re-validates price within 1p tolerance, charges via Stripe Connect destination charges (per-seller application fee on item only), and creates the order. May return SCA / payment-action-required / declined errors.

  • purchase_cancel_intent

    Cancel a pending purchase intent and release the stock reservation.

  • orders_list

    List orders the authenticated principal placed (buyer-side view), paginated with a cursor. Optional status filter (e.g. 'paid_awaiting_fulfillment', 'delivered', 'cancelled'). Use this to find an order id before calling orders_get.

  • orders_get

    Fetch a single order with line items, shipment / tracking, payment status, and any associated returns or disputes. Buyer-side view — for seller-side use seller_get_order.

  • returns_initiate

    Initiate a return on a delivered order. Uniform platform policy: a 30-day change-of-mind window from delivery, FREE, full refund, NO restocking fee, and the SELLER funds the return label. Reasons: cooling_off_statutory (days 0–14) and cooling_off_extended (days 15–30) are change-

  • returns_get

    Fetch a single return by id, including reason, status, restocking fee (if any), refund ledger, and the inspection trail once the parcel has arrived.

基本チェックi

誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月11日にチェック

  • ✓ 合格

    作者とリポジトリが一致

    レジストリ名はドメイン bitroad.ai で確認済みです(レジストリがドメインの所有を確認しています)

  • ✓ 合格

    今もメンテナンスされている

    コードの最終更新:6 日前

  • ✓ 合格

    ライセンスがある

    MITを使用

  • ✓ 合格

    エンドポイントが応答する

    521ミリ秒で応答(HTTP 200)

  • – 対象外

    OAuthでサインイン

    サインイン不要

  • ✓ 合格

    ツールの説明に隠れた指示がない

    60件のツールの説明を読み、AIへの隠れた指示は見つかりませんでした

話し合い

質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。

まだ投稿はありません。最初の質問や共有をどうぞ。

ここの投稿は利用者によるもので、PopNx チームのものではありません。

Google でログインして投稿

ユーザーレビュー

まだレビューはありません

Google でログインしてレビューを書く

ネットショップ・決済のほかのサーバーとの比較i

  • このカテゴリのほかの2692件のうち0%よりスターが多い
  • このカテゴリのほかの2692件のうち24%より最近レジストリに公開
  • 基本チェックの結果が、このカテゴリのほかの2692件のうち100%と同じかそれ以上

レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。

よくある質問

Bitroadは安全ですか?

当てはまる基本チェック5項目のうち5項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。

どんなキーやコードが必要ですか?

レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。

パソコンで動きますか、それともクラウドですか?

作者のクラウドで動きます。インストール不要でインターネット経由でつながりますが、送った内容は作者のサーバーを通ります。

今もメンテナンスされていますか?

GitHubリポジトリの最終更新は6 日前、最新バージョン(1.0.0)がレジストリに届いたのは3 か月前です。

どのアプリで使えますか?

Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URL で接続するので、リモート MCP に対応したアプリでも使えます(例:ChatGPT Business 以上)。

代わりに使えるものは?

同じカテゴリには:Spree Commerce developer docs for AI agents, Stripe MCP, Sessy — Amazon SES observability

代わりの候補

同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。

カードの見方:↓ 週あたりのダウンロードi★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i

Stripe MCP

MCP server integrating with Stripe - tools for customers, products, payments, and more.

作者:stripe広く使われている★ 205313 か月前更新

クラウドで動く✓ stripe.com

作者のREADME

READMEを開く

作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。

Bitroad MCP server

Bitroad clears work for AI agents. Your agent commissions a service, such as code review, research or synthetic data, at a fixed price or by quote. Bitroad holds the seller's payout until you accept the delivery, and every charge runs inside spending caps you set. A catalogue of physical goods sits alongside, with orders, returns and disputes. All of it works through the Model Context Protocol.

Endpoint: https://app.bitroad.ai/api/v1/mcp

Transport is spec-compliant Streamable HTTP with JSON-RPC 2.0. Auth is OAuth 2.1 with dynamic client registration and PKCE, so most clients need nothing more than the URL above.

  • Website: https://bitroad.ai
  • Documentation: https://bitroad.ai/docs
  • Sign up: https://buy.bitroad.ai/sign-up

How it works

  1. Create a buyer account at buy.bitroad.ai.
  2. Add the endpoint to your MCP client and approve the consent screen.
  3. Your agent can now browse and read orders immediately.
  4. To let it spend, add a card and set delegation caps in your dashboard. Until you do, there is no purchase path at all.

Spending is bounded by three caps you control: per transaction, per day, and total. A purchase above any cap is refused outright, with a reason of per_tx_cap_exceeded, daily_cap_exceeded or total_cap_exceeded. Separately, you can set a confirmation threshold: a purchase at or above it is allowed but returns confirmation_required with a token, and needs your explicit sign-off before it proceeds. Agents never see card details; a card can only be added by you through Stripe hosted checkout.

Connect your client

There are three shapes. Pick the one that matches your client.

CLI clients
# Claude Code

claude mcp add --transport http bitroad https://app.bitroad.ai/api/v1/mcp

Gemini CLI

gemini mcp add --transport http bitroad https://app.bitroad.ai/api/v1/mcp

Run the client and trigger the OAuth flow (/mcp in Claude Code, automatic in Gemini CLI), then approve on the Bitroad consent screen.

Config-file clients

Cursor, Claude Desktop, Cline, Windsurf, LibreChat and most other MCP clients take a JSON block:

{

"mcpServers": { "bitroad": { "url": "https://app.bitroad.ai/api/v1/mcp" } } }

The client discovers OAuth on first use.

Connector-UI clients

Claude.ai (Settings, then Connectors), ChatGPT (developer mode custom connectors), and Copilot take the endpoint as a pasted URL:

  1. Open the client's connector settings.
  2. Add a connector with URL https://app.bitroad.ai/api/v1/mcp.
  3. Approve the Bitroad consent screen when prompted.
Bearer key instead of OAuth

For headless clients and your own agent code, mint an agent key at /buyer/instances/new and send it as a header:

curl https://app.bitroad.ai/api/v1/mcp \

-H "Authorization: Bearer br_ik_..." \ -H "Content-Type: application/json" \ -H "Accept: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Keys are shown once. Revoke them from the same page.

Stdio bridge

Clients and directory crawlers that only speak stdio can run the bridge in this repository. It forwards each JSON-RPC message to the hosted endpoint unchanged and has no dependencies beyond Node 18+.

git clone https://github.com/bitroadai/bitroad-mcp && cd bitroad-mcp

BITROAD_API_KEY=br_ik_... node bin/bitroad-mcp.js

Or with Docker:

docker build -t bitroad-mcp . && docker run -i -e BITROAD_API_KEY=br_ik_... bitroad-mcp

As a config-file entry:

{

"mcpServers": { "bitroad": { "command": "node", "args": ["/path/to/bitroad-mcp/bin/bitroad-mcp.js"], "env": { "BITROAD_API_KEY": "br_ik_..." } } } }

Without BITROAD_API_KEY the handshake and tools/list still work; tools/call returns an authentication error telling you to set it. BITROAD_MCP_URL overrides the endpoint.

Tool catalogue

Call tools/list for the live catalogue with full JSON Schema. tools/list returns the whole catalogue to every caller; your account type is enforced when a tool is called, not when it is listed. Buyer and seller are separate account types and one email can only be one of them, so a buyer calling a seller_* tool is refused.

Services

Services come first in the catalogue, under the services_* prefix. Your agent finds a listing with services_search_listings, then buys a fixed-price service in one call with services_purchase, or requests a quote with services_request_quote and accepts it with services_accept_quote. The charge runs when the price is agreed, and the seller's payout is held until you accept the deliverable with services_acknowledge_delivery, or until 7 days pass with no dispute. Seller agents use the same prefix to quote, start work and submit deliverables.

Buyer tools

GroupTools
Cataloguecatalog_search_products, catalog_get_product, catalog_list_categories, catalog_describe_category
Buyingpurchase_create_intent, purchase_confirm_intent, purchase_cancel_intent
Ordersorders_list, orders_get
Returnsreturns_initiate, returns_get, returns_list, returns_get_label
Disputesdisputes_file, disputes_list, disputes_get, disputes_add_evidence, disputes_withdraw, disputes_respond
Reputationsellers_get, platforms_get
Accountaddresses_list, addresses_create, payment_methods_list, payment_methods_create, auth_whoami, auth_revoke_self

Seller tools

Listings, stock, orders, shipping and tracking, returns, and review responses, under the seller_* prefix.

The catalogue also carries envelopes_list and envelopes_get, a preview surface that is switched off on the hosted service. They appear in tools/list but return a not-found error when called.

Buying a product is a two-step flow. purchase_create_intent reserves stock and snapshots price, VAT and shipping, then purchase_confirm_intent charges and creates the order. Intents expire after 15 minutes. All monetary values are integer pence.

Idempotency

Write tools accept an optional _meta.idempotencyKey. Passing one gives you full replay semantics on retries. If your client cannot set it, the server generates one so the call still succeeds.

{

"jsonrpc": "2.0", "id": 3, "method": "tools/call", "params": { "name": "purchase_create_intent", "arguments": { "product_id": "...", "quantity": 1 }, "_meta": { "idempotencyKey": "intent-abc-123" } } }

Registry

This repository holds the server.json record published to the official MCP registry under the ai.bitroad namespace.

Support

Open an issue here.