What can you do with this server?

AgentDeals is an MCP server for discovering, comparing, and monitoring developer infrastructure deals, free tiers, and startup credits. * search_deals: Find free tiers, credits, and discounts across 1,500+ tools by keyword, category, vendor, eligibility (e.g. accelerator, OSS, student), sort, and recency filters. * plan_stack: Get cost-optimized stack recommendations for a use case, estimate costs at hobby/startup/growth scale, or audit an existing stack for risks, costs, and gaps. * compare_vendors: Compare two vendors side-by-side (free tier limits, pricing, risk) or check a single vendor's pricing risk, with alternatives. * track_changes: Monitor pricing changes, free tier removals, limit adjustments, new free tiers, and upcoming expirations, filtered by vendor, change type, or date. * REST API access: Additionally supports programmatic offer search, category listing, new offers, pricing changes, stack recommendations, cost estimates, vendor comparison, risk checks, audits, stats, and traffic data.

Which integrations are available for this server?

Provides tools to search and retrieve Google Cloud startup program deals and infrastructure credits. Enables tracking of Heroku's pricing changes, such as free tier removals or restructuring. Allows discovery and comparison of MongoDB Atlas free tier infrastructure offers and shared cluster details. Facilitates monitoring of PlanetScale's pricing shifts and available database hosting alternatives. Allows tracking of Render's pricing restructures and current infrastructure offers. Provides access to verified startup program deals and credits for Stripe services, including Stripe Atlas. Enables searching and comparing Supabase's current free tier limits and database hosting deals. Allows users to monitor Vercel's pricing updates and verify current infrastructure offers.

agentdeals

by robhunter

Overview Schema Related Servers Score Discussions

TypeScript

Hybrid

AgentDeals

npm version npm downloads

An MCP server that aggregates free tiers, startup credits, and developer tool deals — so your AI agent (or you) can find the best infrastructure offers without leaving the workflow.

AgentDeals indexes real, verified pricing data from 1,500+ developer infrastructure vendors across 54 categories. Available on npm for local use or as a hosted remote server. Connect any MCP-compatible client and search deals by keyword, category, or eligibility.

Live: agentdeals.dev

Install

Option A: Claude Code Plugin (one-click)

Install AgentDeals in Claude Code with a single command:

claude plugin install robhunter/agentdeals

This auto-configures the remote MCP server — no local setup needed. All 4 tools and 6 prompt templates are immediately available.

Option B: Claude Desktop Extension (one-click)

Install AgentDeals directly in Claude Desktop — no configuration needed:

Download the latest agentdeals.mcpb from Releases
Double-click the file to install in Claude Desktop
All 4 tools and 6 prompt templates are immediately available

Or browse for AgentDeals in Claude Desktop under Settings > Extensions.

Option C: npx (local stdio)

No server needed. Runs locally via stdin/stdout:

{
  "mcpServers": {
    "agentdeals": {
      "command": "npx",
      "args": ["-y", "agentdeals"]
    }
  }
}

Option D: Remote HTTP

Connect to the hosted instance — no install required:

{
  "mcpServers": {
    "agentdeals": {
      "url": "https://agentdeals.dev/mcp"
    }
  }
}

Quick Setup (.mcp.json)

Add AgentDeals to any project by dropping this .mcp.json in the project root:

{
  "mcpServers": {
    "agentdeals": {
      "url": "https://agentdeals.dev/mcp"
    }
  }
}

This works with Claude Code, Cursor, and other MCP-compatible clients that read .mcp.json.

Related MCP server: buyapi

Quick Start

Try these example queries

Find free database hosting:

Use the search_deals tool:
  query: "database"
  category: "Databases"

Returns Neon (0.5 GiB free Postgres), Supabase (500 MB), MongoDB Atlas (512 MB shared cluster), PlanetScale alternatives, and more.

What pricing changes happened recently?

Use the track_changes tool (no params for weekly digest, or filter):
  since: "2025-01-01"

