GitHub MCP Server

github_set_token

Set a GitHub personal access token to authenticate API requests and enable secure access to repository data.

Instructions

Set the GitHub personal access token for authentication

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "token": "<token>"
    },
    "name": "github_set_token"
  }
}

Input Schema

Name	Required	Description	Default
`token`	Yes	GitHub personal access token

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 9, 2026

TDQS

A3.5/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states the action and purpose, but does not disclose whether the token is persisted, whether it overwrites an existing token, or any security implications. This lack of side-effect information is a significant gap for a mutation-like tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, short, front-loaded sentence with no filler. It communicates the essential action and purpose in the fewest possible words, earning every character.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with a single parameter and no output schema, so the description is minimally adequate. However, it lacks context about how this tool relates to sibling GitHub tools (e.g., whether setting the token is required before using them) and does not explain persistence or scope, leaving clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with the parameter 'token' described as 'GitHub personal access token'. The description adds no additional meaning beyond what the schema already provides, which aligns with the baseline score for full coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the specific verb 'Set' and names the resource 'GitHub personal access token', clearly distinguishing this from sibling tools that list/get PR data. It unambiguously states the tool's function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'for authentication' implies it is a prerequisite/configuration step, but it does not explicitly state when to use it relative to sibling tools or mention any exclusion conditions. There is no indication that it should be used before other GitHub API calls, leaving usage context only implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server