MCP and Skills: what they actually do for a business

Two notions come up as soon as you move from a conversational assistant to an agent that does real work: connectors, which give it access to your systems, and skills, which package a reusable business procedure.

A connector grants access, not instructions

The connector defines what the agent can read and write in a system: your ERP, your document management system, your invoicing tool. It says nothing about what the agent should do with it. It is as much an access-rights question as a technical one, and IT has a say from this stage on.

A skill packages a procedure

A skill is one of your company's procedures, written once: how to put together an export file, how to format a summary note, which checks to run before sending a quote. The agent replays it identically, and you fix it in a single place.

The day a procedure changes, you update the skill, not the habits of ten people.

Two deployed examples

• An ERP connector plus a “consolidated inventory status” skill for a retail sales agent.
• A document management connector plus a “program summary note” skill for a project team at an international institution.

In both cases, the value comes not from the model but from formalizing the procedure. It is business work, not engineering work.