Thoughts on main Developer creating MCP client?

Feature Discussion
1

Yo all, I have been using the MCP client created by the community and they aren’t production-ready. Is the lead dev considering creating one themselves? Curious on the communities thoughts. At this point I am almost considering it non-nonnegotiable for my workflows.

1 Like
2

This is the one community maintained solution I heard of, not sure about others:

My bet is in future we’ll see some open source projects that provide generic MCP by just being integrated with Vikunja DB - makes things easier.

Maybe there are such now already?

3

Hey, yeah I am using that one currently but it has issues. Was hoping there would be a first-party one created by Vikunja devs to minimize the issues. IMO, the one you linked is currently the best one available.

4

:thinking: , looks like I was wrong. It might be the client that I am using with MCP will do some more digging, but the version I had before worked with the application I was using but the new 0.2.x version doesn’t, works fine in Roocode though. Guess I will complain less and look more into it. Thanks.

5

Found the root issue.
I had a custom version and I was using the configuration

  "vikunja": {
    "command": "node",
    "args": ["/path/to/vikunja-mcp/dist/index.js"],
    "env": {

Switched to main brain branch and used

  "vikunja": {
    "command": "npx",
    "args": ["-y", "@democratize-technology/vikunja-mcp"],

and now everything works. I also see the labels works now!
My opinions have changed. I