/mongodb-atlas-stream-processing

name: mongodb-atlas-stream-processing
description: "Manages MongoDB Atlas Stream Processing (ASP) workflows. Handles workspace provisioning, data source/sink connections, processor lifecycle operations, debugging diagnostics, and tier sizing. Supports Kafka, Atlas clusters, S3, HTTPS, and Lambda integrations for streaming data workloads and event processing. NOT for general MongoDB queries or Atlas cluster management. Requires MongoDB MCP Server with Atlas API credentials."
license: Apache-2.0
metadata:
  version: "1.0.0"
  user-invocable: "true"

MongoDB Atlas Streams

Build, operate, and debug Atlas Stream Processing (ASP) pipelines using four MCP tools from the MongoDB MCP Server.

Prerequisites

This skill requires the **MongoDB MCP Server** connected with:

• Atlas API credentials (`apiClientId` and `apiClientSecret`)

The 4 tools: `atlas-streams-discover`, `atlas-streams-build`, `atlas-streams-manage`, `atlas-streams-teardown`.

**All operations require an Atlas project ID.** If unknown, call `atlas-list-projects` first to find your project ID.

If MCP tools are unavailable

If the MongoDB MCP Server is not connected or the streams tools are missing, see [references/mcp-troubleshooting.md](references/mcp-troubleshooting.md) for diagnostic steps and fallback options.

Tool Selection Matrix

atlas-streams-discover — ALL read operations

| Action | Use when | |--------|----------| | `list-workspaces` | See all workspaces in a project | | `inspect-workspace` | Review workspace config, state, region | | `list-connections` | See all connections in a workspace | | `inspect-connection` | Check connection state, config, health | | `list-processors` | See all processors in a workspace | | `inspect-processor` | Check processor state, pipeline, config | | `diagnose-processor` | Full health report: state, stats, errors | | `get-networking` | PrivateLink and VPC peering details. Optional: `cloudProvider` + `region` to get Atlas account details for PrivateLink setup |

**Pagination** (all list actions): `limit` (1-100, default 20), `pageNum` (default 1). **Response format**: `responseFormat` — `"concise"` (default for list actions) or `"detailed"` (default for inspect/diagnose). **Parameter naming:** `inspect-processor`, `inspect-connection`, and `diagnose-processor` take `resourceName` (not `processorName` or `connectionName`).

atlas-streams-build — ALL create operations

| Resource | Key parameters | |----------|---------------| | `workspace` | `cloudProvider`, `region`, `tier` (default SP10), `includeSampleData` | | `connection` | `connectionName`, `connectionType` (Kafka/Cluster/S3/Https/Kinesis/Lambda/SchemaRegistry/Sample), `connectionConfig` | | `processor` | `processorName`, `pipeline` (must start with `$source`, end with `$merge`/`$emit`), `dlq`, `autoStart` | | `privatelink` | `privateLinkConfig` (project-level, not tied to a specific workspace) |

**Field mapping — only fill fields for the selected resource type:**

• **resource = "workspace":** Fill: `projectId`, `workspaceName`, `cloudProvider`, `region`, `tier`, `includeSampleData`. Leave empty: all connection and processor fields.
• **resource = "connection":** Fill: `projectId`, `workspaceName`, `connectionName`, `connectionType`, `connectionConfig`. Leave empty: all workspace and processor fields. (See [references/connection-configs.md](references/connection-configs.md) for type-specific schemas.)
• **resource = "processor":** Fill: `projectId`, `workspaceName`, `processorName`, `pipeline`, `dlq` (recommended), `autoStart` (optional). Leave empty: all workspace and connection fields. (See [references/pipeline-patterns.md](references/pipeline-patterns.md) for pipeline examples.)
• **resource = "privatelink":** Fill: `projectId`, `privateLinkConfig`. Note: PrivateLink is **project-level**, not workspace-level. `workspaceName` is not required — omit it. Leave empty: all connection and processor fields.

atlas-streams-manage — ALL update/state operations

| Action | Notes | |--------|-------| | `start-processor` | Begins billing. Optional `tier` override, `resumeFromCheckpoint` | | `stop-processor` | Stops billing. Retains state 45 days | | `modify-processor` | Processor must be stopped first. Change pipeline, DLQ, or name | | `update-workspace` | Change tier or region | | `update-connection` | Update config (networking is immutable — must delete and recreate) | | `accept-peering` / `reject-peering` | VPC peering management |

**Field mapping** — always fill `projectId`, `workspaceName`, then by action:

• `"start-processor"` → `resourceName`. Optional: `tier`, `resumeFromCheckpoint`, `startAtOperationTime` (ISO 8601 timestamp to resume from a specific point)
• `"stop-processor"` → `resourceName`
• `"modify-processor"` → `resourceName`. At least one of: `pipeline`, `dlq`, `newName`
• `"update-workspace"` → `newRegion` or `newTier`
• `"update-connection"` → `resourceName`, `connectionConfig`. **Exception: networking config (e.g., PrivateLink) cannot be modified after creation** — delete and recreate.
• `"accept-peering"` → `peeringId`, `requesterAccountId`, `requesterVpcId`
• `"reject-peering"` → `peeringId`

**State pre-checks:**

• `start-processor` → errors if processor is already STARTED
• `stop-processor` → no-ops if already STOPPED or CREATED (not an error)
• `modify-processor` → errors if processor is STARTED (must stop first)

**Processor states:** `CREATED` → `STARTED` (via start) → `STOPPED` (via stop). Can also enter `FAILED` on runtime errors. Modify requires STOPPED or CREATED state.

**Teardown safety checks:**

• **Processor deletion** → auto-stops before deleting (no need to stop manually first)
• **Connection deletion** → blocks if any running processor references it. Stop/delete referencing processors first.
• **Workspace deletion** → See detailed workflow below (lines 108-111).

atlas-streams-teardown — ALL delete operations

| Resource | Safety behavior | |----------|----------------| |