sincecutoff.com
/v1/json /v1/md llms.txt
← all changes

github-mcp-server can exclude tools through server configuration

Introduced 2026-02-19 · score 0.91

HOW TO USE IT

When configuring a GitHub MCP Server deployment, list the tools to disable as comma-separated names. Set them with `--exclude-tools` for a local server or `X-MCP-Exclude-Tools` for a remote server; excluded tools stay disabled even if otherwise enabled.

{"type":"stdio","command":"go","args":["run","./cmd/github-mcp-server","stdio","--toolsets=<toolsets>","--exclude-tools=<tool1>,<tool2>"],"env":{"GITHUB_PERSONAL_ACCESS_TOKEN":"<github-token>"}}
{"type":"http","url":"https://api.githubcopilot.com/mcp/","headers":{"X-MCP-Toolsets":"<toolsets>","X-MCP-Exclude-Tools":"<tool1>,<tool2>"}}

WHY THIS HELPS

Disable selected tools in a GitHub MCP Server deployment configuration.

REQUIREMENTS AND LIMITATIONS

  • Version: v0.31.0
  • --exclude-tools=<tool1>,<tool2> (required): Comma-separated tool names to disable, regardless of other settings.
  • X-MCP-Exclude-Tools: <tool1>,<tool2> (required): Remote-server header listing comma-separated tool names to disable.
  • Prerequisite: Use the local stdio or remote HTTP server configuration format; the docs’ local example supplies a GitHub personal access token through `GITHUB_PERSONAL_ACCESS_TOKEN`.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card