Returns tracked changes like PlanetScale free tier removal, Heroku free dynos sunset, Render pricing restructure, and other shifts.

Show deals I qualify for as a YC company:

Use the search_deals tool:
  eligibility: "accelerator"

Returns AWS Activate, Google Cloud for Startups, Microsoft Founders Hub, Stripe Atlas credits, and 150+ other startup program deals.

Client Configuration

Each client supports both local stdio (via npx) and remote HTTP. Stdio is recommended for reliability and speed.

Claude Desktop

Add to claude_desktop_config.json:

Stdio (recommended):

{
  "mcpServers": {
    "agentdeals": {
      "command": "npx",
      "args": ["-y", "agentdeals"]
    }
  }
}

Remote HTTP:

{
  "mcpServers": {
    "agentdeals": {
      "url": "https://agentdeals.dev/mcp"
    }
  }
}

Config location:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

Cursor

Add to .cursor/mcp.json in your project or global config:

Stdio (recommended):

{
  "mcpServers": {
    "agentdeals": {
      "command": "npx",
      "args": ["-y", "agentdeals"]
    }
  }
}

Remote HTTP:

{
  "mcpServers": {
    "agentdeals": {
      "url": "https://agentdeals.dev/mcp"
    }
  }
}

VS Code (GitHub Copilot)

Add to .vscode/mcp.json in your workspace:

Stdio (recommended):

{
  "servers": {
    "agentdeals": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "agentdeals"]
    }
  }
}

Remote HTTP:

{
  "servers": {
    "agentdeals": {
      "type": "http",
      "url": "https://agentdeals.dev/mcp"
    }
  }
}

Claude Code

Add to .mcp.json in your project root:

Stdio (recommended):

{
  "mcpServers": {
    "agentdeals": {
      "command": "npx",
      "args": ["-y", "agentdeals"]
    }
  }
}

Remote HTTP:

{
  "mcpServers": {
    "agentdeals": {
      "type": "url",
      "url": "https://agentdeals.dev/mcp"
    }
  }
}

REST API

AgentDeals also provides a REST API for programmatic access without MCP.

Search offers

# Search by keyword
curl "https://agentdeals.dev/api/offers?q=database&limit=5"

# Filter by category
curl "https://agentdeals.dev/api/offers?category=Databases&limit=10"

# Paginate results
curl "https://agentdeals.dev/api/offers?limit=20&offset=40"

# Combine search + category
curl "https://agentdeals.dev/api/offers?q=postgres&category=Databases"

Response:

{
  "offers": [
    {
      "vendor": "Neon",
      "category": "Databases",
      "description": "Serverless Postgres with 0.5 GiB storage, 100 CU-hours/month compute on free tier",
      "tier": "Free",
      "url": "https://neon.com/pricing",
      "tags": ["database", "postgres", "serverless"]
    }
  ],
  "total": 142
}

curl "https://agentdeals.dev/api/categories"

Response:

{
  "categories": [
    { "name": "Cloud Hosting", "count": 45 },
    { "name": "Databases", "count": 38 },
    { "name": "Developer Tools", "count": 414 }
  ]
}

More endpoints

# Recently added offers
curl "https://agentdeals.dev/api/new?days=7"

# Pricing changes
curl "https://agentdeals.dev/api/changes?since=2025-01-01"

# Vendor details
curl "https://agentdeals.dev/api/details/Supabase?alternatives=true"

# Stack recommendation
curl "https://agentdeals.dev/api/stack?use_case=saas"

# Cost estimation
curl "https://agentdeals.dev/api/costs?services=Vercel,Supabase&scale=startup"

# Compare vendors
curl "https://agentdeals.dev/api/compare?a=Supabase&b=Neon"

# Vendor risk check
curl "https://agentdeals.dev/api/vendor-risk/Heroku"

# Stack audit
curl "https://agentdeals.dev/api/audit-stack?services=Vercel,Supabase,Clerk"

# Server stats
curl "https://agentdeals.dev/api/stats"

