Academy → Using HermesOfficial documentation · clear explanation

MCP (Model Context Protocol)

بروتوكول MCP

Beginner28 minutes3 questions2026-08-09
The idea in one minute

Start with meaning, then move to detail.

This lesson explains MCP (Model Context Protocol) as part of getting started with Hermes correctly. You will learn what it does, when it matters, and the smallest safe test that proves it works.

If you are new

If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?

For hands-on use

For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.

For specialists

For advanced readers, inspect What MCP gives you, Quick start, Catalog: one-click install for Nous-approved MCPs, then verify failure modes and version compatibility.

What do you need first?

No prior experience is required; follow the steps on a safe test setup first.

What will you know?

A clear outcome before you read.

  • Understand MCP (Model Context Protocol) without assumed prior knowledge.
  • Separate the source description from what still needs testing in your environment.
  • Read the first command and identify its inputs and outputs before copying it.
Lesson terms

Short definitions before the details.

MCP
A standard way to expose external tools, resources, and services to an agent.
Provider
The service that runs or provides access and authentication to a model.
Tool
A structured action the agent can call to read or change something.
Official page description

Connect Hermes Agent to external tool servers via MCP — and control exactly which MCP tools Hermes loads

Topic map

What does the source say, and in what order?

  1. 01
    What MCP gives you

    Start here to understand the core idea or structure.

  2. 02
    Quick start

    Read this after the foundation, then connect it to the previous step.

  3. 03
    Catalog: one-click install for Nous-approved MCPs

    Read this after the foundation, then connect it to the previous step.

  4. 04
    Tool selection at install time

    Read this after the foundation, then connect it to the previous step.

  5. 05
    Trust model

    Read this after the foundation, then connect it to the previous step.

  6. 06
    Manifest version compatibility

    Read this after the foundation, then connect it to the previous step.

  7. 07
    Runtime $ENVVAR substitution

    Read this after the foundation, then connect it to the previous step.

  8. 08
    Updating tool selection later

    Read this after the foundation, then connect it to the previous step.

  9. 09
    Updating the catalog manifest

    Read this after the foundation, then connect it to the previous step.

  10. 10
    Two kinds of MCP servers

    Finish here to verify the result and special cases.

Examples from the official page

Copy only after you understand the effect.

mcp_servers: filesystem: command: "npx" args: ["-y", "@modelcontextprotocol/server-filesystem", "/home/user/projects"]
hermes chat
List the files in /home/user/projects and summarize the repo structure.
Try it now

Read the first command and identify its inputs and outputs before copying it.

Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.

Knowledge check

Three decisions before completion.

1. What is the source of truth when “MCP (Model Context Protocol)” changes?
2. What is the best way to apply this lesson?
3. What should happen before a step can modify files or an external account?