🎉New in v4.3.0: Prompts!

[ravitemer]

Hey everyone! 👋

Just like how MCP servers provide tools, resources and resourceTemplates they also provide prompts as seen below.

In addition to the server provided prompts, we can also create our own prompts using native server architecture mcphub.add_prompt api. There are two inbuilt prompts in neovim server.

A prompt in a MCP server when executed return a messages array with each message with role and content.

• role can be of two types user and assistant (Note: Native server prompts can also have system role).
• content can be of many types: text, image, audio, blob, resource

These prompts are intended to be used by the user either in slash_commands or in a menu. When the slash_command is run we should populate chat history with corresponding messages. That's exactly we are doing now.

As you can see, we can define our own conversations with these prefilled messages and on next user message the llm replicates the behaviour defined in these prefilled messages.

CodeCompanion Integration ⚡

With CodeCompanion integration, all your MCP server prompts automatically become /slash_commands just like how resources become #variables. Just add this to your config:

require("mcphub").setup({
    extensions = {
        codecompanion = {
            -- Show the mcp tool result in the chat buffer
            -- NOTE:if the result is markdown with headers, content after the headers wont be sent by codecompanion
            show_result_in_chat = true,
            make_vars = true, -- make chat #variables from MCP server resources
            make_slash_commands = true, -- make /slash_commands from MCP server prompts
        }
    }
})

Now you can:

• Use any MCP server prompt with /mcp:prompt_name
• Enter arguments through friendly vim.ui.input prompts
• Get rich responses right in your chat window
• Messages are properly formatted with correct roles (user/assistant/system)

Realtime Updates

Just like how resources automatically update as #variables, your slash commands stay in sync with your MCP servers prompts.

This creates a really smooth workflow where you can:

1. Define your prompts in your MCP servers
2. Use them directly in chats with slash commands

Resources as #variables (just in case anyone missed it)

[joaoptpsa]

Can you 'reset' a prompt to say, the avant default one?

(I accidentally set parrot and can't undo it)

[ravitemer]

No, you need to start a new chat or clear the chat or reset it.

[joaoptpsa]

Ah! /new! I had /clear(ed) to no avail.
Thank you!