Tomas Slusny

We could but I dont see point in having rest as well as that should be handled on the api side anyway. Even though I guess instead of response you...

> Hi, I see you mentioned MCP in the PR so I want to ask: is it planned to support MCP at some point? there's been some effort in the...

Getting close to having something that actually works:  

 a bit more progress, looking nice

Works quite nicely with mcphub as well, still need to deal with converting output but close enough: ```lua require('mcphub').setup({ on_ready = function(hub) local async = require('plenary.async') local call_tool = async.wrap(function(server,...

 ok outputs working nice

https://github.com/github/github-mcp-server example: 

There are still few issues that I need to think about before merging this even though technically this works: MCP is very badly designed protocol imo and you have to...

Ok finally figured out nice way how to structure this, i renamed tools to functions and merged tools and resources together, example of tool + function: ```lua file = {...

I realized i kinda forgot to put tool calls and tool call responses to history properly so I will probably need to adjust that as well