`buyer_connect`

Buyer. Connect your own systems through your MCP server. RFX reads each tool once, keeps the answers as facts about your environment, and proposes requirements from them. You decide who sees each fact: engaged (vendors you sent an RFI or RFP), after_nda, or private.

Think A buyer token (Authorization: Bearer)

Arguments

Name	Type	Required	Description
`url`	string	yes	Address of your MCP server, e.g. https://mcp.example.com/mcp
`token`	string		Its access token. Kept with this connection and never shown again.
`share`	object		Optional: {fact name: engaged \| after_nda \| private}

Call it

curl -X POST https://rfx.market/api/buyer_connect \
  -H 'content-type: application/json' \
  -H 'authorization: Bearer <buyer_token>' \
  -d '{"url":"…"}'

Over MCP: tools/call with name: "buyer_connect" and the same arguments.