skills.rest
fcakyon
fcakyonCOMMUNITY
Explore all skills by this author →
Website𝕏@fcakyonGitHub

mongodb-atlas-stream-processing

Manages MongoDB Atlas Stream Processing workspaces, connections, and processor pipelines via MCP tools.

1.1k|107|Updated Jul 9, 2025
Search Tags:#mcp#Kafka#DLQ#change streams#mongoDB#atlas stream processing#stream pipeline
One-click install
npx skills add https://github.com/fcakyon/claude-codex-settings --skill mongodb-atlas-stream-processing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mongodb-atlas-stream-processing
Source: https://github.com/fcakyon/claude-codex-settings/tree/main/plugins/mongodb-skills/skills/mongodb-atlas-stream-processing
Command: npx skills add https://github.com/fcakyon/claude-codex-settings --skill mongodb-atlas-stream-processing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Building and operating Atlas Stream Processing pipelines involves many failure modes: invalid pipeline stages, misconfigured Kafka or S3 connections, wrong region formats, silent zero-output processors, and unexpected billing. This Skill guides an AI agent through the four MongoDB MCP streams tools with validated field mappings, safety checks, and diagnostic decision trees so processors are created, debugged, and sized correctly.

Core Features & Use Cases

  • Full lifecycle management: Provision workspaces, create connections (Kafka, Atlas Cluster, S3, HTTPS, Kinesis, Lambda, SchemaRegistry), build processors with DLQ configuration, and start/stop/modify/delete them safely.
  • Pipeline validation and patterns: Enforces streaming-specific rules (no $$NOW, single terminal sink, required Kafka topic field) and provides ready-made patterns for windows, enrichment, schema validation, and chained multi-sink processors.
  • Diagnostics and sizing: Diagnose failing or zero-output processors with symptom-to-root-cause tables, and select the right SP tier using parallelism formulas and complexity scoring.
  • Use Case: A user asks to stream Kafka order events into an Atlas collection with a 5-minute tumbling window aggregation. The Skill validates connections, composes the pipeline with a DLQ, creates the processor, warns about billing, and verifies output.

Quick Start

Ask the AI to create an Atlas Stream Processing workspace and a processor that reads from your Kafka topic and merges results into an Atlas collection.

Frequently Asked Questions about mongodb-atlas-stream-processing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an Atlas Stream Processing processor with Kafka source?▼

Create a workspace, add a Kafka connection with bootstrapServers as a comma-separated string, then build a processor whose pipeline starts with $source including the required topic field and ends with $merge or $emit. Configure a DLQ and validate connections before creating the processor.

How to debug an Atlas Stream Processing processor with zero output?▼

Run the diagnose-processor action first, then classify the processor type since alert processors normally output little. For windowed pipelines, idle Kafka partitions often block window closure, so add partitionIdleTimeout to the Kafka $source stage.

Does Atlas Stream Processing support $$NOW in pipelines?▼

No, $$NOW, $$ROOT, and $$CURRENT are not available in streaming pipelines. Use the document's own timestamp field or _stream_meta metadata for event time instead.

Can one Atlas Stream Processing pipeline write to multiple sinks?▼

No, a single pipeline supports only one terminal sink such as $merge or $emit. For multiple destinations, chain processors by writing to an intermediate Atlas collection or Kafka topic and reading from it in a second processor.

What are the prerequisites for AWS S3 or Lambda connections in Atlas Stream Processing?▼

The IAM role ARN must be registered in the Atlas project via Cloud Provider Access before creating the connection. Use a dedicated least-privilege IAM role scoped to the specific buckets, streams, or functions the processor needs.

When is Atlas Stream Processing billed and how to avoid charges?▼

Billing is per-hour, calculated per-second, only while a processor is running, with no free tier. Stop processors to halt charges, or prototype for free using sp.process() in mongosh which runs pipelines ephemerally.

Related Skills

Explore More Software Engineering Skills→
re-sohailre-sohail

atlas-stream-processing

Provision and manage MongoDB Atlas Stream Processing workspaces, connections, and processors.

Community
Advanced
jeremylasne92-huejeremylasne92-hue

atlas-stream-processing

Provision and manage MongoDB Atlas Stream Processing workspaces, connections, and processors.

Community
Advanced
kgormankgorman

asp

Manage MongoDB Atlas Stream Processing workspaces, processors, connections, and collection checks via natural language requests.

Community
Advanced
coreweavecoreweave
7

patch-eks-system-tolerations

Patches system pods to tolerate the SUNK lock taint in EKS clusters.

Official
Intermediate