Module
Module 3 of 7Lesson 1 of 1~17 min

MCP server, API integration, in-house tool or skill?

Lesson 1 of the module "MCP or something else?" in the course "Connect AI to your tools and data with MCP".

Take this lesson: your first course is freeSee the full syllabus

Lesson objective

By the end of this lesson, you will be able to choose between an MCP server, a direct API integration, an in-house tool and a skill for a given need, based on four questions (who is the host, is the flow fixed, how many integrations, access or know-how) and on the context cost.

Where it fits

MCP or something else?

For this need, do you want an MCP server, an API integration, an in-house tool or a skill?

Lessons in this module

  1. MCP server, API integration, in-house tool or skill? (this lesson)

What you will learn in the course

This lesson is part of the course Connect AI to your tools and data with MCP

  • Explain what MCP standardizes (host, client, server; tools, resources, prompts; transports; authorization) and what each element implies for a product.
  • Choose between an MCP server, a direct API integration, an in-house tool and a skill for a given need, and justify the choice.
  • Find, evaluate and connect an existing MCP server in a free client, with limited rights, and verify what it actually exposes.
  • Identify the risks specific to MCP (tool poisoning, rug pulls, injection through results, over-broad permissions, confused deputy, supply chain) and specify the matching guardrails.
  • Decide whether to expose your product as an MCP server and, if so, specify its scope (users, tools, rights, authentication, measurement).

Related courses