Github · Developer
GITHUB_CREATE_ISSUE
Create an issue in a GitHub repository using the connected token. Use only after explicit user approval. Returns { id, number, title, state, html_url }.
- Provider
- Github
- Access
- Write
- Category
- Developer
- Version
- v1
Input schema
{
"type": "object",
"properties": {
"owner": {
"type": "string",
"description": "Repository owner (user or org login)."
},
"repo": {
"type": "string",
"description": "Repository name."
},
"title": {
"type": "string",
"description": "Issue title."
},
"body": {
"type": "string",
"description": "Optional issue body in Markdown."
}
},
"required": [
"owner",
"repo",
"title"
],
"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_create_issue 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.
Write action — gate behind explicit user approval and write scope.
Frequently asked
- How do I let an AI agent github create issue?
- Connect Github to CybrLink, then expose the `github_create_issue` 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. Create an issue in a GitHub repository using the connected token. Use only after explicit user approval. Returns { id, number, title, state, html_url }.
- Does the AI model see my Github credentials when using GITHUB_CREATE_ISSUE?
- No. CybrLink stores the credential in a token vault and injects it on the server for each call, so the model can take this action in Github without the OAuth token or API key ever entering its context.