Skip to content

codex_app MCP server fails to start due to incorrect relative path resolution #502

Open

Description

@vladimir-trifonov

Description

When running Agent Scan v0.6.8, the discovered codex_app MCP server fails to start because the relative ./server.mjs path appears to be resolved against the directory where Agent Scan was launched, rather than the MCP/plugin directory.

Error

[codex_app] Error: Cannot find module '<current-working-directory>/server.mjs'

The MCP configuration is discovered under:

~/.codex/plugins/cache/openai-bundled/codex-app-tools/0.1.5/.mcp.json

and Agent Scan reports a command similar to:

~/.codex/plugins/cache/openai-bundled/codex-app-tools/0.1.5/scripts/launch_codex_app_tools_mcp ./server.mjs

However, ./server.mjs appears to be resolved relative to the directory from which Agent Scan was launched.

Expected behavior

Relative paths used by an MCP configuration should be resolved in the appropriate MCP/plugin context, allowing the MCP server to start regardless of the directory from which snyk-agent-scan is executed.

Steps to reproduce

  1. Have the Codex codex-app-tools plugin installed.
  2. Run Agent Scan from a directory unrelated to the plugin:
uvx snyk-agent-scan@latest
  1. Allow the discovered codex_app MCP server to start.
  2. Observe that Node attempts to load ./server.mjs from the current working directory.

Environment

  • macOS
  • Snyk Agent Scan v0.6.8
  • Run via uvx snyk-agent-scan@latest
  • MCP server: codex_app

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions