dapr-mcp-server
OfficialExposes Dapr's building blocks as tools for AI agents, letting them work with a Dapr sidecar across state management, pub/sub, secrets, service invocation, actors, bindings, distributed locks, cryptography, and LLM conversation components. Tools register dynamically based on the Dapr components present in the deployment, and the server follows Dapr's hot-reloaded component set.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
dapr-mcp-server
A Model Context Protocol (MCP) server that exposes Dapr's building blocks as tools for AI agents.
What it is
dapr-mcp-server is a Go MCP server that fronts a Dapr sidecar and hands AI agents a curated set of tools over every Dapr building block: state, pub/sub, secrets, service invocation, actors, bindings, distributed locks, cryptography, and conversation components. Tools register dynamically from the live component set — if your deployment has no pub/sub broker, the pub/sub tools aren't exposed.
Two transports are supported: stdio for local IDE integrations (Claude Desktop, Cursor, VS Code, Claude Code) and streamable HTTP for remote or shared deployments. Every tool call is annotated with OpenTelemetry spans, metrics, and optional log export; requests can be gated by OIDC, SPIFFE, Dapr Sentry, or a hybrid of the three.
Full documentation lives at docs.dapr.io / developing-ai / mcp.
Related MCP server: Swagger/Postman MCP Server
Quick start
Run the binary next to a Dapr sidecar with dapr run (install it from Install):
dapr init
# stdio, for local MCP clients that launch the server themselves
dapr run --app-id dapr-mcp-server --resources-path resources -- dapr-mcp-server
# streamable HTTP, for remote clients
dapr run --app-id dapr-mcp-server --resources-path resources -- dapr-mcp-server --http :8080With --http, connect any MCP client to http://localhost:8080/. The container image is meant for Kubernetes, where the Dapr sidecar injector adds the sidecar through the dapr.io/enabled: "true" and dapr.io/app-id pod annotations. For the complete walk-through (components, auth, OTEL, verification), see the getting started guide.
Install
Method | Command |
Container |
|
Binary | Download from Releases and place on |
From source (Go 1.26.6+) |
|
The server is listed in the official MCP Registry as io.github.dapr/dapr-mcp-server, so MCP clients that browse the registry can install it as a container.
Configuration
The configuration guide has the full environment variable reference.
Flag | Default | Purpose |
| unset (stdio) | Serve streamable HTTP on this address instead of stdin/stdout. Health probes are served on |
|
| Probe |
| from | Address |
|
| Print the version and exit. |
Logs are written as JSON to stderr, so they never mix with the stdio transport on stdout. /readyz returns 503 while the Dapr sidecar is unreachable.
Settings specific to the HTTP transport:
Environment variable | Default | Purpose |
| unset (no CORS headers) | Origin allowed to call the server from a browser, for example |
Documentation
Page | Purpose |
What the server is, architecture, capabilities, when to use it | |
Install, configure components, run, verify | |
Schemas, inputs, outputs, and safety flags for every tool | |
Environment variables, flags, and transport settings | |
OIDC, SPIFFE, Dapr Sentry, hybrid mode | |
Traces, metrics, and logs |
AI coding agents contributing to this repo: see AGENTS.md. For human contributors: see CONTRIBUTING.md.
Tools at a glance
All tools, with links to their entries in the tool reference. Core tools are always registered; conditional tools register only when a matching Dapr component exists. The server follows components that Dapr hot-reloads: each time a client lists tools or calls get_components, it checks the sidecar, adds a building block's tools when its first component appears and removes them when its last one goes, and tells connected clients the tool list changed.
Category | Tool | Registration | Notes |
metadata | Core | Always call first | |
invoke | Core | Service-to-service HTTP invocation | |
actors | Core | Virtual-actor method call | |
state |
| Idempotent save | |
state |
| Read-only | |
state |
| Read-only; several keys | |
state |
| Destructive, idempotent | |
state |
| Atomic batch | |
pubsub |
| Not idempotent | |
pubsub |
| Adds headers/TTL | |
bindings |
| External-system I/O | |
secrets |
| Single secret | |
secrets |
| High-risk; bulk fetch | |
conversation |
| Delegate to a downstream LLM | |
crypto |
| RSA encrypt | |
crypto |
| RSA decrypt | |
lock |
| Distributed mutex | |
lock |
| Pair with |
Development
go build -o dapr-mcp-server ./cmd/dapr-mcp-server
go test -race ./...
golangci-lint run ./...See AGENTS.md for the full contributor / AI-agent playbook (build commands, tool-addition pattern, testing strategy, DCO flow).
Contributing
Contributions welcome — open issues via the issue templates, sign your commits per the DCO, and follow the pull request template. See CONTRIBUTING.md for the full workflow.
Security issues: do not open a public issue — follow the Dapr security disclosure process instead.
License
Apache 2.0 — see LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Discover, compare, route, and execute machine-accessible capabilities for AI agents.
Context and control for any AI. Agent identity, scoped access, and proof across tools.
214 tools for AI agents over one MCP endpoint: image, video, audio, 3D, data, storage, mail, GPUs.
AI Agent Utility Layer for agent safety, web monitoring, crypto research and tool discovery.
Related MCP Servers
- -licenseNot gradedqualityNot gradedmaintenanceDynamically exposes Python SDKs (Kubernetes, GitHub, Azure) through an agent-friendly gRPC interface. Enables interaction with cloud services and platforms using natural language by automatically converting SDK functionality into callable functions.-
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI agents to dynamically discover and interact with APIs through Swagger/OpenAPI specifications and Postman collections using a strategic four-tool approach. It streamlines API integration by providing universal tools for endpoint discovery, detailed request information, and authenticated execution.1-
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Azure AI Agent Service by automatically discovering agents and creating MCP tools for querying and managing agent workflows.1MIT
- AlicenseAqualityDmaintenanceExposes Azure AI Foundry agents, workflows, and AI Search vector-database capabilities as MCP tools, enabling natural language interaction with agents, semantic search, and index management.102MIT