---
title: Toolshelf.space developer resources
description: Read-only API, MCP, and WebMCP interfaces for the source-backed Toolshelf catalog.
canonical: https://www.toolshelf.space/developers
version: 1.0.0
stability: public-beta
---

# Toolshelf.space developer resources

Toolshelf exposes a small read-only catalog API and a remote Model Context Protocol server for people and AI agents that need source-backed digital tool discovery. No account or API key is required. Public list reads are bounded and cached so clients can use the catalog without creating avoidable Neon or Vercel usage.

## Public catalog API

The OpenAPI 3.1 contract is published at [openapi.json](https://www.toolshelf.space/openapi.json). It documents catalog search, lookup by slug, the compact command index, and source-backed stack recommendations. Responses are JSON. Clients should respect response cache headers, avoid bulk mirroring, and use the sitemap or RSS feed to find changed records.

## Remote MCP server

Connect to [the Toolshelf MCP endpoint](https://www.toolshelf.space/mcp) with Streamable HTTP. Its manifest uses the official MCP Registry server.json format and is published at [server.json](https://www.toolshelf.space/server.json). Remote connection metadata is also available through the [MCP server card](https://www.toolshelf.space/mcp/server-card) and domain [AI Catalog](https://www.toolshelf.space/.well-known/ai-catalog.json). The server offers read-only tools for catalog search, exact tool lookup, and catalog overview. Results include canonical Toolshelf detail URLs so agents can cite and inspect the public evidence trail.

## In-page WebMCP

Supported browsers can discover three read-only tools while a person is browsing Toolshelf: `search_toolshelf`, `open_toolshelf_tool`, and `compare_toolshelf_tools`. WebMCP is progressive enhancement. The website works normally when `document.modelContext` is unavailable.

## API stability

The public API and agent interfaces are version 1.0.0 and public beta. Backward-compatible fields may be added without a version change. A breaking contract change will use a new major version. Any scheduled endpoint retirement will be documented here and in OpenAPI before it happens, with standard `Deprecation` and `Sunset` response headers on the affected live endpoint.

## Evidence limits

A missing fact means Toolshelf has not verified it. It is not a negative claim about the product. Toolshelf is not the official source for current pricing, legal terms, security guarantees, or product availability. Check those details on the product's official website before acting on them.

- [OpenAPI specification](https://www.toolshelf.space/openapi.json)
- [MCP server manifest](https://www.toolshelf.space/server.json)
- [Agent index](https://www.toolshelf.space/llms.txt)
- [Catalog coverage](https://www.toolshelf.space/coverage)