# Traffic attributed by client class (AI agent / crawler / browser), and web vs MCP
curl "https://agentdeals.dev/api/traffic"

# OpenAPI spec
curl "https://agentdeals.dev/api/openapi.json"

Available Tools

Tool	Description
`search_deals`	Find free tiers, startup credits, and developer deals for cloud infrastructure, databases, hosting, CI/CD, monitoring, auth, AI services, and more.
`plan_stack`	Plan a technology stack with cost-optimized infrastructure choices. Recommends free-tier services, estimates costs, or audits existing stacks.
`compare_vendors`	Compare developer tools side by side — free tier limits, pricing tiers, and recent pricing changes.
`track_changes`	Track recent pricing changes across developer tools — free tier removals, limit reductions, new free tiers, and expirations.

search_deals

Parameters:

query (string, optional) — Keyword search (vendor names, descriptions, tags)
category (string, optional) — Filter by category. Pass "list" to get all categories with counts.
vendor (string, optional) — Get full details for a specific vendor (fuzzy match). Returns alternatives.
eligibility (string, optional) — Filter: public, accelerator, oss, student, fintech, geographic, enterprise
sort (string, optional) — Sort: vendor (A-Z), category, newest (recently verified first)
since (string, optional) — ISO date. Only return deals verified/added after this date.
limit (number, optional) — Max results (default: 20)
offset (number, optional) — Pagination offset

plan_stack

Parameters:

mode (string, required) — recommend, estimate, or audit
use_case (string, optional) — What you're building (for recommend mode)
services (array, optional) — Current vendor names (for estimate/audit mode)
scale (string, optional) — hobby, startup, growth (for estimate mode, default: hobby)
requirements (array, optional) — Specific infra needs (for recommend mode)

compare_vendors

Parameters:

vendors (array, required) — 1 or 2 vendor names. 1 = risk check, 2 = side-by-side comparison.
include_risk (boolean, optional) — Include risk assessment (default: true)

track_changes

Parameters:

since (string, optional) — ISO date. Default: 7 days ago.
change_type (string, optional) — Filter: free_tier_removed, limits_reduced, limits_increased, new_free_tier, pricing_restructured, etc.
vendor (string, optional) — Filter to one vendor
vendors (string, optional) — Comma-separated vendor names to filter
include_expiring (boolean, optional) — Include upcoming expirations (default: true)
lookahead_days (number, optional) — Days to look ahead for expirations (default: 30)

Use Cases

Agent-assisted infrastructure selection

When your AI agent recommends infrastructure, it's usually working from training data — not current pricing. By connecting AgentDeals, the agent can:

Compare free tiers: "I'm evaluating Supabase vs Neon for a side project" — use compare_vendors with both names
Check eligibility: "We're a YC W24 company, what credits can we get?" — use search_deals with eligibility: "accelerator"
Verify before recommending: Use track_changes to ensure the free tier hasn't been removed or reduced

Monitoring deal changes

Track pricing shifts that affect your stack:

Weekly digest: Call track_changes with no params for a curated summary
Filter by vendor: Call track_changes with vendor: "Vercel" to see if Vercel's pricing has changed
Filter by type: Call track_changes with change_type: "free_tier_removed" to see which vendors have eliminated free tiers

Development

npm install          # Install dependencies
npm run build        # Compile TypeScript
npm test             # Run tests (266 passing)
npm run serve        # Run HTTP server (port 3000)
npm start            # Run stdio server

Local development with stdio

npm start

Local development with HTTP

npm run serve
# Server starts at http://localhost:3000
# MCP endpoint: http://localhost:3000/mcp
# Landing page: http://localhost:3000/

Environment Variables

Variable	Description	Default
`PORT`	HTTP server port	`3000`
`BASE_URL`	Base URL for canonical links, OG tags, sitemaps, and feeds	`https://agentdeals.dev`
`GOOGLE_SITE_VERIFICATION`	Google Search Console verification code	(none)

