Turn any OpenAPI or GraphQL API into tools for your AI agents

What is an API connector?

An OpenAPI document lists a REST API's operations, their parameters and the shape of each request. A GraphQL API describes its own schema when asked, through introspection. An API connector reads that description and turns each operation into a tool, so an agent can call the API without anyone writing code for it.

integrations.sh is an open source registry of the ways agents can reach a service: MCP servers, OpenAPI descriptions, GraphQL endpoints and command-line tools, grouped by domain, with notes on how each signs in. Services list themselves by publishing a /.well-known/integrations.json file.

What bots can do with API connectors in SFCrew

• Use a REST API from its OpenAPI description. Paste the document's URL, in JSON or YAML, and SFCrew turns every operation with an operationId into a tool, up to 100 per API.
• Use a GraphQL API from its endpoint. SFCrew introspects the schema and turns queries and mutations into tools, up to 100 per API.
• Authenticate with a bearer token or an API key header. The key is encrypted, never sent to the model, and removed from what the API sends back.
• Find an API by domain. When the operator points INTEGRATIONS_CATALOG_URL at an integrations.sh-compatible catalog, Search by domain adds a service's OpenAPI description or MCP server with the address and sign-in method filled in.
• Read without asking. A GET operation or a GraphQL query counts as reading, so in Ask mode it usually runs without a card. Writes ask first, under your approval settings.
• Share it. Every bot in the spaces you choose can use the connector. Past 20 tools, a bot searches for the operations it needs instead of loading them all.

When to choose API connectors

Choose an API connector when an app has a documented API and an API key, but no MCP server and no integration in the catalog. That covers many smaller SaaS tools and your company's own APIs, and needs no other service.

If the app publishes an MCP server, use that instead: its tools are written for agents and it can sign you in with OAuth. If the app needs an OAuth sign-in and has no MCP server, Composio or Pipedream handle that for you. The comparison covers all four.

Limits and security

• There is no OAuth sign-in for API connectors. Use an API key or a long-lived token; a token that expires has to be replaced by hand.
• An OpenAPI document must list a server URL, give operations an operationId and be under 2 MB. Only the first 100 operations are imported, and request bodies are JSON.
• A GraphQL API must allow introspection. Larger schemas are cut to 100 operations, split between queries and mutations.
• APIs must be at public addresses. Localhost and private networks are refused unless the operator sets MCP_ALLOW_PRIVATE_ENDPOINT=true on the API and worker, which allows them for every user. Cloud metadata addresses stay blocked.
• The Settings form sends a key as a bearer token or a header. Connectors installed through SFCrew's API can also put it in the URL as a query parameter, so avoid that for sensitive keys. Redirects aren't followed, each call has 30 seconds and responses over 1 MB are cut short.

How to set it up

Anyone with an account can add an API connector, on SFCrew Cloud or a self-hosted server. The catalog search is an optional setting for the admin of a self-hosted SFCrew. See Connect apps and the tools and integrations guide.

1. Find the API's OpenAPI document or GraphQL endpoint in its developer docs or on integrations.sh.
2. Open Integrations from Connect apps at the bottom of the sidebar, choose +, then OpenAPI or GraphQL.
3. Paste the URL, choose No auth, Bearer token or API key header, enter the key, and choose Verify and add.
4. Ask a bot to use the API, and approve any call that changes something.
5. Optionally, an admin sets INTEGRATIONS_CATALOG_URL on the API to https://integrations.sh or a compatible mirror to turn on Search by domain.