Github · Developer
GITHUB_GET_AUTHENTICATED_USER
Get the GitHub user tied to the connected personal access token. Returns { login, id, name, company, html_url, public_repos }.
- Provider
- Github
- Access
- Read
- Category
- Developer
- Version
- v1
Input schema
{
"type": "object",
"properties": {},
"additionalProperties": false
}How to call it
Expose this tool to any MCP-capable agent (Claude, GPT, or your own) through CybrLink's MCP server. The agent calls github_get_authenticated_user with arguments matching the schema above.
CybrLink validates the input, injects the connected Github credentials server-side, and runs a single scoped provider API call through the shared proxy — the same guarded path as the generic call_api tool. The raw secret never reaches the model, and the response is trimmed to just the fields the agent needs.
Frequently asked
- How do I let an AI agent github get authenticated user?
- Connect Github to CybrLink, then expose the `github_get_authenticated_user` tool to any MCP-capable agent (Claude, GPT, or a custom framework). The agent calls it with typed arguments; CybrLink injects the Github credential server-side and runs one scoped API call. Get the GitHub user tied to the connected personal access token. Returns { login, id, name, company, html_url, public_repos }.
- Does the AI model see my Github credentials when using GITHUB_GET_AUTHENTICATED_USER?
- No. CybrLink stores the credential in a token vault and injects it on the server for each call, so the model can read this data from Github without the OAuth token or API key ever entering its context.