GitHub remote MCP connector
The GitHub remote Model Context Protocol (MCP) connector in Mark (Optimizely Agent Platform) lets you access, manage, and collaborate on code repositories. Connect GitHub to Mark to streamline your development workflows without leaving your AI workspace. These tools connect directly to your GitHub environment. Use them to search repositories, read and analyze source code, manage issues and pull requests. Review commits and automate development tasks from Mark.
Note
The GitHub remote MCP is managed by GitHub. See the Remote GitHub MCP Server documentation in GitHub.
First, a Mark administrator must Connect the GitHub remote MCP to Mark. After adding the MCP server, individual Mark users and agent builders log in to GitHub to access their information from Mark. Administrators need to add the GitHub remote MCP only once.
Connect the GitHub remote MCP to Mark
Note
The first person to connect a third-party service to Mark should be an administrator of that service. Administrator access installs the complete set of tools, so Mark adds every available tool. If a non-administrator connects the service first, Mark installs only the tools that account can access.
Mark administrators connect and grant access to GitHub from Mark. After granting access, administrators select which tools to enable in Mark and optionally customize their display names.
Add GitHub connection
As a Mark administrator, complete the following steps:
- Go to Connectors in Mark.
- (Optional) Enter GitHub in the search bar to filter the connectors list.
- Click Connect on the GitHub tile.
- Log in to your GitHub account.
- Configure the connector.
- Click Accept.
A confirmation message displays and you can close the pop-up window.
Configure Mark tools
After adding the GitHub connection, Mark prompts you to select which tools to enable and optionally customize their display names.
As a Mark administrator, complete the following steps:
- Deselect any tools you do not want to add to Mark.
- (Optional) Update any tool's display name.
- Click Finish.
The GitHub tile displays Connect on the Connectors tab for Mark users to authenticate with their personal accounts.
To update the available tools or names, see Update tools.
Authenticate with GitHub
Each Mark user and agent builder logs in to GitHub individually to access their GitHub data from Mark. User-level authentication ensures you access only the data your GitHub account is authorized to view.
Before you begin, confirm that a Mark administrator has connected the GitHub remote MCP to Mark. Until an administrator connects it, the GitHub tile displays Contact admin instead of Connect and you cannot select it.
- Go to Connectors.
- (Optional) Enter GitHub in the search bar to filter the connectors list.
- Click Connect on the GitHub tile.
- Log in to GitHub.
After you connect to GitHub, the GitHub connector tools become available in Mark chat, agents, and workflows.
GitHub connector tools
GitHub connector tools are available in Mark after an administrator connects the GitHub remote MCP to Mark and you log in to GitHub from Mark. The available tools depend on which tools your administrator enabled. For a full list of available tools and actions, see Remote GitHub MCP Server documentation in GitHub.
Update tools
To rename, add, or remove tools, a Mark administrator must delete the GitHub tools registry and re-add it. To do so, complete the following steps:
- Follow the steps in Delete a tool registry.
Note
If you use Opti ID, administrators can turn off generative AI in the Opti ID Admin Center. See Turn generative AI off across Optimizely applications.