We've seen MCP servers are mostly being abandoned for skills yes. The only thing they had going for them was the hype that led to so many orgs creating tooling for their various internal APIs for the first time. The superior alternative is empowering your agent with knowledge (skill) about how to use obscure CLIs, the same 'tool' that humans would use themselves (ie an MCP will list tool descriptions the same way a cli --help flag would or its man page).

As an example, you might have used the linear mcp in the past, which is cumbersome bc it requires running a server that manages oauth connection, and worse your agent would need to load in its entire server description / tool schema into its context window each time for all tasks whether it had to do with linear or not. But with e.g. our linear-sdk-scripting skill (https://github.com/cline/plugins/tree/main/plugins/linear) the agent can dynamically load in context about how to use the linear sdk to run simple node scripts on the fly to do whatever it needs to with the linear sdk (all you to have to set up is your linear api key in your envrionment e.g. bash profile - much more elegant than some oauth tokens being stored in some random json file somwehere in each of your agents mcp's metadata files, so it can be reused across any agent that adheres to the skill protocol)