Jonathan Hefner

> what if instead it added a `# safe` comment ? I did consider a special comment, but comments can become "unmoored" from their keys. For example: ```shell # settings...

> but how about an inline comment only? > > ``` > PORT="8000" # safe > ``` Comments have less "discoverability". For example, if a user isn't familiar with dotenvx...

> something that has been kicking around in my head long term for dotenvx is the ability to do something like this in your code: > > ``` > const...

Implemented by https://github.com/modelcontextprotocol/modelcontextprotocol/pull/173.

I previously left some feedback regarding the async resource approach: https://github.com/modelcontextprotocol/modelcontextprotocol/discussions/491#discussioncomment-13163140. I believe all of those points apply to this approach as well. Some additional points for this approach: *...

> > If a tool returns multiple items in CallToolResult.content, the client may have to maintain a subscription for each item. > > Adding GetResource will provide an alternative to...

> > By "changing the nature of", I mean there will be a bifurcation. Think about how sync tools and async tools will require entirely separate code paths in the...

> The start_task would behave a bit like call_tool but instead of being expected to get a result immediately the client gets a reference that can be used to get...

I agree with what @Joffref said: > I wouldn’t list that as required; I’d rather present it as the easiest path. Session management is ultimately at the discretion of whoever...

As mentioned in https://github.com/modelcontextprotocol/modelcontextprotocol/pull/451#issuecomment-2847667749, those are completely different projects that both happened to be named `mcp-snowflake-service`, so I will close.