BuyAPI MCP Server

Vendor intelligence for AI coding agents choosing developer tools and stacks.

Tools

Last Updated

Jun 14, 2026

What is the BuyAPI MCP Server?

The BuyAPI MCP server gives AI agents structured, permission-aware access to BuyAPI through the Model Context Protocol. With 7 pre-built actions, agents can read, create, and update BuyAPI data on behalf of authorized users.

Willow ships the BuyAPI MCP server as part of an enterprise control plane. Every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to a full audit trail, and integrates with Splunk and Loki for SIEM visibility. Connect from Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, or any custom agent. Install once, distribute org-wide, and see exactly how BuyAPI is being used by every AI agent in your stack.

Tools

vendors.resolve

First stop for category-specific vendor recommendations and vendor ID discovery. Finds BuyAPI vendor IDs for a user question; provide category when known. Use this when the user asks which provider in a category fits their constraints. With a covered category, the response includes ranked results plus a top-3 decision matrix with fit labels, confidence, tradeoffs, cost notes, freshness, and sources. Do not use this for local coding/debugging/docs questions unless they involve choosing a software vendor or tool. If the category is outside BuyAPI's corpus, the tool returns an explicit "not in corpus yet" result instead of inventing vendors.

vendors.details

Follow-up tool for one known vendor. Retrieves detailed pricing, features, limits, gotchas, comparisons, and source provenance. Call vendors.resolve first unless the user already provided a BuyAPI vendor ID like /database/supabase. Use this after a candidate is selected and the user needs claim-level pricing, limit, gotcha, or provenance details.

vendors.evidence

Returns recent reviewed BuyAPI evidence rows for a vendor, category, stack, or comparison. Use this when the user asks why BuyAPI believes something, what sources support a recommendation, or what recent human/source/opinion/history signals exist. This is a trust and provenance follow-up, not the first recommendation tool.

stacks.findSimilar

Finds reviewed public stack examples related to a vendor, or recent curated stack examples. Use this when the user asks who uses a tool, what similar builders use, or wants examples of real stack combinations. Do not use it as a generic recommendation tool.

vendors.compare

Compares two or more already-known BuyAPI vendors for a specific workload or decision. Use this when the candidate set is known, for head-to-head questions like "Convex vs Supabase vs Neon for a realtime SaaS" or "Stripe vs Paddle for a marketplace". If the user has not named candidates, use vendors.resolve first.

vendors.estimateCost

Produces directional monthly cost estimates from BuyAPI pricing data and explicit workload inputs. Use this only when the user asks for cost math and provides explicit workload inputs. Missing workload fields are returned as assumptions or unknowns instead of being hallucinated. Treat results as BuyAPI claim-based estimate math; verify exact billing in first-party docs, vendor CLIs, or vendor MCPs before purchase or production decisions.

stacks.recommend

Recommends a complete stack from BuyAPI's corpus with a structured decision matrix, cost estimate, assumptions, unknowns, alternatives, and sources. Use this when the user is starting a project or asks for a complete multi-layer stack choice. Do not use this for local coding/debugging/docs questions that do not involve software or vendor selection. Do not call vendors.resolve first; this tool handles retrieval and ranking.

Customize Tools

Edit descriptions, modify arguments, select tools, or add new ones

Set Up Your BuyAPI MCP Server in Minutes

Add the following configuration to your MCP client. Authentication is handled via OAuth. Compatible with Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, and any MCP-compatible agent.

Claude Desktop

claude_desktop_config.json

{
  "mcpServers": {
    "willow-buyapi": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/buyapi"
    }
  }
}

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "willow-buyapi": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/buyapi"
    }
  }
}

Claude Code

CLI

claude mcp add willow-buyapi --transport http https://<org>.mcp-s.com/mcp/mcp/buyapi

n8n

HTTP Request Node

{
  "url": "https://<org>.mcp-s.com/mcp/mcp/buyapi",
  "method": "POST"
}

Or click "Install with Willow" above to set up automatically with SSO and RBAC preconfigured.

Enterprise Governance for BuyAPI

Willow adds the layer BuyAPI and every other SaaS doesn't ship out of the box: every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to full audit logs, and detects shadow AI usage across your stack. One MCP gateway. Any agent. Every tool.

BuyAPI MCP Server FAQ

What is the BuyAPI MCP server?

The BuyAPI MCP server is a Model Context Protocol implementation that lets AI agents like Claude, Cursor, and ChatGPT read and write BuyAPI data through a standardized interface. Willow hosts and governs this server so enterprises can roll it out without a security review backlog.

How is Willow's BuyAPI MCP server different from the official one?

The official BuyAPI MCP server is scoped to a single user's account and does not include enterprise governance. Willow's version adds SSO, RBAC, audit logging, shadow AI detection, and centralized control over which actions agents can take across the entire org.

Which AI clients work with the BuyAPI MCP server?

Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code with MCP support, n8n, and any custom agent built with OpenAI Agents SDK, LangChain, Vercel AI SDK, or Anthropic SDK.

Is the BuyAPI MCP server secure? How does Willow handle authentication?

Every call runs behind your existing SSO (Okta, Azure AD). Per-user OAuth scopes the agent to exactly what that user can do in BuyAPI, nothing more. No credentials reach the LLM. Every action writes to an audit trail.

Can I limit which BuyAPI actions agents can take?

Yes. Willow lets you scope agents to specific actions, specific projects, or specific environments. Toggle actions on or off in the dashboard, or enforce policy via infrastructure-as-code through GitHub.

How do I detect shadow BuyAPI MCP servers in my org?

Willow's browser extension and discovery service surface unmanaged MCP servers, skills, and AI agents across the org. If a developer installed an unapproved BuyAPI MCP locally, you'll see it.

What does the BuyAPI MCP server cost?

Pricing depends on org size and deployment model (SaaS, dedicated cloud, self-host). See withwillow.ai/pricing or contact sales for a quote.

How do I install the BuyAPI MCP server with Willow?

Install via the Willow Connect Panel in one click, or paste the JSON snippet above into your Claude Desktop, Cursor, or Claude Code config. SSO and RBAC inherit from your existing Willow setup.