vMCP: answer a call for an unconnected provider with a URL elicitation carrying the connect link

オープン
#7,188 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
go

調査の方向性

Start by reading the related issues #6407 and #6970, then trace the outbound credential read and render seam for tools/call in the vMCP implementation. Check how protocol version and declared client capabilities select the elicitation shape. Done means the acceptance cases pass: URL capable clients receive the connect link without a backend call, and storage or ownership failures remain errors.

索引モデルが issue の本文から書いたものです。

説明

needs-triage

Part of #6406. Depends on #6407; uses the URL elicitation answer from #6970.

Problem: When a delegated token's user has no stored credential for the routed provider, or its refresh is rejected as an invalid grant, #6407 returns a "needs authorization" error carrying a connect link. Nothing turns that error into an answer an MCP client can act on. vMCP's URL elicitation answer (#6970) is produced only by an embedder's in-process decorator, so every deployment would need its own decorator to tell the user where to connect, and a standalone vMCP can't do it at all.

Change:

  • When the outbound credential read returns "needs authorization" for a tools/call, vMCP answers that call with the URL elicitation answer (#6970), carrying the connect link, before sending anything to the backend. The existing render seam chooses the shape for the protocol and the client's declared capabilities. A client that didn't declare URL mode, or whose capabilities vMCP doesn't know, gets the fallback; vMCP's own answer sets no fallback text, so the link never appears in it.
  • The connect link is the one #6407's answer carries: an entry point on the gateway's authorization server that signs the user in and connects that provider (#6831's explicit reconnect). It is never taken from a backend or from the request, and it identifies the provider and nothing about the user.
  • Storage failures and transient refresh failures stay infrastructure errors, never an elicitation. A row owned by another user stays a hard failure.
  • Deployments without upstreamCredentialScope: platformUser are unchanged.

Acceptance:

  • Delegated user with no connection for the routed provider: a client that declared URL elicitation gets the URL elicitation answer with the link for its protocol version, and the recording backend receives no tools/call.
  • After the user connects through the link, the same call succeeds with their credential.
  • A storage outage gets an infrastructure error, not an elicitation. Another user's row is refused.
  • Session-mode behaviour is unchanged.
主要言語
Go
スター
2.3k
フォーク
332
平均マージ
19時間 39分
マージ済み PR(30日)
174

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

stacklok/toolhive のほかの issue

stacklok/toolhive の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。