---
title: "Discussion on \"MCP Explained: Tools, Resources, Prompts, and Protocol Compatibility\" | Hashnode"
description: "Discussion on \"MCP Explained: Tools, Resources, Prompts, and Protocol Compatibility\". Understand MCP hosts, clients, servers, tools, resources, prompts, and version compatibility without confusing discovery with permission."
url: "https://hashnode.com/posts/mcp-explained-tools-resources-prompts-and-protocol-compatibility/6afc08bb094539204a217bf1"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [MCP Explained: Tools, Resources, Prompts, and Protocol Compatibility](https://blog.sant.sh/mcp-explained-tools-resources-prompts-and-protocol-compatibility?utm_source=hashnode&utm_medium=feed)

Understand MCP hosts, clients, servers, tools, resources, prompts, and version compatibility without confusing discovery with permission.

2d ago · 6 min read · blog.sant.sh  
Updated 6h ago  
Read the article

-   [#ai-agents](https://hashnode.com/tag/ai-agents)
-   [#mcp](https://hashnode.com/tag/mcp)

## Written by

[Santosh](https://hashnode.com/@sant-sh)

@sant-sh

  
[View profile](https://hashnode.com/@sant-sh)

Software Engineer

I write about AI agents, harness engineering, and reliable software. My guides turn learning notes and small experiments into clear explanations, diagrams, and exercises you can try.

## Responses 1

Markdown supported · ⌘↵ to post

[OneLifeVibe](https://hashnode.com/@onelifevibe)

[2d ago](https://hashnode.com/posts/mcp-explained-tools-resources-prompts-and-protocol-compatibility/6afc08bb094539204a217bf1/comment/6afc199fed12bf99646c39f1)

The distinction between tools, resources, and prompts is the part I found most useful. Calling everything a tool hides whether an action changes anything, and that is where most of the risk sits. I also liked the warning about mixing examples from different protocol revisions. Pinning the revision and the SDK versions before drawing the sequence feels like extra work, and then it saves a long debugging session later. The diagnostic table is a good checklist to keep nearby when a call is rejected or a result lands on the wrong job.
