vendor_connect_mcp
Vendor. Read an MCP server into your context, instead of uploading documents: your own, or one in front of another system (a compliance platform, a wiki). Connect as many as you have; each is its own connection, told apart by its address (host and path). RFX calls only tools that read: the ones you name in tools, or else those your server marks read-only and that need no arguments. Name the tools on a server that also holds personal or internal data. Each answer becomes a source file at the level you choose, and the capabilities read from it wait for a person to review. Call again with the same address to re-sync. A server that signs people in (OAuth) instead of taking a token answers status sign_in_required with a sign_in_url: give it to a person at your company, who signs in there; RFX connects the server when they come back and renews the access itself.
Vendor A vendor key (x-vendor-key)
Arguments
| Name | Type | Required | Description |
|---|---|---|---|
name | string | What to call this server, e.g. "Drata" or "Product docs" | |
url | string | yes | Address of your MCP server (streamable HTTP) |
token | string | Bearer token for it, if it takes one. Leave it out for a server that signs people in. Kept with the connection, never shown again | |
client_id | string | Only for a sign-in service that does not let RFX register itself: the client id of an OAuth app made there for RFX | |
client_secret | string | That app's secret, if it has one | |
tools | list of string | Tool names to read. Default: read-only tools that need no arguments | |
level | "L2" | "L3" | L2 (default): opens after the NDA. L3: opens only for negotiation |
Call it
curl -X POST https://rfx.market/api/vendor_connect_mcp \
-H 'content-type: application/json' \
-H 'x-vendor-key: <vendor_key>' \
-d '{"url":"…"}'Over MCP: tools/call with name: "vendor_connect_mcp" and the same arguments.