Python - Model Context Protocol

Been meaning to try it out

@Logan M Have you had an opportunity to check thie mcps out?

Checking out your latest agentic workflows to see if there's some room for an integratio

integration

@0xDrTuna I tried out MCP. but tbh, I couldn't figure out how to start a sever and client in two seperate processes 😆 All their examples with a server and client had that server + client starting in the same script... which kind of defeats the purpose

Generally open to integrations here if you have ideas. But I kind of gave up after that

Right? The release was so bad

And the example servers too

I got so tired of it I built the community around r/modelcontextprotocol to discuss it

I love llama-index, I saw on linkedin you just released the agentic workflow upgrade. Going to try it out now

I'm going to build it without mcp integration first, then going to see how it makes sense to integrate if it makes sense at all. I want to build something around Jira / Atlassian to try it out. Maybe mcp would make sense to integrate initiating the workflow from the Claude desktop. But the mcp community is divided on whether mcp is going to be playing any role in the future

anyone tried the LlamaCloud MCP server by @marcusschiesser? https://github.com/run-llama/mcp-server-llamacloud. I followed instruction started the local server, added the server to claude_desktop_config.json with my llama cloud info. Claude desktop called the right get_information tool with the correct query, but returns error "Error executing code: MCP error -32603: Internal error".
{
"mcpServers": {
"llamacloud": {
"command": "node",
"args": [
"/Users/bj/mcp-server-llamacloud/build/index.js"
],
"env": {
"LLAMA_CLOUD_INDEX_NAME": "<MY_INDEX_NAME>",
"LLAMA_CLOUD_PROJECT_NAME": "<MY_PROJECT_NAME>",
"LLAMA_CLOUD_API_KEY": "<MY_API_KEY>"
}
}
}
}

Internal error usually means you can go read/look for the error on the server?