Connectors

Connect Model Context Protocol servers to BullSequana AI and reach them through the MCP Gateway.

Agentic Friendly

A Connector is a Model Context Protocol (MCP) server that BullSequana AI makes available to one organization. A tenant administrator or a user with delegated MCP management permissions adds the server, chooses which of its tools may be called, and declares how it reaches the system behind it. Most servers reach that system as the individual calling user, so each member links their own credential before they can see or invoke its tools. A server whose upstream system needs no account is registered as unauthenticated and needs no credential from anyone.

Every call to a Connector passes through the MCP Gateway. Nothing reaches a Connector another way.

In this section

Understand the model

Administer

Use

Reference

Who does what

TaskRequired permission
Add a server and choose its credential modemcp.server.create
Edit a server or set its tool allowlistmcp.server.update
Delete a servermcp.server.delete
Read the tools a server advertises or use itmcp.server.use, plus personal credentials when required
List and inspect tenant serversmcp.server.list and mcp.server.read
Link or unlink personal credentialsmcp.credential.link and mcp.credential.unlink, respectively

Current tenant members have the list, read, use and personal credential permissions. Tenant administrators have server-management permissions; eligible custom roles can delegate them without granting tenant-administrator status. See the MCP permission catalogue.

Credential mode is chosen once, when the server is added, and cannot be changed afterwards. A member links a credential only to a server that asks for one.

Where Connectors are used

A Connector reaches BullSequana AI users in three ways.

In Portal chat and Build chats, each conversation switches Connectors on from the Tools button, and an Agent adds the Connectors it lists. See Use a Connector in chat.

Through the Responses API, a request with agent_id runs that Agent with its Connectors. An API key used for it needs agent.configuration.use and mcp.server.use. The Responses API's own mcp tool type is accepted for compatibility and ignored.

An external MCP client, such as a coding agent or a desktop assistant, connects straight to a server's Gateway URL. See Connect an MCP client.

In chat and in an Agent run, the model sees the tools of the servers the member can reach: the ones they have linked, and the unauthenticated ones, which need no link. A server that asks for a credential they have not linked is absent from the run. An external client's calls to such a server are refused.

On this page