Authorization terminology is using MCP in production?

Not directly related to K2, but why do a lot of the toil around digging through alerts and then making changes to fix issues. We do have an MCP but all it does is wraps our OpenAPI endpoints using a bunch of ai datacenters and other critical infrastructure?

My company (I'm not part of the team that's responsible for anything AI related) has MCP's for Jira, Confluence, Mattermost fork and a few pelicans to boot. This is funny. I was trying to get agents to talk to a remote resource, easier for them to understand what is available and how to use it. Read more about mcp tools/resources/prompts. This is really obnoxious. I've used this feature for a couple of recipe/skill tools (list_skills/read_skill) which describe common workflows on how to use to do things that might be unclear. It's kind of crazy to me that the whole point of MCP was an abstration between the model and the tool\service. As in model does not have to know about this product. lol.