Training course · Model Context Protocol (MCP) · Internal Tools & Automation

Model Context Protocol (MCP) for Internal Tools and Automation

Build and connect MCP servers securely: tools, resources and prompts for Claude Code, Cursor, Copilot and your own AI agents.

Duration
2 days (14 hrs)
Format
Online or on-site
Language
German or English
Participants
open dates or exclusive for your team
Certificate
Certificate of attendance

Overview

“Model Context Protocol (MCP) for Internal Tools and Automation” is a hands-on course for roles such as Software developers maintaining internal applications and scripts, DevOps, SRE and platform teams and IT administrators with automation responsibilities. Rather than learning Model Context Protocol (MCP) in the abstract, you work on tasks from your daily routine – with examples, exercises and templates from Internal Tools & Automation.

The Model Context Protocol is an open standard that gives AI applications a uniform way to access external tools, data sources and workflows. Instead of building separate integrations for every assistant, you implement an MCP server once and use it in Claude Code, Claude Desktop, Cursor, GitHub Copilot, VS Code and your own agents. In this two-day course you learn the host, client and server architecture, the three core primitives of tools, resources and prompts, and the stdio and Streamable HTTP transports, applying each of them directly in your own code.

On day one you use the official TypeScript or Python SDK to build an MCP server that exposes internal APIs, databases or files to AI assistants in a controlled way, and you test it with the MCP Inspector. Day two covers remote servers, OAuth-based authorisation, security risks such as prompt injection and tool poisoning, and operations, logging and governance in an enterprise setting. You learn to write tool descriptions that models use reliably, and you leave knowing how to integrate MCP servers safely into your development and agent landscape.

Almost every company has a long backlog of small tools nobody gets round to building: admin interfaces for master data, scripts for recurring data reconciliation, Slack or Teams bots, report generators and glue between SaaS systems. With AI coding assistants and agents, internal tools like these can be built in hours rather than weeks. Developers, ops and platform teams therefore shift their focus from writing code to clear requirements, secure access and reliable operation. Internal tools in particular often hold far-reaching rights over production data and quickly become business-critical. In this course you learn to build internal tools and automations rapidly with AI, implement authentication and permissions correctly from the start and design solutions that stay documented, tested and maintainable.

The course is delivered live – either online in a virtual classroom or on-site in our training rooms in Munich, Salzburg, Berlin, Augsburg, Hanover, Bremen, Stuttgart and Kaiserslautern. We can also run it exclusively for your team.

Who is this course for?

  • Software developers maintaining internal applications and scripts
  • DevOps, SRE and platform teams
  • IT administrators with automation responsibilities
  • Operations and RevOps engineers
  • Business process automation teams

Typical challenges we address

  • A long backlog of internal tools that never get prioritised next to product work
  • Manual reconciliation between SaaS systems, spreadsheets and databases that is prone to error
  • Internal tools with excessive permissions, no logging and no clear owner
  • Undocumented scripts that only one person understands

What you will be able to do

  • You explain the MCP architecture and choose between tools, resources and prompts for each use case.
  • You develop your own MCP server in TypeScript or Python and test it systematically.
  • You connect MCP servers to Claude Code, Cursor, Copilot and custom agents.
  • You run remote servers using Streamable HTTP and OAuth-based authorisation.
  • Build internal tools, bots and automations with AI agents quickly and to a solid standard.
  • Implement authentication, permissions, logging and secrets management correctly from the outset.
  • Design automations that are documented, testable and operable, so they do not depend on individual people.

Course outline

Day 1

Module 1 Architecture and core concepts
  • Roles of host, client and server and the lifecycle of a connection
  • JSON-RPC messages, capability negotiation and notifications
  • Tools, resources and prompts: choosing the right primitive
  • Client features such as sampling, roots and elicitation at a glance
Module 2 Building your own MCP server
  • Setting up a server with the official TypeScript or Python SDK
  • Defining tools cleanly with JSON Schema for inputs and outputs
  • Exposing resources and resource templates for documents, records and configuration
  • Testing and debugging with the MCP Inspector and meaningful error messages
Module 3 Connecting to Claude Code, Cursor, Copilot and agents
  • Configuring local stdio servers and remote servers in clients
  • Project-level and user-level configuration, approvals and permissions
  • Writing tool descriptions that models reliably select correctly
  • Integrating MCP servers into custom agents built with the Claude Agent SDK or OpenAI Agents SDK
Module 4 Transport, authorisation and operations
  • Streamable HTTP, session management and stateless servers
  • OAuth-based authorisation, token validation and integration with existing identity providers
  • Deploying as containers, on serverless platforms or behind a gateway
  • Logging, monitoring, rate limiting and versioning tool interfaces

Day 2

Module 5 Security and governance
  • Threats: prompt injection via tool results, tool poisoning, confused deputy
  • Least privilege, confirmation requirements and sandboxing
  • Reviewing and approving third-party servers within the organisation
  • Data protection, logging of personal data and requirements under GDPR and the EU AI Act
Module 6 Practice lab: Internal Tools & Automation
  • Generating admin interfaces
  • Automating data reconciliation
  • Chat bots for teams
  • Automating ops runbooks
  • Generating reports and exports
  • Building agent workflows
Module 7 Data protection, quality & transfer to daily work
  • Internal tools often access employee, customer and production data: you learn to grant permissions on a least-privilege basis, keep secrets in vaults rather than code, log access and take GDPR and works council requirements into account for tools that touch employee data.
  • Ground rules for safe AI use in your team
  • Checking results: facts, sources, tests and the four-eyes principle
  • Personal action plan for the next 30 days
  • Open questions, outlook and resources for further learning

