A custom agent is configured with a local MCP server so Copilot can query internal API contract metadata before editing generated client code. When the issue is assigned to Copilot, the session starts, but the agent cannot list the MCP tools. Which option best explains the log output? Select one answer.
Copilot cloud agent session: 74291
Repository: octo-org/payments-api
Agent profile: api-client-agent
Start MCP Servers
Loading agent profile from .github/agents/api-client-agent.md
MCP server: api-contracts
type: local
command: uvx
args: ["internal-contracts-mcp"]
Error: spawn uvx ENOENT
MCP server api-contracts failed to start
No tools were discovered for api-contracts
Environment setup
.github/workflows/copilot-setup-steps.yml not found
Using default GitHub-hosted runner image
Result
Agent continued with built-in repository tools onlyChoose an answer
Tap an option to check your answer.
Correct answer: MCP dependency missing from setup environment.
Why this is the answer
The error "spawn uvx ENOENT" indicates that the uvx command, which is specified to start the api-contracts MCP server, was not found in the environment where the agent is running. ENOENT stands for "Error No Entry," meaning the system could not find the executable. This points to a missing dependency or an incorrect path setup for uvx in the agent's execution environment. Without the MCP server starting correctly, no tools can be discovered from it. "Agent profile omitted GitHub tool aliases" is incorrect because the issue is with the MCP server startup, not tool aliases. "GITHUBTOKEN cannot write pull requests" is irrelevant to the MCP server failing to start. "Pull request workflow lacked path filters" is also unrelated to the MCP server's inability to launch.
Pass your exam — without the endless answer hunt
Get every verified question and explanation for this exam in one place, and save hours of prep. 1,000+ certifications · 20+ languages · free to start.
Pass your exam faster → No card needed