MCP and connected systems

Inhalt

MCP (Model Context Protocol) separates the host application, clients, servers, tools, resources, and prompts. This makes it easier to design systems where models can reliably access external capabilities without ad-hoc integration logic. In practice today, most production glue is still OpenAPI + HTTP — MCP is the emerging standard; both are worth knowing. Rough rule: ≤3 tools and one team → OpenAPI is fine. Many tools, multiple owners, tools you want to share across products → MCP starts paying for itself.

Beispiel: A campus assistant could connect to course documents, room data, and scheduling tools through clean interfaces — each a separate server with declared tools and resources.

Hast du das verstanden?

• [ ] You made one working call via OpenAPI AND one via MCP
• [ ] Your diagram names host, client, server, tool, resource correctly
• [ ] You logged at least one real request + response
• [ ] You can name one case where OpenAPI beats MCP for your situation
• [ ] You can explain in one sentence what you learned that you would tell a labmate tomorrow

Direkt ausprobieren

Diese Links öffnen die laufenden Demos auf n8n.32dots.de + dify.32dots.de.