Replies: 2 comments 6 replies
-
|
Hey! First off, thanks for this amazing plugin! I was exploring it yesterday and going through the wiki, but I’m feeling a bit lost. If you ever have the time, it would be really helpful to have a blog post or a single markdown file that walks through an Example with everything step by step, from installation to setup, usage, and even how it works with CodeCompanion. A complete workflow example would make it so much easier to understand. That would be greatly appreciated! 😊 |
Beta Was this translation helpful? Give feedback.
-
|
Seems like it doesn't work for me or I am missing a step ravitemer/mcphub.nvim#62 |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
Hey everyone! 👋
Just like how MCP servers provide
tools,resourcesandresourceTemplatesthey also providepromptsas seen below.In addition to the server provided prompts, we can also create our own prompts using native server architecture
mcphub.add_promptapi. There are two inbuilt prompts inneovimserver.A
promptin a MCP server when executed return amessagesarray with each message withroleandcontent.rolecan be of two typesuserandassistant(Note: Native server prompts can also havesystemrole).contentcan be of many types: text, image, audio, blob, resourceThese 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_commandsjust like how resources become#variables. Just add this to your config:Now you can:
/mcp:prompt_nameRealtime 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:
Resources as #variables
Beta Was this translation helpful? Give feedback.
All reactions