-
Notifications
You must be signed in to change notification settings - Fork 3.7k
MCP server configured in .warp/.mcp.json not accessible to Oz agent in same session #9111
Copy link
Copy link
Open
Labels
area:agentAgent workflows, conversations, prompts, cloud mode, and AI-specific UI.Agent workflows, conversations, prompts, cloud mode, and AI-specific UI.area:mcpMCP server integrations, tool connections, and resource providers.MCP server integrations, tool connections, and resource providers.bugSomething isn't working.Something isn't working.os:macmacOS-specific behavior, regressions, or requests.macOS-specific behavior, regressions, or requests.ready-to-implementThe issue is ready for implementation work.The issue is ready for implementation work.repro:mediumThe report suggests a plausible repro path, but some uncertainty remains.The report suggests a plausible repro path, but some uncertainty remains.triagedIssue has received an initial automated triage pass.Issue has received an initial automated triage pass.
Description
Metadata
Metadata
Assignees
Labels
area:agentAgent workflows, conversations, prompts, cloud mode, and AI-specific UI.Agent workflows, conversations, prompts, cloud mode, and AI-specific UI.area:mcpMCP server integrations, tool connections, and resource providers.MCP server integrations, tool connections, and resource providers.bugSomething isn't working.Something isn't working.os:macmacOS-specific behavior, regressions, or requests.macOS-specific behavior, regressions, or requests.ready-to-implementThe issue is ready for implementation work.The issue is ready for implementation work.repro:mediumThe report suggests a plausible repro path, but some uncertainty remains.The report suggests a plausible repro path, but some uncertainty remains.triagedIssue has received an initial automated triage pass.Issue has received an initial automated triage pass.
Bug Report
Description
When an MCP server is configured via
~/.warp/.mcp.jsonand shows as connected in Settings > MCP Servers (green dot, tools listed), the Oz agent in a conversation is unable to call any of its tools.list_relevant_mcp_contextreturnsNo relevant MCP context foundeven after starting a new conversation.Steps to Reproduce
~/.warp/.mcp.json(e.g. Nightwatch vianpx -y mcp-remote https://nightwatch.laravel.com/mcp).list_applications).Expected Behavior
The Oz agent should be able to call tools from any MCP server that is connected and visible in Settings.
Actual Behavior
list_relevant_mcp_contextreturns no context. The agent cannot access the tools despite the server showing as connected in the UI.Workaround
The same MCP server works correctly in Claude Code, confirming the server itself is functional.
Environment
nightwatch(npx -y mcp-remote https://nightwatch.laravel.com/mcp)~/.warp/.mcp.json