Skip to main content
Integrations is the page where you connect outside services to Cortex. It invites you in with Connect the tools your sessions need to reach., and it is the right place to connect GitHub and to register an MCP server for your workspace. Read the next paragraph before you connect anything, because the page’s invitation is broader than what a Cortex Code session can use today.
Tools connected here do not reach a Code session today. A Code turn is built with an empty tool catalog for outside tools, so a Code session is given no MCP servers, no connected apps and no plugins. The session will tell you so itself: its Tools tab can read Off · this session has no MCP access. and Off · Chat and Bot access does not carry into Code. Connected apps do work elsewhere, in Connectors for Cortex Chat and in Connected apps and secrets for a bot. Treat this page as workspace configuration, and never plan a Code session around a tool you connected here.
The one thing on this page that genuinely changes what a Code session can do is the GitHub connection, because that is what gives Code repositories to work in and the ability to open a pull request. Everything else is configuration held for the workspace.

​
The sections of the page

​
Connected apps

An app on this page is in one of two states, and there are only two. Either Cortex can connect it, or it renders Not connectable, which means its tools exist but Cortex has no sign-in for it yet. There is no third option, and in particular there is no token method for a connected app: you cannot make an app connectable by pasting a credential. At least one app in the list is not connectable yet. That row is doing what it should, so do not read it as a fault or an outage on your side.
An MCP server’s optional bearer token is a different thing entirely and stays. Aside from that one field, no Code surface asks you to paste a credential: there is no personal access token field anywhere, and Code has no Secrets page.

​
Repositories

The REPOSITORIES section is a view of your GitHub connection rather than a separate setting, and its empty copy tells you which of three situations you are in. Connect GitHub is a single control with a single label, and it appears here, in the composer’s repository picker, in the dashboard checklist and in Settings. If the connection has lapsed it reads Reconnect GitHub instead and says so. When GitHub is connected there is no control and no note, and on a deployment without GitHub the control is simply absent rather than greyed out. For the whole flow, including what to do when a connection attempt does not finish, see Connect GitHub.
The connection Code uses is not the only GitHub install Cortex offers. Cortex Security’s GitHub App is a separate install that lets it read pull requests and post checks, and the Cortex CLI has its own install command. Connecting one does not connect the others. See Pull-request review and Code in the terminal.

​
MCP servers

You register an MCP server with three fields.
1

Name it

Name is the label you will recognise the server by.
2

Give it a URL

URL is the server’s address.
3

Add a token if it needs one

Auth token is optional. Its own hint is the guarantee worth reading: Sent as a bearer token on every call. Sealed on the server. Once saved it is never read back into the form, so keep your own copy if you need it again.
A registered server is configuration held for the workspace. Whether a given surface can reach it is decided by that surface, and a Code session reports its own answer on its Tools tab, where rows read On, Off or Organization denied. A session with nothing available shows No tool servers on this session. For MCP in a surface where it is used today, see MCP servers.

​
API keys

The API keys section exists on this page for programmatic access to your account. How a key is created, shown or revoked here is not documented, so work from the section in the app rather than from an expectation set here.

​
What is not available

  • MCP servers, connected apps and plugins in a Code session. Configured here, not given to a Code turn. This is the limit to plan around.
  • Scoping a server to one repository, and any per-workspace server limit shown to you, are not documented. No number is shown on this page.
  • The full list of connectable apps changes with the connector marketplace, so read the page rather than a list in the docs.