[lnbharath]

I definitely relate with your sentiment and I like your term "configuration bankruptcy"

on MCP, the mental model that clicked for me is "giving claude access to tools it can call" so that instead of copy pasting from your database or API, claude can just... query it

playwright MCP for me is godsend

[tanmay001]

Nice way to put it. Skills feel great for shaping how Claude works inside a repo, while MCP really shines when you want it to talk to “live” systems : databases, test runs, CI, all that external state.

[Lx1oG-AWb6h_ZG0]

I thought skills were supposed to help with “giving claude access to tools it can call”. When would one use MCP over skills?

[lnbharath]

skills are basically markdown files that teach claude how to do something. they live in your repo and load on demand.

MCP is for when you need claude to actually interact with external systems like querying a database, hitting an API, etc...

[tstrimple]

I've not explicitly used skills or MCP, but have had zero issues with Claude calling apis via curl as an example. I'm not sure what the MCP server or skill is actually enabling at this point. If I wanted CC to talk to SQL Server, I'd have it open a nix-env with the tools needed to talk to the database. One of my primary initial claude.md entries has to do with us running on NixOS and that temporarily installing tools is trivial and it should do things in the NixOS way whenever possible. Since then it has just worked with practically everything I've thrown at it. Very rarely do I see it trying to use a tool that isn't installed anymore. CC even uses my local vaultwarden where I have a collection of credentials shared with it. All driven through claude.md.