Aerostack

AI Marketplace — Browse MCP Servers, Skills & Agents

Browse the MCP Registry

MCP Servers

AI Skills

Agent Templates

Search the MCP marketplace and AI marketplace: discover MCP servers, skills, agent templates, and edge functions, then install them into your workspace in one click.

Nothing found

No content published yet.

Frequently asked questions

What is the Aerostack MCP marketplace and what can I find here? +

The Aerostack Explore page is the MCP marketplace — and a broader AI marketplace — where you browse, search, and install everything the community has published: 250+ MCP servers, AI skills, agent templates, and edge functions. Each item has a detail page with a description, tool list, author, and install count. You can filter by type — MCP server, skill, function, agent — and by category such as database, payments, auth, or AI. Every item in the catalog is installable into an Aerostack workspace in one click, and once installed it is immediately accessible to any AI client that supports the Model Context Protocol, including Claude, Cursor, and custom agents. Think of it as a searchable registry for the entire MCP ecosystem, not just Aerostack-native tooling.

What is an MCP server and why does the MCP registry matter for AI agents? +

An MCP server is a backend service that exposes a set of callable tools to AI agents via the Model Context Protocol — an open standard for connecting language models to external systems. Instead of hardcoding API integrations into every agent, you point your AI client at an MCP server URL and it discovers the available tools automatically. The Aerostack MCP registry matters because it is a curated, community-built directory of ready-to-use MCP servers covering databases, payment processors, authentication providers, AI utilities, and more. Rather than building a GitHub or Stripe integration from scratch, you find it in the registry, install it into your workspace, and your agent gains those tools in under a minute. The catalog grows continuously as the community publishes new servers.

How do I install an MCP server from the marketplace into my AI agent setup? +

Open any listing in Explore and click Install. The server is added to your active Aerostack workspace immediately — no config files to edit, no credentials to wire manually at this step. Your workspace is a single authenticated URL that composes all your installed MCP servers behind one endpoint. Copy that URL into your AI client's MCP config field: in Claude desktop add it as a remote server, in Cursor paste it into the MCP settings, or pass it to any agent that speaks the Model Context Protocol. From that point on every tool from every installed server is available to your agent in a single connection. If you need to share a server privately across a team without listing it publicly, that flow lives under the Private MCP section of your workspace.

What is the difference between MCP servers, skills, agent templates, and edge functions in the catalog? +

These four types sit at different layers of the agent stack. An MCP server exposes tools — discrete callable actions like query-database or send-email — to any AI agent via the protocol. A skill is a higher-level, reusable AI capability bundled with its own prompt logic; skills are designed to be composed into agents rather than called directly by a user. An agent template is a pre-built autonomous workflow that combines an LLM reasoning loop, tool calls, and optionally human-approval steps — install it and you have a working agent you can customize. An edge function is plain backend logic deployed on Cloudflare Workers: no agent loop, no MCP protocol, just fast serverless code with database, cache, and AI bindings built in. Browse MCP servers when you want tools; browse templates when you want a complete agent to run.

How do I choose between similar MCP servers, or decide when to publish my own? +

When two servers cover the same integration, check install count and author-verified status first — a higher install count usually means more real-world testing. Read the tool list on each detail page: one server may expose five tools while another exposes twenty with more granular control. If a server is authored by the service itself or a verified Aerostack partner, it is likely to stay current with API changes. Publish your own when no existing server covers your use case, when you need tools scoped to internal systems that should never be public, or when you want to share a server you have built with the wider community. If your server is for internal use only, publish it as private; it will appear in your workspace but not in the public catalog. A private server can also be shared with specific team members without being listed here.

Are items in the AI marketplace free, and how does the free tier work? +

Installing items from the catalog is free. The Aerostack free tier includes 500,000 AI tokens per month on Cloudflare's edge infrastructure, which covers a substantial volume of agent tool calls and edge function executions before any paid usage applies. Community-published MCP servers, skills, and agent templates have no install fee; you pay only for compute and token usage as your agents run. Edge functions run on Cloudflare Workers, which means global low-latency execution with no servers to manage. If you bring your own model API key — Anthropic, OpenAI, or any supported provider — that usage is billed directly by the model provider and does not count against the platform token allowance.

Can I publish my own MCP server or skill to the marketplace? +

Yes. Any Aerostack user can publish MCP servers, skills, edge functions, and agent templates to the public catalog. Build and test your server in a workspace, then submit it for listing — you choose whether it is public (visible to everyone in Explore) or private (visible only to you or your team). Public listings put your work in front of the whole community, and Aerostack handles hosting and distribution. Private listings are useful for internal tooling you want to host and version on the platform without exposing it to the community. The listing page lets you write a description, specify categories, and document the tools your server exposes so other users can evaluate it before installing. Quality and community trust build over time through install counts and reviews, which is why publishing early — even at version one — is worth doing.

When should I NOT just install from the marketplace — and build or host privately instead? +

The marketplace is the right starting point for general integrations — commodity tools like database access, payment APIs, or authentication that many agents need. Reach for a private or custom path when your tooling touches internal systems that should never be reachable from a public server, when you need proprietary business logic baked into the tools rather than exposed as a generic API wrapper, or when you require strict SLA control over the server itself. For those cases, build the server locally and publish it as a private listing under your workspace; the Private MCP section of Aerostack handles hosting, secrets injection, and access control. Also consider building your own if existing catalog servers for a given integration are outdated or missing key tools — publishing a better version benefits both you and the community.