Three ways to connect
Managed connectors
BoostGPT builds and maintains these. Enter one credential; when a vendor changes an endpoint, that is ours
to fix.
Remote MCP servers
The vendor runs the server. You sign in and approve access — there is no key to paste and no app to register.
Bring your own
An OpenAPI specification, a Postman collection, or the address of any MCP server.
Grouped by what they are for
Both catalogues are grouped by the loop BoostGPT works in, rather than alphabetically:
The featured entries in each group are the ones that change what the Site says or what the Widget answers.
Everything else is one click away under Show more.
Connecting one
1
Connect it once, for the workspace
Connectors in the dashboard. A credential you enter is checked against the vendor before anything is
saved, and a server that signs in is saved only once the sign-in succeeds — so a connection that exists is
one that works.
2
Give it to the agents that need it
Each agent has its own Connectors tab. A connection is shared, so adding it to a second agent asks for
no credential; switching a tool off for one agent does not touch another.
3
Decide what needs asking first
Every connection carries an approval setting — every time, never, or per tool. An agent can always ask more
often than you set, never less.
Two connectors need no setup at all: Serper for web search and Pexels for photography are funded by
BoostGPT and attached to a new agent automatically. Your own key always takes precedence over ours.