Apiosk Connect

io.github.obcraft由 GitHub 帳號 obcraft 發布v1.7.0更新於 Oct 24, 2026

Discover, pay for, execute, and publish APIs through Apiosk.

已驗證Streamable HTTP可網頁執行金融資料與分析商業與電商

概覽

AI 產生的概覽

Apiosk Connect 讓助理提出問題、比較付費 API 資料來源、核准報價總額並執行購買,以取得附引用的結果。

可以做什麼
  • 提出問題並檢視相符的資料來源及其輸入欄位與價格
  • 將選定的資料來源整理成一個經審閱的最高總額,並明確核准該報價
  • 查看進度、重新報價、補上缺少的輸入、重試探索並調整任務選項
  • 讀取已儲存的答案、證據、結果頁面、下載內容與對話,並依已購證據追問
  • 審閱已連結應用程式的操作,並把週期性檢查交給主機排程器
適用情境
適合希望助理透過購買特定第三方 API 端點的存取權來回答問題、而非依賴一般知識的情境,且每次支出前都有明確的核准步驟。也適合檢視已儲存的證據,並對已購買的資料繼續追問。
執行需求
可使用 mcp.apiosk.com 的遠端端點(OAuth 驗證),或使用 npm、PyPI 本機套件並需 Node.js 22.16 以上版本。需要已授權的 Apiosk 連線;stdio 方式使用 APIOSK_CONNECT_TOKEN,APIOSK_PRIVATE_KEY 為選用的自動 x402 付款私鑰。另需工作區 ID 以及連線至 Apiosk Gateway 的網路。
安裝前請注意
核准報價即授權在報價上限內實際付費,且總額涵蓋多個提供者,因此應先確認幣別、總額、資料來源、缺口與有效期限。APIOSK_PRIVATE_KEY 是可動用資金的钱包私鑰,須與 APIOSK_CONNECT_TOKEN 一同保存在私人設定中,切勿寫入已提交的檔案。本機日誌會在磁碟保存對話與核准紀錄,託管執行需要持久化磁碟區。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Apiosk Connect,將其新增到工作區。
  2. 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.obcraft%2Fapiosk-mcp/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。

{
  "mcpServers": {
    "apiosk-connect": {
      "type": "http",
      "url": "https://mcp.apiosk.com/mcp"
    }
  }
}

README

Apiosk MCP

@apiosk/mcp 3.0.0 brings the Apiosk Ask workflow to Claude, Codex and other MCP hosts: ask a question, compare matching sources, review inputs and one total, approve that request, and inspect saved results. It uses the existing Gateway for discovery, planning, prices, execution and evidence.

MCP1 card URLs, connection identity, token formats and cached Ask tool signatures remain compatible. Compatibility operations stay private to cards; new model connections continue to see Ask first. Both old and new approval calls share the same durable approval record.

The default is question-scoped source discovery. There is no global “browse the catalog” flow. For example, “What does ASML do?” should first call apiosk_ask with that question and display its matching sources; a model's general knowledge is not an Apiosk result.

This repository is the canonical obcraft/apiosk-mcp implementation. Versioned source and manifests do not establish that this version has been deployed, published or installed in a host.

Ask interactions and embedded components

The server exposes 36 public tools and six private component operations, saved-request resources and an Ask prompt. The actual App Ask React components and design tokens are vendored in src/ask-page/ and compiled into the self-contained embedded resource. The local tester loads that same resource. src/ask-ui/ retains the original MCP transport and compatibility renderers; every operation still uses the durable saved-request and approval journal.

Source discovery uses the App’s filtering, deduplication and provider ordering. Offered endpoint descriptors enrich matching sources without adding unrelated catalog entries. Account display currency comes from Gateway’s read-only /v2/display-context; quoted atomic amounts remain unchanged. Rebuild the embedded bundle with npm run build:ask-page after editing its sources.

Manual source selection prepares each chosen native endpoint with the App’s exact input values. Connected clients use /v2/ask/source/prepare, which requires explicit approval even when the connection has a standing spending rule. The MCP combines those saved quotes into one reviewed maximum; preparation does not purchase data.

MCP Apps and ChatGPT-compatible metadata identify the embedded resources. Model-visible results carry compact source identifiers, status, input needs and the exact approval. Full component data travels separately in _meta.apiosk_card_data, so large source schemas and raw response trees do not flood the model context. Saved evidence remains available through the result and evidence tools.

