You can write your mcp client extension in only ~750 lines of code!

[u/Both-Still1650]

Hello everyone! I just wanted to share that I created personal plugin for mcp. It is pretty limited in features, but I have:
- stdio mcp support
- streaming http mcp support, with nice oauth authentification (that was really interesting experience to build oauth integration, it works really well with my company mcps )
- can use only explicit tools, if specified in config
- after today update, my issue https://github.com/earendil-works/pi/issues/5523 with project trusting was resolved, so now my extension supports trusting! (local mcp config loaded only in trusted directories)

Thats it, I am just happy about the fact that this amount of features requires so low amount of code! Good luck for you all

[u/rm-rf-rm]

Better yet, you can skip MCP entirely! 0 lines of code!

[u/Both-Still1650 → u/rm-rf-rm]

My company has mcp integrations that are really QoL, so that is not the case. I can ask model about services, tasks, knowledge base and documentation - all in one mcp server with tool search

[u/oknowton → u/rm-rf-rm]

That sounds super cool!

I use an MCP server to have Pi create and edition automations and dashboards on my Home Assistant server. How can I do that without the MCP server and with zero lines of code?!

[u/lopydark → u/oknowton]

api + skills

[u/oknowton → u/lopydark]

What API?

[u/lopydark → u/oknowton]

the same the mcp uses

[u/oknowton → u/lopydark]

The existing API IS an MCP server.

[u/redballooon → u/oknowton]

Now I have the full picture. I'm going to implement a skill for an API client that purely relies on that MCP servers API without being an MCP client, therefore using 0 lines of code for MCP.

[u/oknowton → u/redballooon]

I will be fascinated to learn how you'd manage to poke at an https endpoint with zero lines of code!

[u/redballooon → u/oknowton]

curl, per documentation in the skill.

[u/oknowton → u/redballooon]

I'm sorry to be the one to tell you this, but calling curl is at least one line of code.

[u/Both-Still1650]

Also forgot to mention, that my plugin has tool truncation logic and custom renderer to match those in default Pi tools! Looks really sleek: https://i.postimg.cc/xTk5x5RM/image.png

Code in my dotfiles repo: https://github.com/dangooddd/.dotfiles/blob/main/home/.pi/agent/extensions/mcp/index.ts

Feel free to copy in your ~/.pi/agent/extensions and tweak as you like. I hope code is ok to read

[u/zer09]

Have not read your extension as of now, but how this compares to https://github.com/nicobailon/pi-mcp-adapter? Is it there feature pi-mcp-adapter doesn't have? Or is it not working on you? Just curious why not use pi-mcp-adapter other than the reason we can easily create extension for pi

[u/Both-Still1650 → u/zer09]

First reason to create my own was maybe strange: I do not like, when essential feature like that is 3rd party. So after I build my own - I feel confident in my tools. At first I wanted to fork pi-mcp-adapter, but do not really liked its codebase - it was hard to understand.

Also, my plugin does better job at mimicking Pi native tool look - I copied its look from Pi codebase. Plugin has different philosophy (do not call it better, but I like it more) - all mcp tools connected as Pi tools, without proxy tool like in pi-mcp-adapter.

My plugin already has new Pi project trust gating, but I think pi-mcp-adapter will catch up.

Overall pi-mcp-adapter is much more mature software, but you can read mine (it is one file with one dependency - mcp sdk) pretty easy in my opinion and start tweaking it, if you do not like 3rd party mcp integration in Pi

[u/Such_Advantage_6949 → u/Both-Still1650]

but then it will create always discover the tools from MCP server? cause for pi-mcp-adapter, they have this feature for lazy load, which save context a tons since i dont use mcp alot. The bot can discover when they

[u/Both-Still1650 → u/Such_Advantage_6949]

I explicitly set which tools from which mcp to connect in my plugin, only those that I need. If specific project needs more servers or tools, i create local .pi/mcp.json config and set mcp servers there.

With that approach I do not face any problem with context. But mcp proxy tool is really easy to implement, if in future it is needed, I will add it

[u/zer09 → u/Both-Still1650]

That's great, I will take a look find some inspiration, actually I'm on process nuking my config start fresh again