Plugin Directory Features

[nzlov]

Now users are required to control the activation of the MCP service. Is it possible to provide a directory for the large model so that the large model can search and activate the corresponding MCP service by itself?

[ravitemer]

we can send it the list of available servers including the disabled ones and give it a start_mcp_server tool to let it start it. I am not sure I understand what you mean by giving a directory, do you mean the servers json file?

[nzlov]

What I mean is that now the large model is limited by the length of the context, and we should provide a retrieval tool for the large model to filter the tools it needs, such as a directory or search.

[ravitemer]

That's a nice idea. This can be implemented. We can provide some servers upfront and give it a retreival tool. Will think about how to implement it.

See #40 PR in the Native servers section. You can try using that branch and add a tool to the current basic neovim server.

[nzlov]

What an amazing update. Thank you.

It would be great if the tools that overlap with avante could be automatically disabled or at least mentioned in the documentation.

[ravitemer]

Yes, the neovim mcp server is not finalized yet. I wanted to provide same set of capabilities irrespective of the chat plugin. I am not totally sure if I should create all tools like file operations, diffs, terminal etc. that already exist with avante or not.

What do you think? How do you feel having all the neovim tools inbuilt? This might require a lot of maintaining but I feel this might be helpful for the users if well implemented.

[nzlov]

Perhaps the relevant tools should be extracted and made into a separate MCP server. This would maintain the simplicity of each plugin and reduce maintenance efforts.

@yetone What do you think?