{"id":"streamnative-streamnative-mcp-server","name":"streamnative-mcp-server","homepage":null,"repo_url":"https://github.com/streamnative/streamnative-mcp-server","category":"devtools","subcategories":[],"tags":["mcp","model-context-protocol","kafka","pulsar","streaming","agent-integration","go","sse","stdio"],"what_it_does":"StreamNative MCP server that implements an MCP server interface for AI agents to manage and use StreamNative Cloud resources plus Apache Kafka and Apache Pulsar (admin and client operations). It supports both stdio and SSE transport modes and can connect to StreamNative Cloud using service-account authentication or to external Kafka/Pulsar clusters directly.","use_cases":["Letting LLM agents perform Kafka admin tasks (topics, partitions, consumer groups) and client tasks (produce/consume)","Letting LLM agents perform Pulsar admin tasks (tenants/namespaces/topics/schemas) and client tasks (produce/consume)","Managing messaging/connectivity resources from an agent via a standardized MCP interface","Running multi-session per-user Pulsar sessions over SSE using Bearer tokens"],"not_for":["Use as a general-purpose database/API when you only need HTTP REST/SDK integrations","Environments where you cannot securely provide long-lived service account keys or tokens to the server process","Production deployments without validating the underlying authz boundaries for each messaging operation"],"best_when":"You want an MCP-compatible bridge for agentic operations across Kafka/Pulsar (and optionally StreamNative Cloud) with a single standardized tool interface.","avoid_when":"You need a fully specified public REST/OpenAPI developer API surface (this is primarily an MCP server, stdio/SSE runtime).","alternatives":["Use Kafka/Pulsar native SDKs/tools directly from your agent (no MCP layer)","Build a custom MCP server that wraps Kafka/Pulsar SDKs with your own authz and error handling","Use other MCP servers/integration layers for messaging systems (if available in your ecosystem)"],"af_score":51.8,"security_score":54.0,"reliability_score":30.0,"package_type":"mcp_server","discovery_source":["github"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T15:31:40.958820+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":"/mcp (SSE path) or stdio (local transport)","has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["StreamNative Cloud service account key file (admin role mentioned)","Pulsar Bearer token for external Pulsar (via --pulsar-token or SSE Authorization: Bearer)","Kafka authentication (flags for SASL_SSL/PLAIN plus optional TLS CA/certs/keys; schema registry auth options)"],"oauth":false,"scopes":false,"notes":"Auth model is driven by transport/runtime flags: StreamNative Cloud uses a service account key file; external Pulsar via token; external Kafka via SASL/TLS flags. SSE multi-session mode requires Authorization: Bearer <token> per request."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information provided in the supplied content; Open-source project likely, but StreamNative Cloud/Kafka/Pulsar usage costs depend on your infrastructure."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":51.8,"security_score":54.0,"reliability_score":30.0,"mcp_server_quality":80.0,"documentation_accuracy":70.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":55.0,"rate_limit_clarity":5.0,"tls_enforcement":70.0,"auth_strength":65.0,"scope_granularity":25.0,"dependency_hygiene":45.0,"secret_handling":60.0,"security_notes":"The README describes multiple authentication modes (service account key file for StreamNative Cloud; tokens for Pulsar; SASL/TLS options for Kafka). It also documents a strict 401 behavior for missing/invalid Bearer tokens in SSE multi-session Pulsar mode. However, supplied content does not specify fine-grained scopes, authorization boundaries per tool, secret handling/logging guarantees, or detailed security/error-code behavior.","uptime_documented":0.0,"version_stability":45.0,"breaking_changes_history":40.0,"error_recovery":35.0,"idempotency_support":"false","idempotency_notes":"No idempotency guarantees described for the operations/tools; messaging operations may or may not be idempotent depending on the specific tool semantics.","pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["MCP tool availability can change significantly based on the --features flag; agents may fail if required tools are disabled","For SSE multi-session Pulsar mode, requests require Authorization: Bearer <token>; missing/invalid tokens yield HTTP 401","In stdio mode there is no mention of per-user session separation; multi-session mode is SSE-only for external Pulsar"]}}