Back to Browse

Dapr MCP Server

by Dapr
Developer ToolsModerate5.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

Dapr state, pub/sub, bindings, secrets, locks, crypto, conversation, actors, invocation as MCP tools

About

Dapr state, pub/sub, bindings, secrets, locks, crypto, conversation, actors, invocation as MCP tools

Security Report

5.2
Moderate5.2Moderate Risk

The provided code is a Dapr MCP server with strong authentication options (OIDC, SPIFFE, Dapr Sentry), and the Sentry tests cover JWT validation thoroughly, including alg none, algorithm confusion, tampered payloads, and SPIFFE subject checks. The main concerns are the high-risk get_bulk_secrets tool, which exposes many secrets to an AI agent at once, and the unverified default auth behavior in HTTP mode, since only a truncated mock file and README were provided. Permissions match the server's purpose as a Dapr building-block gateway. Supply chain analysis found 5 known vulnerabilities in dependencies (0 critical, 3 high severity).

5 files analyzed · 9 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

database

Check that this permission is expected for this type of plugin.

secrets_access

Check that this permission is expected for this type of plugin.

message_queue

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

gRPC port of the Dapr sidecarOptional

Environment variable: DAPR_GRPC_PORT

Dapr API token, if the sidecar requires oneRequired

Environment variable: DAPR_API_TOKEN

Log level, written as JSON to stderrOptional

Environment variable: DAPR_MCP_SERVER_LOG_LEVEL

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-dapr-dapr-mcp-server": {
      "env": {
        "DAPR_API_TOKEN": "your-dapr-api-token-here",
        "DAPR_GRPC_PORT": "your-dapr-grpc-port-here",
        "DAPR_MCP_SERVER_LOG_LEVEL": "your-dapr-mcp-server-log-level-here"
      },
      "args": [
        "dapr-mcp-test"
      ],
      "command": "uvx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

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.

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 :8080

With --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

MethodCommand
Containerdocker pull ghcr.io/dapr/dapr-mcp-server:latest
BinaryDownload from Releases and place on PATH
From source (Go 1.26.6+)go install github.com/dapr/dapr-mcp-server/cmd/dapr-mcp-server@latest

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.

FlagDefaultPurpose
--http <addr>unset (stdio)Serve streamable HTTP on this address instead of stdin/stdout. Health probes are served on /livez, /readyz and /startupz.
--health-checkfalseProbe /livez of a running server and exit 0 if it answers 200, 1 otherwise. Used by the container HEALTHCHECK.
--health-check-addr <host:port>from --http, else localhost:8080Address --health-check probes. A wildcard host such as 0.0.0.0 is probed as localhost.
--versionfalsePrint 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 variableDefaultPurpose
DAPR_MCP_CORS_ORIGINunset (no CORS headers)Origin allowed to call the server from a browser, for example https://app.example.com. Set it only when a browser-based MCP client on another origin needs access.

Documentation

PagePurpose
OverviewWhat the server is, architecture, capabilities, when to use it
Getting startedInstall, configure components, run, verify
Tool referenceSchemas, inputs, outputs, and safety flags for every tool
ConfigurationEnvironment variables, flags, and transport settings
AuthenticationOIDC, SPIFFE, Dapr Sentry, hybrid mode
ObservabilityTraces, 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.

CategoryToolRegistrationNotes
metadataget_componentsCoreAlways call first
invokeinvoke_serviceCoreService-to-service HTTP invocation
actorsinvoke_actor_methodCoreVirtual-actor method call
statesave_statestate.*Idempotent save
stateget_statestate.*Read-only
statedelete_statestate.*Destructive, idempotent
stateexecute_transactionstate.*Atomic batch
pubsubpublish_eventpubsub.*Not idempotent
pubsubpublish_event_with_metadatapubsub.*Adds headers/TTL
bindingsinvoke_output_bindingbindings.*External-system I/O
secretsget_secretsecretstores.*Single secret
secretsget_bulk_secretssecretstores.*High-risk; bulk fetch
conversationconverse_with_llmconversation.*Delegate to a downstream LLM
cryptoencrypt_datacrypto.*RSA encrypt
cryptodecrypt_datacrypto.*RSA decrypt
lockacquire_locklock.*Distributed mutex
lockrelease_locklock.*Pair with acquire_lock

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.

Reviews

No reviews yet

Be the first to review this server!