Describe the bug

When using the remote GitHub MCP server (https://api.githubcopilot.com/mcp/) and enabling the actions toolset, tools/list does not include the
consolidated Actions tools (actions_get, actions_list, actions_run_trigger). Instead it returns only the legacy per-endpoint tool names (e.g.
list_workflows, get_workflow_run, etc).

This is surprising because we just recently migrated to work with consolidated actions but now it breaks again today, not sure if there's any feature flag changes on the remote MCP server deployment

Affected version

• Remote server: https://api.githubcopilot.com/mcp/ (reproduced via MCP Inspector on <DATE/TIME>)
• Open-source reference: v0.26.3 (63c7db0) Add aliases for new actions tools #1652

Steps to reproduce the behavior

1. Start MCP Inspector:

   npx @modelcontextprotocol/inspector --transport http --server-url https://api.githubcopilot.com/mcp/

2. Set request header:

   • X-MCP-Toolsets: actions

3. Call tools/list

Expected vs actual behavior

Expected

• tools/list for the actions toolset includes consolidated tools like:
  • actions_get
  • actions_list

Actual

• actions_get is missing; only legacy tools are returned. The tool names I see include:
  • cancel_workflow_run
  • delete_workflow_run_logs
  • download_workflow_run_artifact
  • get_job_logs
  • get_workflow_run
  • get_workflow_run_logs
  • get_workflow_run_usage
  • list_workflow_jobs
  • list_workflow_run_artifacts
  • list_workflow_runs
  • list_workflows
  • rerun_failed_jobs
  • rerun_workflow_run
  • run_workflow

Logs

Inspector output excerpt (full tools/list response available, can paste if needed):

{
"tools": [
{ "name": "list_workflows", ... },
{ "name": "get_workflow_run", ... }
// ... no actions_get/actions_list/actions_run_trigger present
]
}

Additional context

In the open-source repo, the consolidated Actions tools are gated behind the remote_mcp_consolidated_actions feature flag, and the legacy
Actions tools are disabled when that flag is enabled. It looks like the remote deployment may currently have that flag disabled (or rolled back), which would explain why actions_get isn’t advertised.

If the remote server is expected to expose the consolidated tools, can you confirm whether this is a remote rollout/config regression? If the remote server is not expected to expose them yet, could the docs be updated to clarify the remote behavior/timeline?