github / github/copilot-cli

Mcp issue in copilot

Ouverte
#3,461 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
area:mcp area:models area:tools
Langage dominant
Shell
Étoiles
11.2k
Forks
1.9k
Merge moyen
14 h 16 min
PR mergées (30 j)
6

Description

### Describe the bug

● 💡 No copilot instructions found. Run /init to generate a copilot-instructions.md file for this project.

● Copilot CLI's incomplete support for .vscode/mcp.json has been removed. See https://gh.io/copilotcli-mcpmigrate to migrate
to .mcp.json.

! Failed to connect to MCP server "ade_eck". Execute '/mcp show ade_eck' to inspect or check the logs.

! Failed to connect to MCP server "reliability". Execute '/mcp show reliability' to inspect or check the logs.

! Failed to connect to MCP server "smake". Execute '/mcp show smake' to inspect or check the logs.

! Failed to connect to MCP server "sch_general_edits". Execute '/mcp show sch_general_edits' to inspect or check the logs.

! Failed to connect to MCP server "demo". Execute '/mcp show demo' to inspect or check the logs.

! Failed to connect to MCP server "autoda". Execute '/mcp show autoda' to inspect or check the logs.

! Failed to connect to MCP server "eoumgr_flow_agent". Execute '/mcp show eoumgr_flow_agent' to inspect or check the logs.

! MCP server 'virtuoso_studio' is taking longer than expected to connect.

! MCP server 'netlister' is taking longer than expected to connect.

! MCP server 'maestro_sim_debug' is taking longer than expected to connect.

! MCP server 'intel_trc' is taking longer than expected to connect.

! MCP server 'maestro_query' is taking longer than expected to connect.

! MCP server 'maestro_edit' is taking longer than expected to connect.

! MCP server 'xtract' is taking longer than expected to connect.

! MCP server 'layoutsynthesis' is taking longer than expected to connect.

! MCP server 'intelrfill' is taking longer than expected to connect.

! MCP server 'migrationaide' is taking longer than expected to connect.

! MCP server 'libgen' is taking longer than expected to connect.

! MCP server 'dde' is taking longer than expected to connect.

! MCP server 'socb_check' is taking longer than expected to connect.

! MCP server 'custom_infra' is taking longer than expected to connect.

! MCP server 'esd' is taking longer than expected to connect.

! MCP server 'perc_erc' is taking longer than expected to connect.

! MCP server 'primelib' is taking longer than expected to connect.

! MCP server 'totem_rv_analyser' is taking longer than expected to connect.

! MCP server 'schematic_migration' is taking longer than expected to connect.

! MCP server 'ip_regression' is taking longer than expected to connect.

! MCP server 'cth_r2g_phoenix_tool' is taking longer than expected to connect.

! MCP server 'cth_r2g_sdhc_dev' is taking longer than expected to connect.

! MCP server 'cth_r2g_run_analyzer_agent' is taking longer than expected to connect.

! MCP server 'cth_r2g_lv_icv_v_cal' is taking longer than expected to connect.

! MCP server 'cth_r2g_power_mapping_debug_agent' is taking longer than expected to connect.

! MCP server 'cth_r2g_power_diff_debug_agent' is taking longer than expected to connect.

! MCP server 'cth_r2g_extraction_paranoia_review_agent' is taking longer than expected to connect.

! MCP server 'cth_sd_eda_communicator' is taking longer than expected to connect.

! MCP server 'cth_dteg_sage' is taking longer than expected to connect.

! MCP server 'cth_r2g_power_clock_agent' is taking longer than expected to connect.

! MCP server 'fc_innovus_conversion_agent' is taking longer than expected to connect.

! MCP server 'arc_prime' is taking longer than expected to connect.

! MCP server 'blocksinfo' is taking longer than expected to connect.

! MCP server 'crt' is taking longer than expected to connect.

! MCP server 'csv_analyzer' is taking longer than expected to connect.

! MCP server 'hsd' is taking longer than expected to connect.

! MCP server 'jenkins' is taking longer than expected to connect.

! MCP server 'netbatch' is taking longer than expected to connect.

! MCP server 'p4' is taking longer than expected to connect.

! MCP server 'rag' is taking longer than expected to connect.

! MCP server 'snps_ka' is taking longer than expected to connect.

! MCP server 'splunk' is taking longer than expected to connect.

! MCP server 'sql_database' is taking longer than expected to connect.

! MCP server 'cdislookup' is taking longer than expected to connect.

! MCP server 'confluence' is taking longer than expected to connect.

! MCP server 'stodstatus' is taking longer than expected to connect.

! Failed to connect to MCP server "ip_regression". Execute '/mcp show ip_regression' to inspect or check the logs.

! Failed to connect to MCP server "virtuoso_studio". Execute '/mcp show virtuoso_studio' to inspect or check the logs.

! Failed to connect to MCP server "netlister". Execute '/mcp show netlister' to inspect or check the logs.

! Failed to connect to MCP server "intel_trc". Execute '/mcp show intel_trc' to inspect or check the logs.

! Failed to connect to MCP server "maestro_edit". Execute '/mcp show maestro_edit' to inspect or check the logs.

● GitHub MCP Server: Connected

● Environment loaded: 24 skills, 42 MCP servers, 6 plugins, 22 agents, Visual Studio Code connected

❯ hi

● Request failed (transient_bad_request). Retrying...

● Request failed (transient_bad_request). Retrying...

✗ Execution failed: CAPIError: 400 Invalid 'tools': array too long. Expected an array with maximum length 128, but got an array
with length 467 instead. (Request ID: 6124:66486:A03991:B3C038:6A0FCC57)

### Affected version

_No response_

### Steps to reproduce the behavior

_No response_

### Expected behavior

_No response_

### Additional context

_No response_

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

Start by reproducing the failure with the reported MCP configuration, including .vscode/mcp.json and the migrated .mcp.json, then run /mcp show for an affected server and inspect the logs. Use the reported 467-tool request and the 128-tool limit as the observed failure boundary; done means the CLI handles this configuration without producing the CAPIError.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
github, shell, vscode
Domaine
cli, devtools
Type d'issue
Bug
Difficulté
4/5
Temps estimé
3-5 jours
Activité
Calme
Clarté
À clarifier
Accessibilité débutants
35/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.