GitHub Copilot
Connect GitHub Copilot to the Akeyless MCP Server.
Connect GitHub Copilot to the Akeyless MCP Server when you want Copilot to access Akeyless tools through MCP.
For general MCP background and command syntax, see MCP Server.
Requirements
- Akeyless CLI version
1.130.0or later. - GitHub Copilot CLI installed.
- A configured Akeyless profile, or the authentication values required by your chosen access type.
- A Gateway URL passed directly in the client configuration.
Install GitHub Copilot CLI
npm install -g @githubnext/github-copilot-cliConfigure GitHub Copilot
- Install and configure the Akeyless CLI.
- Edit
~/.copilot/mcp-config.json. - Add the Akeyless MCP server configuration.
- Start GitHub Copilot with MCP enabled.
The following examples show common authentication configurations:
{
"mcpServers": {
"akeyless": {
"command": "akeyless",
"args": [
"mcp",
"--profile", "<profile-name>",
"--gateway-url", "https://<your-gateway-url>:8000/api/v2"
]
}
}
}{
"mcpServers": {
"akeyless-saml": {
"command": "akeyless",
"args": [
"mcp",
"--access-id", "<access-id>",
"--access-type", "saml",
"--gateway-url", "https://<your-gateway-url>:8000/api/v2"
]
}
}
}{
"mcpServers": {
"akeyless-oidc": {
"command": "akeyless",
"args": [
"mcp",
"--access-id", "<access-id>",
"--access-type", "oidc",
"--gateway-url", "https://<your-gateway-url>:8000/api/v2"
]
}
}
}Start Copilot with MCP:
copilot mcpVerify The Integration
After GitHub Copilot starts with MCP enabled, verify that it can run MCP-backed requests such as:
- "Show me my Akeyless secrets"
- "List all my targets"
- "Create a new secret called
api-key"
Notes
- The Akeyless CLI serves MCP over
stdio, so GitHub Copilot must invoke theakeyless mcpcommand directly. - When
--profileis used, the saved CLI profile supplies the authentication settings. - Pass
--gateway-urldirectly in the Copilot configuration even when the profile already has a saved Gateway value.
Updated 2 days ago
