# BuyAPI MCP server

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

## Links
- Registry page: https://www.getdrio.com/mcp/io-github-thesnakefang-buyapi-mcp
- Repository: https://github.com/TheSnakeFang/buyapi-mcp
- Website: https://buyapi.ai

## Install
- Command: `npx -y buyapi`
- Endpoint: https://buyapi.ai/api/mcp
- Auth: Not captured

## Setup notes
- Package: Npm buyapi v0.7.1
- Remote endpoint: https://buyapi.ai/api/mcp

## 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. Endpoint: https://buyapi.ai/api/mcp
- 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. Endpoint: https://buyapi.ai/api/mcp
- 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. Endpoint: https://buyapi.ai/api/mcp
- 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. Endpoint: https://buyapi.ai/api/mcp
- 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. Endpoint: https://buyapi.ai/api/mcp
- 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. Endpoint: https://buyapi.ai/api/mcp
- 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. Endpoint: https://buyapi.ai/api/mcp

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: io.github.TheSnakeFang
- Version: 0.7.1
- Runtime: Npm
- Transports: STDIO, HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: May 4, 2026
- Source: https://registry.modelcontextprotocol.io