Steroid Kit logo

Steroid_Kit

Steroid MCP›Server Catalog

Server Catalog

The catalog snapshot contains 241 registry entries and 3,188 tool definitions. Twelve entries have no tool definitions; 229 generated AP pieces cover the tool-bearing entries. Listing, search indexing, generated blocks and tested runtime availability are distinct.

Browsing the Catalog

Log in at steroidkit.com/catalog. There is no steroid catalog search terminal command. You do not need to browse the catalog before using a server — natural-language queries to search_tools are usually sufficient. The catalog is useful for discovering what is available, understanding auth requirements before a session, and verifying tool names.

Server catalog — browse catalog
  • Each catalog entry shows the server identifier, a short description, and the total number of tools it exposes
  • Search, authentication filtering and pagination help narrow the registry.
  • Server details show setup/configuration and tool guidance; this is not an in-browser tool-execution session.
  • Use the server-request workflow for a missing integration. Catalog counts are a checkout snapshot, not a live availability SLA.

Server Categories

CategoryExample catalog key
Communicationslack
Developer toolsgithub-official
Databasespostgres
Web searchbrave
Knowledge/productivitynotion

Auth Types

The current web classification is 84 none, 157 API-key and zero OAuth entries. Inspect server metadata for exact secrets and configuration; a none-classified server can still need configuration. AP's upstream OAuth integrations are a different surface from Steroid gateway onboarding.

No secret declared (84 entries)

No declared secret does not mean no setup: server configuration, backend availability and required tool arguments still matter. Do not infer that a public search service never needs an API key.

API-key/secret setup (157 entries)

The most common auth type. The user provides a long-lived API key once; Steroid stores it encrypted in the encrypted local store and sends needed credentials to execution services. If a key is missing when run_toolis called, Steroid pauses execution and renders an elicitation prompt in the IDE, asking the user to paste the key. Subsequent calls reuse the stored credential automatically.

Continue Reading

→ Marketplace Search/Run→ Credential Management→ Hallucination Prevention→ Steroid MCP — Overview

On this page