Skip to content

MCP configuration Environment Variable expansion does not work in cmd section #4014

@axmo

Description

@axmo

App Version

v3.18.3

API Provider

Not Applicable / Other

Model Used

N/A

🔁 Steps to Reproduce

Create a .env.local file with

SUPABASE_ACCESS_TOKEN=<valid access token>

Add an MCP config like:

"supabase": {
    "command": "npx",
    "args": [
        "-y",
        "@supabase/mcp-server-supabase@latest",
        "--access-token",
        "${env:SUPABASE_ACCESS_TOKEN}"
    ],
    "alwaysAllow": []
}

💥 Outcome Summary

Expected result: the MCP server connects to Supabase using <valid access token> pulled from .env.local via variable substitution.

Actual result: the MCP server attempts to connect to Supabase using the literal string "${env:SUPABASE_ACCESS_TOKEN}" as the access token.

📄 Relevant Logs or Errors (Optional)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Issue/PR - TriageNew issue. Needs quick review to confirm validity and assign labels.bugSomething isn't working

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions