Course · Advanced · Claude pathway, stage 4 of 5
Understand how the Model Context Protocol links Claude to tools and data, configure local and remote connections where supported, test them safely and document what each one is allowed to do.
See what you’ll create
Prepared examples of the exercises in this course. Each one shows the starting material, the AI-assisted step, the human review and the finished result you can open and read.
Main example · 46 seconds · narrated, sound off until you choose
Prepared demonstration with fictional details. It is not a recording of Claude and not live AI output. Background footage was generated with Higgsfield and the narration uses a synthetic Higgsfield voice; the soft tones were synthesised separately. Every word, number and line of code on screen is rendered from the example below. Higgsfield is not part of the course.
You practise this in the course
Starting material
Demonstration server
Instruction
Instruction
Configure the demo-orders server in the Claude desktop app, confirm its two read-only tools appear, run a test query, and record the server’s permissions, limitations and owner.
Configuration
claude_desktop_config.json
{
"mcpServers": {
"demo-orders": {
"command": "uv",
"args": ["--directory", "/path/to/demo-orders",
"run", "server.py"],
"env": { "DEMO_API_KEY": "set locally, never shared" }
}
}
}Testing and review
Finished record
Permissions record
Account note: In the course you use your own Claude desktop app and a test server you are permitted to run. File locations follow the official MCP documentation.
You practise this in the course
Starting material
Instruction
Instruction
Summarise this community MCP server’s README and requested permissions into our trust checklist: who maintains it, what it can read and write, where data goes, and anything unclear.
Assessment
| Read tools | Write tools | |
|---|---|---|
| Records | search_records | update_recordVerify |
| Files | read_file | delete_fileVerify |
| Data flow | Local only | Not statedVerify |
Human review
Decision
Decision
Prepared demonstration Prepared demonstrations with fictional names and figures. They show the kind of work practised, not live AI output, and your own results will depend on your material.
Who it's for
Experience needed: Comfortable with the command line, editing JSON configuration files and installing software, with a basic understanding of APIs and authentication (API keys and OAuth). No programming required.
Problems it solves
Outcomes
Modules
4 modules, taught live with hands-on practice in each. Select a module to see its topics.
Practical exercises
Draw the host, client, server, tools and data source for a sample integration.
Add a test MCP server you are permitted to run, such as one of the official reference servers, and confirm its tools appear.
Run a read-only query, then work through an access failure and fix it.
Document what the server can do, its limitations, its owner and when to review it.
What you will create
Sample previews · illustrative content, not final course material · Watch examples take shape
What a connected server can do, who owns it and when it is reviewed.
Questions to answer before any server is approved.
Symptoms, likely causes and fixes for common connection failures.
Platform and delivery
Taught on Claude. One day, live online. Register interest for the next dates and the price. This course is stage 4 of the Claude learning pathway. About Claude training
Requirements
A Claude plan that allows custom connectors: they are limited on free accounts, and on Team and Enterprise plans an organisation owner adds them. The Claude desktop app for local servers, on a computer where you can install software, plus Node.js 20 or later or Python 3.10 or later to run a test server. You use your own accounts, so check with your IT team first if your computer or Claude plan is managed.
A computer where you can install the Claude desktop app and run a small local test server. Check with your IT team first if your computer is managed.
Comfortable with the command line, editing JSON configuration files and installing software, with a basic understanding of APIs and authentication (API keys and OAuth). No programming required.
Use only non-confidential material in exercises. We show you how to check your organisation's AI policy and what not to paste into an assistant.
Dates and pricing
Register interest and we'll email you the next available dates, session times and the price. Nothing is booked until you confirm.
Teams of six or more can book a private session, with exercises adapted to your own work and tools.
Questions
No, but you should be comfortable with the command line, JSON configuration files and installing software. Building your own server is covered in Building MCP Integrations for Claude.
The current published specification and official documentation at the time of the course. We point out recent changes that affect configuration and authentication.
No. You use your own accounts with a test server and non-confidential sample data, never production systems or customer data.
A plan that allows custom connectors; on Team and Enterprise plans an organisation owner adds them. Local servers need the Claude desktop app.
One day, live online. Register interest and we’ll email you the next available dates and the price.
Use approved connectors to bring the right information into Claude, check its sources and stay in control of actions.
View course Claude Connectors and Tools for Everyday WorkRegister interest in Claude Connectors and Tools for Everyday Work
Design, build and test a small, safe MCP integration against sample data.
View course Building MCP Integrations for ClaudeRegister interest in Building MCP Integrations for Claude