Practical scenarios from your field

Generating admin interfaces

Create CRUD interfaces from a database schema or API with search, filters, validation, role-based permissions and an audit log, so business teams can maintain master data safely.

Automating data reconciliation

Write scripts that regularly pull data from CRM, ERP, ticketing systems and spreadsheets, reconcile it and report discrepancies, with retry logic, idempotency and clear error messages.

Chat bots for teams

Build Slack or Teams bots that answer status queries, trigger approvals, announce deployments or provide on-call information while only executing explicitly permitted actions. Every action is logged with the user ID.

Automating ops runbooks

Turn recurring operational tasks such as user management, certificate renewal or log analysis into reviewed scripts and workflows, safeguarded with a dry-run mode and logging.

Generating reports and exports

Automatically prepare regular analyses from databases and APIs as PDF, spreadsheet or email, including scheduling, parameters and traceable data sources. Manual copy-and-paste between systems disappears entirely.

Building agent workflows

Connect AI agents to tools such as the ticketing system, knowledge base and internal APIs, for example via MCP, to pre-qualify requests, gather data and prepare drafts for human approval.

Possible hands-on projects

Onboarding automation

A workflow that creates accounts in several systems for new starters, assigns groups and sends the line manager a checklist of outstanding steps.

Licence overview

An internal dashboard that pulls usage data from SaaS tools, flags unused licences and shows costs per team at a glance.

Deployment bot

A chat bot that announces deployments, summarises changes from pull requests and notifies the right people when a pipeline fails.

Prerequisites

Solid programming skills in TypeScript/JavaScript or Python and a basic understanding of HTTP APIs and JSON. Some experience using AI assistants in day-to-day development is helpful. You have programming experience in a language such as Python, TypeScript or Go and know the basics of APIs, databases and the command line.

Technical requirements

A laptop with Node.js or Python, Git and a code editor, plus access to at least one MCP-capable client such as Claude Code, Claude Desktop, Cursor or VS Code with Copilot.

Data protection & compliance

Internal tools often access employee, customer and production data: you learn to grant permissions on a least-privilege basis, keep secrets in vaults rather than code, log access and take GDPR and works council requirements into account for tools that touch employee data.

Suggested dates

All dates are suggestions – your preferred date is always possible.

  • Mon, 23 November 2026 – Tue, 24 November 2026 Online Request
  • Mon, 30 November 2026 – Tue, 1 December 2026 Augsburg Request
  • Mon, 14 December 2026 – Tue, 15 December 2026 Online Request
  • Mon, 11 January 2027 – Tue, 12 January 2027 Online Request
  • Wed, 27 January 2027 – Thu, 28 January 2027 Kaiserslautern Request
  • Tue, 2 February 2027 – Wed, 3 February 2027 Online Request

Frequently asked questions

Why would I need my own MCP server?

Whenever AI assistants need access to internal systems such as ticketing tools, databases, documentation or line-of-business applications. Your own server defines precisely which actions and data are available and can then be reused across several clients. That avoids isolated one-off integrations and keeps access firmly under your control.

Which programming language does the course use?

You can choose between TypeScript and Python, both of which have official SDKs. The concepts are identical and all exercises are available in both versions. Developers working in other languages still benefit, because the protocol is language-agnostic and SDKs for other languages follow a similar structure.

How secure is MCP for enterprise use?

The protocol provides mechanisms for authorisation and permissions, but real-world security depends on implementation and operations. Risks such as prompt injection through tool results or over-privileged servers are genuine. We cover concrete countermeasures, approval processes for third-party servers and how to handle personal data.

When is a custom internal tool better than an off-the-shelf product?

When a process is specific to your organisation, spans several systems or standard tools only fit after heavy customisation. AI cuts development cost considerably, but operation and maintenance remain. In the course you learn to weigh effort against benefit realistically and build tools that keep working with minimal upkeep.

How do we secure internal tools that were built quickly with AI?

With fixed guardrails: sign-in through your central identity provider, role-based permissions, no secrets in code, logging of every write action and a short review before go-live. These building blocks can be stored as a template so AI agents include them automatically in every new tool. You create exactly these templates in the course.

How much does “Model Context Protocol (MCP) for Internal Tools and Automation” cost?

The course costs a flat €949 plus VAT per participant – whether online or on-site. This includes 2 training day(s) with a live trainer, course materials, a lab environment and a certificate of attendance.

Can I suggest my own date?

Yes. Our suggested dates are just a guide. In the request form you can always describe your preferred date or period in free text – we check availability and confirm within one working day.

Is the course online or on-site?

Both are possible: live online in a virtual classroom or on-site in Munich, Salzburg, Berlin, Augsburg, Hanover, Bremen, Stuttgart or Kaiserslautern. We can also run the course exclusively for your team.

More courses for Internal Tools and Automation

More Model Context Protocol (MCP) courses

All 29 Model Context Protocol (MCP) courses

Model Context Protocol (MCP) · MunichModel Context Protocol (MCP) · SalzburgModel Context Protocol (MCP) · BerlinModel Context Protocol (MCP) · AugsburgModel Context Protocol (MCP) · HanoverModel Context Protocol (MCP) · BremenModel Context Protocol (MCP) · StuttgartModel Context Protocol (MCP) · KaiserslauternModel Context Protocol (MCP) · Online