Hosts that support embedded components can show the interactive cards. Text-only hosts receive structured results and use the public tools. Support and rendering still depend on the host; passing local tests does not establish installed Claude, Codex or ChatGPT acceptance. Read-only HTML exports are separate from interactive cards.

InteractionTools
Ask and inspect matching sourcesapiosk_ask, apiosk_sources
Edit source inputs and prepare one totalapiosk_prepare
Review and explicitly approve the exact quoteapiosk_approve
Read progress, refresh prices, supply choices or missing inputapiosk_status, apiosk_requote, apiosk_continue
Retry interrupted discovery and adjust task optionsapiosk_retry_search, apiosk_task_options, apiosk_source_selection, apiosk_analysis_quote
Saved answers, evidence, pages, downloads and conversationsapiosk_result, apiosk_evidence, apiosk_result_page, apiosk_artifact, apiosk_chats
Follow up using purchased evidenceapiosk_follow_up
Connected app actions and recurring checksIntegration/action review tools, native recurring tools and apiosk_schedule_handoff

apiosk_ask defaults to mode: "sources". Automatic planning is available with mode: "automatic". Preparation never approves a purchase. Review the returned currency, maximum total, sources, gaps, expiry and approval ID before authorizing execution. The visible choices use the same purchasability filter as the Ask page; discovery metadata and source options are not purchased findings.

Results retain source dates, citations, coverage and gaps, including meaningful 0 and false values. Local filters, sorting, chart/table views, saved pages and exports reuse saved data. Follow-ups use purchased evidence where possible; a need for new data creates a separately reviewed request.

Run from this checkout

Requires Node.js 22.16 or newer and an authorized Apiosk connection. In this workspace the canonical directory is /Users/olivier/Documents/Apiosk/Production/Main/mcp.

sh
cd /Users/olivier/Documents/Apiosk/Production/Main/mcpnpm cinpm run checknpm test

Use the existing Apiosk credentials in your private environment or local .env; do not put credentials in committed examples. Runtime entry points read environment variables. To load .env explicitly, use Node's --env-file option.

Entry pointPurpose
node index.mjs / npm run start:stdioLocal stdio MCP; uses the configured connection token. The apiosk, apiosk-mcp and apiosk-mcp-server package commands use this entry.
node server.mjs / npm startCanonical hosted HTTP server, default port 3000, with OAuth metadata, registration, authorization and token routes. Also retains authenticated legacy SSE endpoints.
node bin/mcp-2.mjs --http --host 127.0.0.1 --port 3012Minimal bearer-token HTTP transport for local testing. This compatibility filename remains internal; this entry does not provide the hosted OAuth flow.

For stdio with a private .env:

sh
node --env-file=.env index.mjs

The hosted server preserves the existing OAuth identity and secret configuration. Starting it requires those settings, including its signing secret; use node --env-file=.env server.mjs when they are in a local file. HTTP clients authenticate each request themselves. A server-wide token is never lent to HTTP callers. /health reports process health, not Gateway or source readiness.

Local tester

The tester runs at http://127.0.0.1:3013 and defaults to an MCP endpoint at http://127.0.0.1:3012/mcp. Start the minimal local MCP transport in one terminal:

sh
node --env-file=.env bin/mcp-2.mjs --http --host 127.0.0.1 --port 3012

Start the tester in another:

sh
npm run dev:chat

To test the canonical hosted server on port 3000 instead:

sh
MCP_DEV_URL=http://127.0.0.1:3000/mcp npm run dev:chat

The tester reads this checkout's .env, .env.v2.local and .env.dev.local, with inherited environment values taking precedence. It reuses an existing MCP_DEV_TOKEN and OPENROUTER_API_KEY. If no local OpenRouter key is set, it reads only the provider key from the sibling gateway/.env (OPENROUTER_API_KEY, then INTENT_API_KEY). It does not inherit Gateway execution flags or change those credentials. MCP_DEV_PORT, MCP_DEV_URL and MCP_DEV_MODEL override the tester defaults. Set MCP_DEV_GATEWAY_URL for a custom Gateway event origin; the embedded card and tester use the same fixed origin policy for live status updates.

