GitHub connector
The GitHub data source connects to GitHub through the GitHub MCP server. It provides search across code, repositories, issues, pull requests, and users. It also provides access to commits, branches, tags, releases, teams, and file contents. It uses Bearer token (personal access token) authentication.
You can create connectors in Stack Management > Connectors.
GitHub connectors have the following configuration properties:
- MCP Server URL
- The URL of the GitHub MCP server. Defaults to
https://api.githubcopilot.com/mcp/. - Bearer Token
- A GitHub personal access token for authentication. Refer to Get API credentials for instructions.
You can test connectors when you create or edit the connector in Kibana.
The GitHub connector exposes the following actions:
getMe- Get the authenticated GitHub user's profile information.
searchCode- Search for code across GitHub repositories.
searchRepositories- Search for GitHub repositories.
searchIssues- Search for issues across GitHub repositories.
searchPullRequests- Search for pull requests across GitHub repositories.
searchUsers- Search for GitHub users.
listIssues- List issues in a repository. Uses cursor-based pagination.
listPullRequests- List pull requests in a repository. Uses cursor-based pagination.
listCommits- List commits in a repository. Uses cursor-based pagination.
listBranches- List branches in a repository. Uses cursor-based pagination.
listTags- List tags in a repository. Uses cursor-based pagination.
listReleases- List releases in a repository. Uses cursor-based pagination.
getCommit- Get details of a specific commit.
getLatestRelease- Get the latest release for a repository.
pullRequestRead- Read the details of a specific pull request.
getFileContents- Get the contents of a file or directory from a GitHub repository.
getIssue- Get details of a specific issue in a repository.
getIssueComments- Get comments for a specific issue in a repository.
listTools- List all tools available on the GitHub MCP server. Use this to discover available capabilities.
callTool- Call any tool on the GitHub MCP server directly by name. Use this as an escape hatch when a specific tool is not yet exposed as a named action.
Use the Action configuration settings to customize connector networking, such as proxies, certificates, or TLS settings. You can set configurations that apply to all your connectors or use xpack.actions.customHostSettings to set per-host configurations.
To use the GitHub connector, you need a GitHub personal access token:
- Log in to GitHub.
- Go to Settings > Developer settings > Personal access tokens > Fine-grained tokens (or create one directly).
- Select Generate new token.
- Configure the token:
- Set a descriptive name (for example, "Kibana data source").
- Select an expiration period.
- Select the repositories you want to grant access to.
- Under Permissions, grant read access to the resources you need (for example, Contents, Issues, Pull requests, Metadata).
- Select Generate token.
- Copy the token and store it securely. Use this value as the Bearer Token when configuring the GitHub connector in Kibana.
Classic personal access tokens also work. When using a classic token, select the repo scope for full repository access, or public_repo for public repositories only.