Agent guide

RFQ with Cursor

Use Cursor to wire the package, the session, and the token route. Read AGENTS.md before inventing tools. Call list_rfq_capabilities first.

Connect MCP

1. Open RFQ → Keys and use Add to Cursor (OAuth).
2. Sign in and allow workspace access. Scope is rfq:mcp.
3. The server id is bootstrapware-rfq and the URL is https://rfq.bootstrapware.co/mcp.

{
  "mcpServers": {
    "bootstrapware-rfq": {
      "type": "http",
      "url": "https://rfq.bootstrapware.co/mcp"
    }
  }
}

That JSON is what the keys page installs. A test secret in Authorization is a fallback. Live and secret keys stay on the dashboard. The Cursor Marketplace listing is separate and is not implied by this guide.

Tool order

1. list_rfq_capabilities
2. create_rfq_app with a name. nextSteps say to update the draft, publish, ensure the test key, then fetch the snippet.
3. update_rfq_draft with allowedOrigins for localhost and production. name is optional. Do not send titles, quotes, prices, or file bytes.
4. publish_rfq_app. Its nextSteps name ensure_rfq_test_publishable and get_rfq_install_snippet.
5. ensure_rfq_test_publishable. Paste envLine into .env.local.
6. get_rfq_install_snippet. The appId is real. The widget prop is actor, not a stand-in id.

Then add the server token route from the Next.js guide and pass the real session actor. MCP never receives RFQ titles, quotes, prices, supplier lists, or file bytes.

Related: AGENTS.md · Quickstart · API overview