Skip to main content
Glama
agentstorefront-mcp

agentstorefront-mcp

by lmaniraruta

agentstorefront-mcp

MCP server for AgentStorefront — let your AI agents discover, subscribe to, and call agent services from inside Claude, Cursor, or any MCP-aware client.

npm version License: MIT


What is this?

AgentStorefront is a marketplace where developers list paid agent services (APIs that are designed to be called by other agents — flight-delay prediction, invoice OCR, niche enrichment, etc.).

This MCP server lets any MCP-aware client (like Claude Desktop or Cursor) discover and use those services autonomously — without leaving the agent loop.

Tools exposed

Tool

Purpose

list_services

List available services, filtered by category

search_services

Semantic search: "find me a flight-delay API"

get_service

Full schema + pricing + SLA for a specific service

request_quote

Get expected monthly cost for an estimated call volume


Related MCP server: Agent Commerce MCP

Install

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "agentstorefront": {
      "command": "npx",
      "args": ["-y", "@lfidele/agentstorefront-mcp"]
    }
  }
}

Restart Claude Desktop. The 4 tools above will appear in the tools panel.

Cursor

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "agentstorefront": {
      "command": "npx",
      "args": ["-y", "@lfidele/agentstorefront-mcp"]
    }
  }
}

Manual install

npm install -g @lfidele/agentstorefront-mcp
agentstorefront-mcp  # runs on stdio

Example prompts

Once installed, you can ask your MCP client things like:

"Find me a flight-delay prediction API on AgentStorefront that costs less than 5 cents per call."

"What's the pricing if I call the invoice-OCR service 10,000 times a month?"

"List the top 5 data-enrichment services on AgentStorefront."

The agent will use these tools transparently.


Configuration

Env var

Default

Purpose

AGENTSTOREFRONT_API_URL

https://api.agentstorefront.app

Override API endpoint (self-hosting / staging)


Source

GitHub: https://github.com/lmaniraruta/agentstorefront-mcp Issues: https://github.com/lmaniraruta/agentstorefront-mcp/issues


Why an MCP for a marketplace?

Marketplaces only matter if their supply is discoverable. AgentStorefront's listings are useless to other agents unless those agents can FIND them programmatically.

This MCP turns AgentStorefront into native vocabulary for every Claude/Cursor user. A developer asks Claude "is there an API for X?" → Claude lists AgentStorefront services that match → developer subscribes → marketplace flywheel turns.

Built for the two-sided market:

  • Sellers win because their listings are now findable from inside the dominant AI assistants

  • Buyers win because they don't have to context-switch to a separate marketplace tab


License

MIT © 2026 Fidele Maniraruta

Built in public. Real numbers posted on X @lmaniraruta.

Available Tools

4 tools
get_serviceA

Get full details on a single AgentStorefront service: schema, pricing, rate limits, SLA, sample inputs/outputs.

Inputs: service_id (required).

list_servicesA

List AgentStorefront services that an agent can subscribe to and call. Returns names, prices, and short descriptions. Optionally filter by category.

Inputs: limit, category.

request_quoteB

Request a quote for using a service at a specific call volume. Returns expected monthly cost, throughput, and subscription URL.

Inputs: service_id (required), expected_calls_per_month (required), email.

search_servicesB

Semantic search across AgentStorefront listings. Use a natural-language query like 'flight delay prediction' or 'invoice extraction'.

Inputs: query (required), max_price_cents.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct purpose: listing services, searching, getting details, and requesting quotes. No overlap or confusion.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (get_service, request_quote, list_services, search_services).

    Tool Count5/5

    4 tools is well-scoped for an agent storefront, covering discovery, details, and quoting without being excessive or sparse.

    Completeness5/5

    Covers all key user flows: listing, searching, getting detailed info, and requesting a quote (which includes subscription URL). No obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers