MCP (Model Context Protocol) is an open standard for connecting AI applications such as Claude to tools and data sources. A configured connector can expose selected capabilities from a database, file store, project tracker or internal API, subject to authentication and access permissions.
The proposed module covers the concept, permission model and a connector demonstration. Availability depends on the account, organisation policy and connected system; confirm the setup and depth for your batch.
The copy-paste ceiling
Pasting or uploading information can be enough for a one-off task. A connector can let the assistant work with an approved system directly, while keeping the access scope explicit.
Connect and use a connector
A proposed exercise: set up an available connector, inspect the tools and data it exposes, and run a bounded task. Confirm the demonstration and account requirements with the trainer.
Permissions come first
Check access scope, authentication and organisation policy before connecting company data. Use approved practice data and understand which actions require human review.
Connectors for everyday work
Files, drives, calendars and tickets connected to the assistant you already use, so context stops being something you assemble by hand each morning.
MCP servers for developers
The same protocol connects Claude Code to a database, an issue tracker or an internal API, so an agent working in your repository can also see the systems around it.
Building your own MCP server
Writing an MCP server is a development project. Discuss whether it belongs in an optional developer track or the Generative AI programme for your goals.