Connect the intended account before asking a question. The tester calls apiosk_ask for the first question and renders the same embedded components served to other hosts. An initial discovery stops at the authoritative Ask card without an extra model-written answer. Later model continuations receive a bounded projection of tool results; full card data stays available to the component. Model API usage and approved source purchases are separate operations.

Connect Claude or Codex

Use examples/codex.toml, examples/claude-code.mcp.json or examples/claude-desktop.json, preserving other configured servers. Adjust absolute paths for your installation and keep tokens in private configuration or environment variables. These files are examples, not an installed connection.

The hosted connector address remains https://mcp.apiosk.com/mcp; local source changes do not update that deployment. The Apiosk plugin supplies Ask-first instructions and the hosted connection definition. server.json, manifest.json and dxt.json describe the canonical package; a desktop manifest is not a built or installed bundle.

Configuration and backend boundaries

VariableMeaning
APIOSK_GATEWAY_V2_URLData/execution Gateway; defaults to https://gateway.apiosk.com. Use loopback HTTP only for a local Gateway.
APIOSK_GATEWAY_URLExisting OAuth agent gateway setting; it does not select the data/execution Gateway.
APIOSK_CONNECT_TOKENApiosk agent connection credential for stdio.
APIOSK_TOKENOverrides the connection token. A valid personal App session JWT enables account-only routes; this server does not refresh that App session.
APIOSK_WORKSPACE_IDStdio workspace. HTTP callers use x-apiosk-workspace-id.
APIOSK_MCP_STATE_DIRPersistent private journal directory; defaults to .local/state in the package.
APIOSK_MCP_PORT / PORTHTTP port; defaults to 3000.
APIOSK_MCP_HOST / APIOSK_MCP_BIND_HOSTListener address. The hosted entry defaults to 0.0.0.0; use loopback for local-only access.
APIOSK_MCP_ALLOWED_HOSTS, APIOSK_MCP_ALLOWED_ORIGINSExplicit host/origin controls for the HTTP listener.

Gateway scope, budget, workspace and feature restrictions remain authoritative. Organization API keys are not substitutes for agent connection tokens in the raw task/approval protocol. Account-only integrations and native recurring operations may require a valid App session and backend enablement; an app_only or public_api_required response is not bypassed.

Connection tokens use /v2/ask/page, which applies the Ask page's interpreter, validation and source searches. App sessions use the original App routes. Both use the same source filtering, grouping, input values and display currency. Connected discovery preserves the App's matches without the older public API's interpretation repairs or extra source expansion; signed searches remain bound to the account, connection and workspace. Source refresh reuses the saved parse, and automatic planning adopts that displayed search without parsing the question again.

Recurring execution needs its own explicit review of the workflow, schedule, destination and cost limits. apiosk_schedule_handoff supplies instructions for the host scheduler and reports schedule_created: false; it does not create a scheduled job. External app actions likewise require their own reviewed execution.

Saved state, recovery and deployment

The journal stores private conversations, evidence and approval intent with private file permissions, without storing credentials. Conversations are separate from the web app's chat-history table; authorized Gateway tasks can be imported by ID. State scopes include the Gateway and workspace. Raw bearer callers are token-scoped; hosted OAuth sessions retain their verified grant scope across token refresh.

Atomic writes and per-request locks record approval intent before dispatch. An uncertain purchase is not blindly replayed: read saved status and use the returned recovery path. The quoted total is a spending ceiling across providers, not an all-or-nothing transaction. Local disk failures stop money-moving actions.

Hosted operation requires a persistent journal. The Fly configuration preserves the existing app identity and expects an existing mcp_state volume mounted at /data; run one machine until shared state and distributed locking are implemented. Provision and review that volume before deploying. See deployment and release instructions.

Pushing the repository runs checks only. Deployment and publication are separate manual workflows. Tests use controlled fixtures and do not purchase source data; local success is not proof of production retrieval, message delivery, a running schedule or an installed host connection.

來源:README.md,提交 66b402c

工具

0
該伺服器需要登入,因此 SourceWeft 無法在沒有帳號的情況下讀取其工具,也未收錄。已連接帳號所能看到的內容可能因帳號及其權限而異。

版本歷史

1
  1. v1.7.0最新Sep 16, 2026

評分

已滿足適用檢查項的 85%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分