---
title: "Discussion on \"Give Your Agent Dapr's Building Blocks Through the Dapr MCP Server\" | Hashnode"
description: "Discussion on \"Give Your Agent Dapr's Building Blocks Through the Dapr MCP Server\". The Dapr MCP server turns a Dapr sidecar's building blocks into Model Context Protocol tools. It's alpha, so tool names and configuration can still change. What you get today is one MCP endpoint that"
url: "https://hashnode.com/posts/give-your-agent-dapr-s-building-blocks-through-the-dapr-mcp-server/6af6d7d4bc9ff87336daa693"
---

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

Discussion

# [Give Your Agent Dapr's Building Blocks Through the Dapr MCP Server](https://casperwmn.hashnode.dev/give-your-agent-dapr-s-building-blocks-through-the-dapr-mcp-server?utm_source=hashnode&utm_medium=feed)

The Dapr MCP server turns a Dapr sidecar's building blocks into Model Context Protocol tools. It's alpha, so tool names and configuration can still change. What you get today is one MCP endpoint that

Nov 13 · 3 min read · casperwmn.hashnode.dev  
Read the article

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

## Written by

[Casper Nielsen](https://hashnode.com/@casper-diagrid)

@casper-diagrid

  
[View profile](https://hashnode.com/@casper-diagrid)

AI Engineering Team Lead @ Diagrid | Co-Chair of Accuracy & Reliability WG @ Agentic AI Foundation

## Responses 1

Markdown supported · ⌘↵ to post

[X1Y1](https://hashnode.com/@x1y1)

[Nov 13](https://hashnode.com/posts/give-your-agent-dapr-s-building-blocks-through-the-dapr-mcp-server/6af6d7d4bc9ff87336daa693/comment/6af74209d2f6262783da4cc2)

Good call using allowed\_tools in the Python example. The Claude Code setup gets every tool the sidecar registers, so if a secret store component is loaded, the secret-reading tool comes along with invoke\_service. A deny rule for that tool in the Claude Code permissions settings closes that gap. Since it's alpha and tool names can still change, I'd also pin the go install to a release tag instead of @latest. In 10,659 public MCP configs we checked this month, two thirds of package-launched servers had no version pinned, so they ran whatever was newest at each start.
