integrations.sh
5,758 machine-readable integration specs — MCP, OpenAPI, GraphQL, CLI — across 3,230 domains
integrations.sh is an open registry that maps, for each of 3,230 service domains, which integration surfaces exist and what credentials each one needs. The catalogue holds 5,758 specs: 3,806 OpenAPI/REST, 1,274 MCP servers, 565 CLIs and 113 GraphQL endpoints, each with a domain, category, icon and source URL. The whole thing is downloadable as one JSON file at /api.json, with per-domain detect/discover/surface endpoints and a hosted MCP server on top. It is aimed at agents that must answer 'can I talk to this service, and how do I authenticate' without a human in the loop.
Pull https://integrations.sh/api.json once and cache it — it is a single flat array with kind, domain, categories and source URL per record, which is far cheaper than web-searching 'does X have an MCP server'. Use it as a discovery index only: the entries point at a vendor's own docs page and the descriptions are LLM-written, so verify the auth flow at the linked source before you generate credential code. Treat the schema as unstable (the repo self-labels v0.0.1) and the snapshot as dated — the copy verified here was generated 2026-07-08.
Why it is here. The cheapest single artefact for answering 'what can my agent connect to and how' — a rare case of a directory built for machines first.
- one-file /api.json catalogue
- 1,274 MCP servers indexed
- 3,806 OpenAPI specs
- hosted MCP server with detect and discover tools
- MIT-licensed dataset
Verified 2026-08-15. HTTP 200. https://integrations.sh/, https://integrations.sh/api.json (downloaded, 5,758 records counted and bucketed by kind and category), https://github.com/UsefulSoftwareCo/integrations, GitHub API for stars/licence/last push. Note: GET https://integrations.sh/mcp returned 404 — the MCP endpoint is documented in the repo README but was not exercised.
