| ▲ | anotherpaul 5 hours ago | |
If I understand correctly MCP is the interface to connect any API to LLMs. Now a lot of people use it to add context to their model. And also tool calls? I am using continue.dev not Claude but I imagine this tech stack will be ported everywhere. As a python Dev I don't quite yet understand though how and what service I should be running. Or be using. Tbh. Can anyone ELI5? | ||
| ▲ | podviaznikov 30 minutes ago | parent | next [-] | |
I’ve made one MCP server for fun https://altonote.com/. it allows publishing any text or claude artifact directly from the claude. I have made it mostly for fun and as an experiment to try what is possible. | ||
| ▲ | beatthatflight 4 hours ago | parent | prev | next [-] | |
easiest one to get going with is to add the Playwright MCP. As a python dev you might have used it to do test automation? Anyway, it gives your tool eg Cursor, Claude Code access to the browser and automation using playwright. Meaning it can literally load a page to confirm its own change just had the desired effect. The blender one is also fun as a starting point, if you do any 3d modelling (or even if you don't). | ||
| ▲ | jasonjmcghee 2 hours ago | parent | prev [-] | |
You can give LLMs useful tools to have more rich interactions with them - help them help you more. They're also fun and easy to build. Here's one I made - it wraps the vscode debugger: https://github.com/jasonjmcghee/claude-debugs-for-you I've specifically tested it with continue.dev so it might serve as a useful example / template. | ||