8000 stop using environment variables · Issue #210 · upstash/context7 · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

stop using environment variables #210

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
ryanleecode opened this issue May 20, 2025 · 1 comment
Open

stop using environment variables #210

ryanleecode opened this issue May 20, 2025 · 1 comment

Comments

@ryanleecode
Copy link
Contributor
ryanleecode commented May 20, 2025 •
edited
Loading

No reason that we should be using environment variables and dotenv; this is breaking deno as the only permission i want to pass is allow-net. the MCP server shouldnt require access to my file system.

We can easily just pass in command line arguments.

Contextually when I raised this issue, the response was

"The MCP server in this case doesn’t really deal with the file system or env variables — it just sends requests to a remote API. So there’s not much risk in practice."

#7 (comment)
@ryanleecode ryanleecode mentioned this issue May 20, 2025
Open
@ryanleecode
Copy link
Contributor Author

The alternative approach would be to keep using that environment variable but not using dotenv as it will try to search your file system for .env files -- we shouldn't require access to the filesystem as per the discussion in #7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ryanleecode
0