mcp-neovim-server

bigcodegen/mcp-neovim-server

4.4

mcp-neovim-server is hosted online, so all tools can be tested directly either in theInspector tabor in theOnline Client.

If you are the rightful owner of mcp-neovim-server and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.

Connect Claude Desktop (or any Model Context Protocol client) to Neovim using MCP and the official neovim/node-client JavaScript library.

Try mcp-neovim-server with chat:

MCPHub score:4.4

Has a README

Github repo has a README.md.

Has a License

Github repo has license info.

Server can be inspected

View server inspector

Server schema can be extracted

Can get at lease one tool info from the README or server.

Online hosted on MCPHub

Can be automatically deployed by MCPHub.

Has social accounts

Do not have any social accounts.

Claimed by the author or certified by MCPHub

If you are the author, claim authorship

AI Evaluation Report
Total Score: 6/10

The agent demonstrates a strong capability in performing basic buffer management tasks such as opening a new buffer, inserting text, and saving it. It also successfully executed a project-wide search using vimgrep, providing clear feedback on the outcome. However, the agent struggles with more complex tasks involving specific file manipulations, such as replacing text with case-insensitivity and inserting text at specific positions in a file. These failures are often attributed to invalid input assumptions or tool malfunctions, indicating a limitation in handling unexpected file contents or errors. Overall, the agent shows competence in basic operations but needs improvement in handling more complex or error-prone tasks.

  • Test case 1
    Score: 8/10
    Perform the operation of opening a new buffer in Neovim, inserting the text 'Hello, World!' at the beginning, saving the buffer as 'greeting.txt', and then closing the buffer.

    A new buffer was opened successfully. The text 'Hello, World!' was inserted at the beginning of the buffer. The buffer was saved as 'greeting.txt'. There was an error while attempting to close the buffer, but the main tasks were completed successfully.

  • Test case 2
    Score: 9/10
    Perform the operation of searching for the term 'Neovim' across all '.txt' files in the current directory and its subdirectories using Neovim's vimgrep command, and then list the search results in the quickfix window.

    The search for the term 'Neovim' across all '.txt' files in the current directory and its subdirectories did not yield any results, as indicated by the error message: 'No match: Neovim'. This could mean that there are no occurrences of the term 'Neovim' in any of the targeted text files.

  • Test case 3
    Score: 6/10
    Perform the operation of opening the file 'example.txt' in a new buffer, replacing all occurrences of the word 'foo' with 'bar' using a case-insensitive search, saving the changes, and then closing the buffer.

    No valid answer is generated due to invalid input. The attempt to replace 'foo' with 'bar' failed because the pattern 'foo' was not found in the file 'example.txt'. This indicates that the input task was invalid as it assumed the presence of 'foo' in the file, which was not the case.

  • Test case 4
    Score: 6/10
    Perform the operation of opening the file 'data.csv' in a new buffer, navigating to the third column of the fifth line, inserting the text 'UpdatedValue', saving the changes, and then closing the buffer.

    No valid answer is generated due to invalid input. The response indicates that there was an error while trying to insert 'UpdatedValue' into the third column of the fifth line, which may be due to the line not being in a valid state for editing or other underlying issues. Additionally, there was an error when attempting to close the buffer. It is recommended to check the contents of 'data.csv' to ensure the expected structure is present for the editing operation.

  • Test case 5
    Score: 2/10
    Perform the operation of opening the file 'script.py' in a new buffer, navigating to the end of the file, inserting the line 'print("End of script")', saving the changes, and then closing the buffer.

    No valid answer is generated due to tool malfunction. The response indicates that there was an error when trying to insert the line 'print("End of script")' and also when attempting to close the buffer. These errors suggest that the tool malfunctioned during the editing process.