OlaDigital
ES

Connect your first tool to Claude via MCP in ten minutes

MCP is the standard plug between AI assistants and external tools. With this recipe you connect the first one, understand what it can and cannot do, and are ready to connect your own.

Level
Low code
Requires a simple automation or an API call.
Time
Half an hour, including the first conversation with the connected tool
Published

What it costs

Zero: the MCP documentation is open, many servers are free and custom connectors are available on claude.ai plans and in Claude Code. Third-party servers may have their own pricing.

guided mode // I ask, you answer

ready to start

Do it with me, step by step

I will ask you 6 questions about your business, use your answers to get the prompt ready to copy, and then walk you through the 5 steps, one at a time. Like a Thermomix: you just answer and move on.

Also from Claude or ChatGPT with the Master Cookbook MCP: say "start the recipe conectar-tu-primera-herramienta-por-mcp".

Who it is for

Anyone who already uses Claude or ChatGPT daily and wants the AI to do things outside the chat: read their database, check their calendar, look up their cookbook, without waiting for someone to build a custom integration.

The problem

Every tool has its own API and every integration is a project. The assistant knows a lot but cannot touch anything in your operation, so you end up copying and pasting between windows.

What changes

An assistant that, in the same conversation, queries or acts on one of your tools through a standard connector. According to the source, MCP works like a universal port: it is defined once and works for any client that speaks it, whether Claude, Cursor or another.

Ingredients

  • Claude on the web or desktop with access to connectors, or Claude Code in your terminal
  • The address of an MCP server to test with (for example, the Recetario Magistral server: https://oladigital.cl/mcp)
  • Twenty minutes without interruptions

Step by step

  1. 1

    Understand the three pieces

    According to the source, MCP defines a client (your assistant), a server (the tool) and a protocol between the two. The server offers tools, resources and prompts; the client discovers and uses them. You do not need more theory to get started.

  2. 2

    Add the connector

    In Claude: Settings, Connectors, Add custom connector, paste the server address. In Claude Code: `claude mcp add --transport http name "https://address"`. If the server requires a key, it goes in the address or in the header, as the server indicates.

  3. 3

    Ask it to list what it can do

    Type: "what tools do you have available from connector X?". You will see the names and descriptions. That list is the tool's manual.

  4. 4

    Do a real task in the same conversation

    For example, with the cookbook connected: "find a recipe for sorting support tickets and guide me step by step". Watch how the assistant calls the tool and uses the response.

  5. 5

    Decide what to connect next

    Make a list of the three tools where you copy and paste the most today. Check whether an MCP server exists for each one; for most of the popular ones there already is.

The prompt

Replace what is in brackets with your company details, or use the guided mode above: it asks you and fills it in for you.

# Role
You are my patient technical guide. My role is [YOUR ROLE, FOR EXAMPLE "small business owner"] at [COMPANY NAME], I use [CLAUDE ON THE WEB, CLAUDE CODE OR ANOTHER CLIENT] and I want to connect my first tool via MCP without getting lost.

# Context
The tool I want to connect is: [NAME AND ADDRESS OF THE MCP SERVER]. My technical level: [LOW, MEDIUM OR HIGH]. What I want to achieve with it: [WHAT YOU WANT TO DO, IN ONE SENTENCE].

# Task
Guide me step by step, one step at a time: give me the instruction, wait for me to confirm I did it or tell you what happened, and only then move on to the next one. If something fails, help me read the error message before proposing something else.

# Output format
Each of your messages: a single step, with the exact text I should type or click, and one line saying what I should see if it worked. No long lists up front.

# Examples
Expected step: "Open Settings → Connectors → Add custom connector. Paste this address: ... You should see the connector with a green dot. Do you see it?".

What usually goes wrong

  • ✕Starting by building your own server. First connect one that already exists; understand the flow from the user's side and then build.
  • ✕Granting broad permissions right away. Connect read-only tools at first; the ones that write or delete come later, and carefully.
  • ✕Confusing MCP with an API. The API belongs to the tool; MCP is the standard that lets any assistant use it without custom code.

When not to use this recipe

If all you need is for the model to read a document, upload it as a file: do not set up a server for that. And do not connect tools with access to sensitive data without understanding what permissions you are giving them.

Source and real case

Cross-industry · integrations

The official documentation presents MCP as an open standard for connecting AI applications with external systems, comparing it to a universal port, and describes the client-server architecture with tools, resources and prompts. The recipe brings it down to the first connection by a person without a technical team, using the cookbook itself as the test server.

Official documentation:Introduction — Model Context Protocol · modelcontextprotocol.io

Last verified:Official Model Context Protocol introduction (modelcontextprotocol.io), read in full; the URL returned 200 on September 22, 2026.

MCPClaudeToolsIntegrations

Share it

If someone on your team could use this recipe, send it in one click. The suggested text copies itself.

LinkedInInstagram

Want to apply it in your business? Message Cristián directly.

Telegram
← Back to the cookbook