E.V.

Added Google Workspace MCP

Ran into a few issues with this one. First the server is hosted locally but wasn’t packaged so i had to first clone the open source repo. This meant I also had to declare the current working directory. Another issue was that some parts of the Google Workspace schema didn’t sync well with Groq. So i had to clean the function names and I had to get rid of an attribute called pattern. Another Issue I had was that when I asked for the list of tools, my function was returning a pydantic list rather than a typical one.

But now it can access my Google Workspace and can make changes when I prompt it.

Next steps are to clean up the pipeline so there is a clear flow of events using a small routing model to pick either the LLM or the tool calling.

I began working on E.V. an AI assistant just like JARVIS from Ironman. However, the namesake is from the new Spiderman movie which inspired me to finally take this project on.

So far I have:

1. Implemented a simple chatbot using the Groq api
2. Added Speech to text and text to speech
3. Added in tool calling features
4. Made a script to pull tools from a locally hosted MCP
5. Added a feature to call tools from locally hosted MCPs