Stats

1,525 vendor offers across 54 categories
57 tracked pricing changes
4 MCP tools + 6 prompt templates + 17 REST API endpoints
266 passing tests
Data verified as of 2026-03-14

Registries

License

MIT

Available Tools

4 tools

compare_vendorsAInspect

Compare 2 vendors side-by-side or check a single vendor's pricing risk. Returns free tier limits, risk levels, pricing history, and alternatives.

ParametersJSON Schema

Name	Required	Description	Default
`vendors`	Yes	1 or 2 vendor names. 1 vendor = risk check. 2 vendors = side-by-side comparison.
`include_risk`	No	Include risk assessment (default: true)

TDQS

A4.4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: the tool returns 'free tier limits, risk levels, pricing history, and alternatives', which helps understand output. However, it lacks details on permissions, rate limits, or error handling, leaving some behavioral aspects unclear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded and concise, with two sentences that efficiently convey purpose, usage, and output. Every sentence earns its place by providing essential information without redundancy or unnecessary details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (2 parameters, no output schema, no annotations), the description is mostly complete: it covers purpose, usage, and output. However, it lacks details on error cases or limitations (e.g., vendor name formats), which could enhance completeness for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds value by explaining the semantic meaning of the 'vendors' parameter: '1 or 2 vendor names' with implications for functionality (risk check vs. comparison), enhancing understanding beyond the schema's technical description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with specific verbs ('compare side-by-side', 'check pricing risk') and resources ('vendors'), distinguishing it from siblings like 'plan_stack', 'search_deals', and 'track_changes' by focusing on vendor comparison and risk assessment rather than planning, searching, or tracking.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states when to use the tool: '1 vendor = risk check' and '2 vendors = side-by-side comparison', providing clear guidance on usage scenarios without needing to reference alternatives, as the context is self-contained and distinct from sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

plan_stackAInspect

Get stack recommendations, cost estimates, or a full infrastructure audit. Describe what you're building to get a free-tier stack, or pass your current services to estimate costs and find risks.

ParametersJSON Schema

Name	Required	Description
`mode`	Yes	recommend: free-tier stack for a use case. estimate: cost analysis at scale. audit: risk + cost + gap analysis.
`use_case`	No	What you're building (for recommend mode, e.g. 'Next.js SaaS app')
`services`	No	Current vendor names (for estimate/audit mode, e.g. ['Vercel', 'Supabase'])
`scale`	No	Scale for cost estimation (default: hobby)
`requirements`	No	Specific infra needs for recommend mode (e.g. ['database', 'auth', 'email'])

TDQS

A3.9/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool provides 'free-tier stack' recommendations and 'risk + cost + gap analysis' in audit mode, which adds useful context about what the tool delivers. However, it doesn't disclose important behavioral traits like rate limits, authentication requirements, or what format the output takes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is efficiently structured in two sentences that each serve distinct purposes: the first states the core functionality, the second provides usage guidance. Every word earns its place with no redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 5 parameters, no annotations, and no output schema, the description provides adequate but incomplete context. It explains what the tool does and gives basic usage guidance, but doesn't cover important aspects like output format, error conditions, or detailed behavioral characteristics that would be needed for optimal agent use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds some context about parameter usage ('Describe what you're building' relates to use_case, 'pass your current services' relates to services), but doesn't provide significant additional semantic meaning beyond what's in the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with specific verbs ('Get stack recommendations, cost estimates, or a full infrastructure audit') and distinguishes it from siblings by focusing on planning/analysis rather than comparison, searching, or tracking. It explains what the tool does in concrete terms.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use different modes ('Describe what you're building to get a free-tier stack, or pass your current services to estimate costs and find risks'), but doesn't explicitly mention when NOT to use it or name specific alternatives among sibling tools. The guidance is helpful but not exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_dealsBInspect

Find free tiers, credits, and discounts for 1,500+ developer tools. Search by keyword, browse categories, or get full vendor details with alternatives. Covers AWS, Vercel, Supabase, Cloudflare, and more.

