A registry of 5,700+ integration specs from Rhys Sullivan — the same builder behind Executor. Every service normalized into MCP, OpenAPI, GraphQL, and CLI form, each surface leading with a grounded, cited credential guide agents can act on.
If Executor is the gateway that lets an agent call thousands of tools through one typed SDK, integrations.sh is the catalog of what's out there to connect in the first place — the same author, one layer up the stack. Tagline: "Every integration, in every format agents speak."
Repo: UsefulSoftwareCo/integrationsdotsh · MIT © Rhys Sullivan.
A registry mapping 3,200+ services to every integration surface they expose, grouped by protocol:
Query a domain (Slack, Notion, Stripe, Figma, Salesforce…) and get back every publicly-reachable surface it has.
Finding an endpoint is easy. Figuring out which credential type it wants, how to obtain it, and where to put it is the part that eats research time. integrations.sh leads every surface with a grounded, cited credential guide instead of a generic docs link:
detected (machine-verifiable) or discovered (from docs)/api.json for the full catalog, /api/{domain}/surface for a structured surface doc/mcp exposing detect and discover tools/openapi.jsonIt's skills.sh but for the integration layer: a discovery index that's itself machine-readable, so an agent can go from "connect to X" to a credential-complete surface spec without a human doing the research. Pairs naturally with Executor — discover here, call there.