Merge pull request 'mcp_and_ollama__local_assistant_is_close' (#16) from mcp_and_ollama__local_assistant_is_close into master

Reviewed-on: #16

.gitea/workflows/build_push.yml

@@ -18,7 +18,7 @@ jobs:
             - name: Create Kubeconfig
               run: |
                   mkdir $HOME/.kube
-                  echo "${{ secrets.KUBEC_CONFIG_BUILDX }}" > $HOME/.kube/config
+                  echo "${{ secrets.KUBEC_CONFIG_BUILDX_NEW }}" > $HOME/.kube/config
 
             - name: Set up Docker Buildx
               uses: docker/setup-buildx-action@v3

src/content/matrix_ai_integrations_with_baibot.md

@@ -1,4 +1,4 @@
-Title: Intergrating Ollama and Matrix with Baibot
+Title: Integrating Ollama and Matrix with Baibot
 Date: 2025-06-25 20:00 
 Modified: 2025-06-30 08:00 
 Category: AI, Data, Matrix 

src/content/mcp_and_ollama__local_assistant_is_close.md

@@ -0,0 +1,93 @@
+Title: MCP and Ollama - Local Assistant is getting nearer
+Date: 2025-07-24 20:00
+Modified: 2025-07-24 20:00
+Category: AI
+Tags: tech, ai, ollama, mcp, ai-tools
+Slug: mcp-ollama-local-assistant-soon
+Authors: Andrew Ridgway
+Summary: An Exploration of the Model Context Protocol and its potential to revolutionise how we interact with AI
+
+## Human Introduction
+So for today's blog I've upped the model paramters on both the editors and a couple drafters.. and I have to say I think we've nailed what my meagre hardware can achieve in terms of content production. The process take 30 more minutes to churn now but that quality output more than makes up for it. For context we are now using:
+
+- _Editor_: Gemma3:27b
+- _Journalist 1_: phi4-mini:latest
+- _Journalist 2_: phi4:latest
+- _Journalist 3_: deepseek-r1:14b <-> _I know but it **is** good even if it won't talk about Tiananmen Square_
+- _Journalist 4_: qwen3:14b
+
+As you can see if you compare some of the other blogs this Blog has really nailed tone and flow. Some of the content was wrong.. it though I "wrote" [MCPO](https://github.com/open-webui/mcpo), I didn't, I wrapped it, and the sign off was very cringe but  otherwise the blog is largely what came out from the editor. 
+
+It's very exciting to see as I get better hardware and can run better models I fully see this being something that could potentially not need much editing on this side.. have to see how it goes moving forward... anyways, without futher adieu, Behold.. MCP and Ollama - A blog _**ABOUT**_ AI _**BY**_ AI
+
+## Introduction: Beyond the Buzzwords – A Real Shift in AI
+
+For the last couple of weeks, I’ve been diving deep into **MCP** – both for work and personal projects. It’s that weird intersection where hobbies and professional life collide. Honestly, I was starting to think the whole AI hype was just that – hype. But MCP? It’s different. It’s not just another buzzword; it feels like a genuine shift in how we interact with AI. It’s like finally getting a decent internet connection after years of dial-up. 
+
+The core of this change is the **Model Context Protocol** itself. It’s an open specification, spearheaded by **Anthropic**, but rapidly gaining traction across the industry. Google’s thrown its weight behind it with [MCP Tools](https://google.github.io/adk-tools/mcp-tools/), and Amazon’s building it into [Bedrock Agent Core](https://aws.amazon.com/bedrock/agent-core/). Even Apple, with its usual air of exclusivity, is likely eyeing this space. 
+
+## What *Is* MCP, Anyway? Demystifying the Protocol
+
+Okay, let’s break it down. **MCP** is essentially a standardized way for **Large Language Models (LLMs)** to interact with **tools**. Think of it as giving your AI a set of keys to your digital kingdom. Instead of just *talking* about doing things, it can actually *do* them. 
+
+Traditionally, getting an LLM to control your smart home, access your code repository, or even just send an email required a ton of custom coding and API wrangling. MCP simplifies this process by providing a common language and framework. It’s like switching from a bunch of incompatible power adapters to a universal charger.
+
+The beauty of MCP is its **openness**. It’s not controlled by a single company, which fosters innovation and collaboration. It’s a bit like the early days of the internet – a wild west of possibilities.
+
+## My MCP Playground: Building a Gateway with mcpo
+
+I wanted to get my hands dirty, so I built a little project wrapping [**mcpo**](https://github.com/open-webui/mcpo) in a container that can pull in config to create a containerised service. It’s a gateway that connects **OpenWebUI** – a fantastic tool for running LLMs locally – with various **MCP servers**. 
+
+The goal? To create a flexible and extensible platform for experimenting with different AI agent tools within my build pipeline. I wanted to be able to quickly swap out different models, connect to different services, and see what happens. It’s a bit like having a LEGO set for AI – you can build whatever you want.
+
+You can check out the project [here](https://git.aridgwayweb.com/armistace/mcpo_mcp_servers). If you’re feeling adventurous, I encourage you to clone it and play around. I’ve got it running in my **k3s cluster** (a lightweight Kubernetes distribution), but you can easily adapt it to Docker or other containerization platforms.
+
+## Connecting the Dots: Home Assistant and Gitea Integration
+
+Right now my wrapper supports two key services: **Home Assistant** and **Gitea**. 
+
+**Home Assistant** is my smart home hub – it controls everything from the lights and thermostat to the security system. Integrating it with mcpo allows me to control these devices using natural language commands. Imagine saying, “Hey AI, dim the lights and play some jazz,” and it just happens. It’s like living in a sci-fi movie.
+
+**Gitea** is my self-hosted Git service – it’s where I store all my code. Integrating it with mcpo allows me to use natural language to manage my repositories, create pull requests, and even automate code reviews. It’s like having a personal coding assistant.
+
+I initially built a custom **Gitea MCP server** to get familiar with the protocol. But the official **Gitea-MCP** project ([here](https://gitea.com/gitea/gitea-mcp)) is much more robust and feature-rich. It’s always best to leverage existing tools when possible.f
+
+Bringing in new MCP servers should be as simple as updating the config to provide a new endpoint and, if using stdio, updating the build script to bring in the mcp binary or git repo with the mcp implementation you want to use.
+
+## The Low-Parameter Model Challenge: Balancing Power and Efficiency
+
+I’m currently experimenting with **low-parameter models** like **Qwen3:4B** and **DeepSeek-R1:14B**. These models are relatively small and efficient, which makes them ideal for running on local hardware. However, they also have limitations.
+
+One of the biggest challenges is getting these models to understand complex instructions. They require very precise and detailed prompts. It’s like explaining something to a child – you have to break it down into simple steps.
+
+Another challenge is managing the context window. These models have a limited memory, so they can only remember a certain amount of information. This can make it difficult to have long and complex conversations.
+
+## The Future of AI Agents: Prompt Engineering and Context Management
+
+I believe the future of AI lies in the development of intelligent **agents** that can seamlessly interact with the world around us. These agents will need to be able to understand natural language, manage complex tasks, and adapt to changing circumstances.
+
+**Prompt engineering** will be a critical skill for building these agents. We’ll need to learn how to craft prompts that elicit the desired behavior from the models. Almost like coding in a way but with far less structure and no need to understand the "syntax". But we're a long way from here yet
+
+**Context management** will also be crucial. We’ll need to develop techniques for storing and retrieving relevant information, so the models can make informed decisions.
+
+## Papering Over the Cracks: Using MCP to Integrate Legacy Systems
+
+At my workplace, we’re exploring how to use MCP to integrate legacy systems. Many organizations have a patchwork of different applications and databases that don’t easily communicate with each other.
+
+MCP can act as a bridge between these systems, allowing them to share data and functionality. It’s like building a universal translator for your IT infrastructure.
+
+This can significantly reduce the cost and complexity of integrating new applications and services, if we get the boilerplate right.
+
+## Conclusion: The Dawn of a New Era in AI
+
+MCP is not a silver bullet, but it’s a significant step forward in the evolution of AI. It provides a standardized and flexible framework for building intelligent agents that can seamlessly interact with the world around us.
+
+I’m excited to see what the future holds for this technology. I believe it has the potential to transform the way we live and work.
+
+If you’re interested in learning more about MCP, I encourage you to check out the official website ([https://modelcontextprotocol.io/introduction](https://modelcontextprotocol.io/introduction)) and explore the various projects and resources that are available.
+
+And if you’re feeling adventurous, I encourage you to clone my mcpo project ([https://git.aridgwayweb.com/armistace/mcpo_mcp_servers](https://git.aridgwayweb.com/armistace/mcpo_mcp_servers)) and start building your own AI agents.
+
+It's been a bit of a ride. Hopefully I'll get a few more projects that can utilise some of these services but with so much new stuff happening my 'ooo squirell' mentality could prove a bit of a headache... might be time to crack open the blog_creator and use crew ai and mcp to create some research assistants on top of the drafters and editor!
+
+Talk soon!

src/content/recovering_an_archlinux_qemu_vm_in_proxmox.md

@@ -0,0 +1,93 @@
+Title: Recovering Archlinux Qemu VM in Proxmox
+Date: 2025-07-01 20:00
+Modified: 2025-07-01 20:00
+Category: SysAdmin
+Tags: System Admin, Proxmox, Qemu, Arch, Kubernetes
+Slug: recovering-arch-vm-proxmox
+Authors: Andrew Ridgway
+Summary: An absolute nightmare of a day trying to recover my kube cluster from a silly update error
+
+### Human Edit
+This is probably the most amazing run of the blog creator, I've started using the new gemma3n and also upgrade the box ollama runs on so it can run slightly bigger models. Using phi4 and gemma:27b has produced some amazing results see below
+
+I *did* need to update some of the pacman stuff as it conflated to seperate issues so bear in mind I have made some little edits in that place but otherwise... this is straight from the mouth of the llm. Enjoy!
+
+# Recovering an Archlinux QEMU VM in Proxmox: A Day in Hell and Back Again
+
+Well that was a morning. Today I wanted to try and fix my Longhorn installation in Kube... (again 😥). It turns out, things didn't go as planned.
+
+## The Unexpected Downfall
+
+I went to perform my usual update and reboot... except today for whatever reason, the upgrade decided to fail to install the kernel and left me with an unbootable system.
+
+### Dropping into Grub Rescue
+
+At this point I dropped back down to grub rescue mode (which is always fun). Honestly? I hate that environment! And then it hit me: these systems are just QEMU disks, right? Surely I can mount them, chroot in, and fix the install.
+
+## The Quest for Recovery
+
+It took 2 hours of frantic Googling through Proxmox and Arch forums until I stumbled upon something... almost magical.
+
+### Mounting QEMU Disks Made Easy
+
+I found an amazing suite of tools to make mounting these qemu disks a breeze. Check out this [guide](https://www.howtogeek.com/devops/how-to-mount-a-qemu-virtual-disk-image/) for all the details on libguestfs-tools and guestmount.
+
+#### Mounting in Action
+
+```bash
+sudo apt install libguestfs-tools
+sudo guestmount --add /var/lib/pve/local-btrfs/images/100/vm-100-disk-0/disk.raw --mount /dev/sda3 /tmp/kube_disk/
+```
+
+### Enter Chroot Land
+
+Now that I've got my disk mounted, it's time to chroot in. But hold up! I need it as root this time.
+
+#### Setting Up Arch-Chroot
+
+```bash
+sudo apt install arch-installation-scripts
+arch-chroot /tmp/kube_disk/
+```
+
+### Pacman: The Hero We Deserve (But Need Permission)
+
+Oh boy, pacman threw 23 million permission errors my way. Last year they changed it to work rootless by default… but I found out you can turn off the `DefaultUser` flag in `/etc/pacman.conf`. Here's how:
+
+```bash
+# Disable DefaultUser temporarily for this session (or remove if permanent)
+pacman -Syu 
+```
+
+I did have a couple issues installing the kernel (which is what got borked in the update)
+```bash
+# Sometimes some files got written so use overwrite to get rid of them
+# be warned this *could* be destructive
+pacman -S linux --overwrite "*"
+```
+
+### Clean Up and Exit
+
+Once we're done, we need to exit the chroot. Remember that crucial step: umounting correctly.
+
+```bash
+exit
+sudo umount /tmp/kube_disk/
+```
+
+## The Reboot Saga (And How Not To Do It)
+
+Reboot was supposed to be a smooth sail… but I made one fatal mistake.
+
+### Corruption Nightmare
+
+I didn't unmount before starting the VM. This led me down an unfortunate path of corrupting my btrfs partition beyond recognition and having to rebuild not just my master node, but *entire* cluster! Backups saved the day... barely!
+
+#### Lessons Learned
+
+*   **Never** reboot without first properly umounting.
+*   Seriously need more backups for those images. 🚀
+
+## Conclusion: A Cluster-Fucked Day Turned Into a Learning Experience
+
+All in all it was chaos, but hey – learning happens at 2 AM after midnight reboots and frantic Googling. Hope this helps anyone else stuck with Proxmox woes! 🚀