ParametersJSON Schema

Name	Required	Description
`query`	No	Keyword search (vendor names, descriptions, tags)
`category`	No	Filter by category. Pass "list" to get all categories with counts.
`vendor`	No	Get full details for a specific vendor (fuzzy match). Returns alternatives in the same category.
`eligibility`	No	Filter by eligibility type
`sort`	No	Sort: vendor (A-Z), category, newest (recently verified first)
`since`	No	ISO date (YYYY-MM-DD). Only return deals verified/added after this date.
`limit`	No	Max results (default: 20)
`offset`	No	Pagination offset (default: 0)

TDQS

B3.3/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It mentions the scope ('1,500+ developer tools') and examples ('AWS, Vercel, Supabase, Cloudflare, and more'), but lacks details on behavioral traits such as rate limits, authentication needs, response format, or pagination behavior. It does not contradict annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded with the core purpose in the first sentence. The second sentence adds usage modes efficiently, and the third provides scope examples. There is no wasted text, though it could be slightly more structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (8 parameters, no annotations, no output schema), the description is incomplete. It lacks details on behavioral traits, response format, and error handling, which are crucial for a search tool with multiple filtering options. The description does not compensate for the absence of annotations or output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents all 8 parameters. The description adds minimal semantic context by mentioning 'search by keyword, browse categories, or get full vendor details with alternatives,' which loosely maps to the query, category, and vendor parameters, but does not provide additional meaning beyond what the schema already specifies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Find free tiers, credits, and discounts for 1,500+ developer tools.' It specifies the resource (developer tools deals) and the action (find/search), and distinguishes itself from siblings by focusing on discovery rather than comparison, planning, or tracking.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage through phrases like 'Search by keyword, browse categories, or get full vendor details with alternatives,' but does not explicitly state when to use this tool versus its siblings (compare_vendors, plan_stack, track_changes). No exclusions or alternatives are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

track_changesAInspect

Track developer tool pricing changes, upcoming expirations, and new deals. With no params, returns a weekly digest. Filter by vendor, change type, or date range.

ParametersJSON Schema

Name	Required	Description
`since`	No	ISO date (YYYY-MM-DD). Default: 7 days ago.
`change_type`	No	Filter by type of change
`vendor`	No	Filter to one vendor (case-insensitive)
`vendors`	No	Comma-separated vendor names to filter (e.g. 'Vercel,Supabase')
`include_expiring`	No	Include upcoming expirations (default: true)
`lookahead_days`	No	Days to look ahead for expirations (default: 30)

TDQS

A3.9/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the tool's function and default behaviors (e.g., weekly digest with no params, default inclusion of expirations implied by parameters), but lacks details on permissions, rate limits, or error handling, which are important for a tool with multiple parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose, followed by usage notes, in two efficient sentences with zero wasted words. Every sentence earns its place by adding actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (6 parameters, no annotations, no output schema), the description is adequate but incomplete. It covers purpose and basic usage but lacks details on output format, error cases, or advanced behavioral traits, which are needed for full contextual understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds minimal value by mentioning filtering by 'vendor, change type, or date range', which aligns with parameters but doesn't provide additional semantics beyond the schema. Baseline 3 is appropriate given high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with specific verbs ('track', 'returns') and resources ('developer tool pricing changes, upcoming expirations, and new deals'). It distinguishes from siblings by focusing on tracking changes rather than comparing vendors, planning stacks, or searching deals.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use the tool ('with no params, returns a weekly digest') and how to filter results. However, it does not explicitly state when not to use it or name specific alternatives among sibling tools, keeping it from a perfect score.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

