MCP Registry

The Aerostack Registry is an MCP server that lets any AI agent discover and use 100+ MCP servers without manual configuration. One URL, semantic search, full tool documentation — your agent finds what it needs on its own.

Connect the Registry

Add this to your MCP client config:

{
  "mcpServers": {
    "aerostack-registry": {
      "url": "https://mcp.aerostack.dev",
      "transport": "streamable-http"
    }
  }
}

{
  "mcpServers": {
    "aerostack-registry": {
      "url": "https://mcp.aerostack.dev",
      "transport": "streamable-http"
    }
  }
}

Available Tools

The registry exposes 3 tools:

search_registry

Semantic search across all MCPs, functions, skills, and agents in the Aerostack marketplace.

Example: Your agent asks “I need to send notifications to a Slack channel”

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "search_registry",
    "arguments": {
      "query": "send slack message",
      "type": "mcp",
      "limit": 3
    }
  }
}

Returns ranked results with name, description, tool count, and a call_hint showing exactly how to invoke each one.

get_tool_schema

Get full parameter documentation for any MCP server or function — input schemas, descriptions, capability manifest.

Returns the complete tool list with inputSchema for every parameter, plus the AI-generated capability manifest (best for, not suitable for, pairs with).

call_function

Execute any published community function directly through the registry.

How It Works

Your AI Agent
    │
    ├─ "I need to send a Slack message and create a Stripe invoice"
    │
    ▼
search_registry("send slack message")     → mcp-slack (8 tools)
search_registry("create stripe invoice")  → mcp-stripe (5 tools)
    │
    ▼
get_tool_schema("mcp-slack")    → post_message: channel, text, thread_ts
get_tool_schema("mcp-stripe")   → create_invoice: customer, amount, currency
    │
    ▼
Agent now knows exactly which tools exist and how to call them

From Discovery to Execution

The registry helps agents discover tools. To actually call them, connect a workspace:

{
  "mcpServers": {
    "my-workspace": {
      "url": "https://mcp.aerostack.dev/s/YOUR_USERNAME/YOUR_WORKSPACE",
      "headers": {
        "Authorization": "Bearer mwt_YOUR_TOKEN"
      }
    }
  }
}

Security

• Discovery is open — search_registry and get_tool_schema require no auth
• Execution is gated — calling tools requires a workspace token
• Per-tool access control — enable/disable individual tools per workspace
• Secrets encrypted — API keys are AES-GCM encrypted, injected as headers at runtime, never exposed
• Rate limited — 25 requests/min per IP for discovery

See Agent Security for the full access control breakdown.

What’s in the Catalog

100+ servers across categories:

Browse the full catalog at aerostack.dev/mcp.