4 tool updatesv0.2.0Mar 17, 2026
- First observedcompare_vendors
- First observedplan_stack
- First observedsearch_deals
- First observedtrack_changes

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.1/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: compare_vendors focuses on vendor comparison and risk assessment, plan_stack provides infrastructure recommendations and cost estimation, search_deals finds discounts and free tiers, and track_changes monitors pricing updates. There is no overlap in functionality, making tool selection unambiguous.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (compare_vendors, plan_stack, search_deals, track_changes) with clear, action-oriented verbs. The naming is uniform and predictable across all four tools, enhancing readability and usability.

Tool Count5/5

With 4 tools, the server is well-scoped for its purpose of helping developers with vendor selection, cost planning, deal discovery, and change tracking. Each tool earns its place by covering a distinct aspect of the domain without being too sparse or overwhelming.

Completeness5/5

The tool set provides complete coverage for the domain of developer tool pricing and infrastructure planning. It includes comparison, planning, search, and tracking functionalities, offering a full lifecycle from discovery to monitoring with no obvious gaps or dead ends.

Maintenance

ActivityActive

ResponsivenessResponsive

Resources

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Agentic Platform A
io.github.andysalvo
Free MCP tools: the only MCP linter, health checks, cost estimation, and trust evaluation.
Developer Tools Monitoring Observability
31
ComparEdge Pricing A
io.github.comparedge
Verified SaaS, AI, and LLM pricing for 490+ tools: plans, hidden costs, TCO, and alternatives.
AI & Machine Learning Research & Data
922
Utility Matrix A
io.github.helphub369
Free browser-based calculators and analyzers for cloud cost, DevOps, security, and data governance.
Cloud Platforms Developer Tools Security
2
Cralo
ai.cralo
Pay-per-use tool marketplace for AI agents. Search, price-check, and call APIs via MCP.
Agent Orchestration Developer Tools
1

Related MCP Servers

atom-mcp-server
AI & Machine Learning Search Finance
A7OM-AI
A
license
A
quality
C
maintenance
Global price benchmarking for AI inference across 2,600+ SKUs from 47 vendors. Query live pricing, market indexes, and model specs via 8 tools. Free tier available.
Updated 2 months ago (2026-06-23 07:47 UTC)
8
103
MIT
buyapi
Developer Tools Search
TheSnakeFang
A
license
Not graded
quality
A
maintenance
Unbiased vendor intelligence MCP server that helps AI agents and developers make informed infrastructure decisions by providing current, structured, neutral vendor comparisons and recommendations.
Updated 13 days ago (2026-08-24 16:07 UTC)
96
1
MIT
Cloud Cost MCP
Cloud Platforms Finance
jasonwilbur
A
license
A
quality
D
maintenance
Multi-cloud pricing comparison MCP server that enables natural language queries to compare compute, storage, egress, and Kubernetes costs across AWS, Azure, GCP, and OCI.
Updated 3 months ago (2026-06-03 22:48 UTC)
31
68
5
Apache 2.0
CloudCost MCP Server
Cloud Platforms Finance
JadenRazo
A
license
Not graded
quality
A
maintenance
Enables AI agents to parse multi-cloud infrastructure-as-code files, query real-time pricing from AWS, Azure, and GCP, and generate cost estimates and comparison reports.
Updated a day ago (2026-09-04 18:57 UTC)
39
MIT

Appeared in Searches

A server for finding free and popular resources

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/robhunter/agentdeals'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

AgentDeals

Install

Option A: Claude Code Plugin (one-click)

Option B: Claude Desktop Extension (one-click)

Option C: npx (local stdio)

Option D: Remote HTTP

Quick Setup (.mcp.json)

Quick Start

Try these example queries

Client Configuration

Claude Desktop

Cursor

VS Code (GitHub Copilot)

Claude Code

REST API

Search offers

List categories

More endpoints

Available Tools

search_deals

plan_stack

compare_vendors

track_changes

Use Cases

Agent-assisted infrastructure selection

Monitoring deal changes

Categories

Development

Local development with stdio

Local development with HTTP

Environment Variables

Stats

Registries

License

Available Tools

Tool Schema Changelog

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

Appeared in Searches

Latest Blog Posts

MCP directory API