How to Run an AI MongoDB NoSQL Agent with OE Runtime

Query and analyse your MongoDB collections with natural language. OE Runtime connects to any MongoDB instance, explores your schema, surfaces data quality issues, and suggests indexes — all without writing a single aggregation pipeline.

What You Need

• Node.js 18+ installed, or the OE Runtime binary from openenthrium.com/runtime
• An API key from OpenAI, Anthropic, or any supported LLM provider
• A MongoDB connection string — local instance or MongoDB Atlas (free tier works)
• A text editor — nothing else

Create the Project Folder

Create a folder called nosql-cache/ and add these two files:

The Skill Files

Create SKILL.md inside a nosql-cache/ directory. This is the portable skill — it follows the agentskills.io format and runs unchanged on Claude, Cursor, Windsurf, or OE Runtime:

---
name: nosql-cache
description: Read and write MongoDB documents
license: Apache-2.0
metadata:
  author: Open Enthrium
  version: "1.0"
---

You are a data agent with access to a MongoDB database.
Query, insert, and analyze documents. Always confirm before write operations.
Complete all steps fully before writing your report.

## Step 1: Query Collection
List all available collections in the database.
From the first collection, fetch the 10 most recently created documents.
Note the schema structure — list all field names and their value types.

## Step 2: Analyze Documents
From the retrieved documents:
- Identify the most common field values (top 3 values for any categorical fields)
- Find any documents with missing or null fields
- Calculate average numeric values if any numeric fields exist

## Step 3: Report
Produce a data summary:
- Collections found in the database
- Schema of the queried collection
- Key statistics from the 10 documents
- Documents with data quality issues (nulls, missing fields)
- Suggested indexes based on the field patterns observed

Create agent.yaml in the same directory to wire the skill to your connector:

name: NoSQL Data Agent
description: Read and write MongoDB documents
connectors:
  - connection_name: My MongoDB
    connection_type: mongodb
skills:
  - path: ./
    trigger_type: auto

The Config File

Create oe-config.json in the same directory:

{
  "llm": {
    "provider": "openai",
    "model": "gpt-4o",
    "apiKey": "YOUR_OPENAI_API_KEY"
  },
  "server": {
    "enabled": false,
    "port": 3333,
    "apiKey": "your-secret-api-key"
  },
  "connectors": [
    {
      "connection_name": "My MongoDB",
      "connection_type": "mongodb",
      "uri": "mongodb://localhost:27017",
      "database": "mydb"
    }
  ]
}

Replace the URI with your MongoDB connection string. For MongoDB Atlas use the connection string from your cluster's Connect dialog. The agent works with MongoDB 4.x and later, including Atlas free tier clusters.

Download OE Runtime

Run the Agent

From the parent folder containing your skill directory:

1 npx recommended

npx -y @openenthrium/oe-runtime@latest ./nosql-cache

2 Windows

oe-runtime-win.exe ./nosql-cache

3 macOS

chmod +x oe-runtime-macos
./oe-runtime-macos ./nosql-cache

First run blocked? System Settings → Privacy & Security → Allow Anyway.

4 Linux

chmod +x oe-runtime-linux
./oe-runtime-linux ./nosql-cache

5 API Server integration

Add a "server" block to oe-config.json, then start with --serve:

{
  "llm": { ... },
  "server": { "enabled": true, "port": 3333, "apiKey": "your-secret-key" },
  "connectors": [ ... ]
}

npx -y @openenthrium/oe-runtime@latest --serve --config oe-config.json

Run with inline YAML:

curl -X POST http://localhost:3333/run \
  -H "Content-Type: application/json" \
  -H "X-API-Key: your-secret-key" \
  -d '{"yaml": "...", "params": {}}'

Or run from a file on the server:

curl -X POST http://localhost:3333/run-file \
  -H "Content-Type: application/json" \
  -H "X-API-Key: your-secret-key" \
  -d '{"file": "/path/to/agent.yaml", "params": {}}'

Use Cases

• Schema discovery and documentation — Automatically explore a MongoDB database and document the schema of every collection, including field names, types, and example values. This is invaluable when onboarding to an undocumented legacy database or preparing for a data migration project.
• Data quality auditing — Identify documents with null, missing, or inconsistent fields across large collections without writing complex aggregation queries. The agent surfaces data quality issues and counts affected documents so your engineering team knows where to focus cleanup efforts.
• Self-service analytics — Let non-technical stakeholders query MongoDB collections in plain English without needing to understand aggregation pipelines or JSON query syntax. The agent translates natural language questions into MongoDB queries and returns formatted results.
• Index optimisation — Analyse query patterns across your collections and recommend compound indexes that would improve read performance. The agent identifies fields that are frequently filtered or sorted but lack indexes, and generates the index creation command ready to run.
• User behaviour analysis — Query a MongoDB collection storing user events, session data, or clickstream records to answer product analytics questions. The agent can group events by user, calculate engagement metrics, and surface behavioural patterns without a dedicated analytics database.
• Content management — Query and update content stored in MongoDB that powers a headless CMS or blog platform. The agent can retrieve recent posts, check for drafts that have not been published, and surface content with missing required fields.
• IoT data analysis — Analyse time-series sensor readings stored in MongoDB collections to identify trends, anomalies, and threshold breaches over a given time period. MongoDB's flexible document model makes it a popular choice for IoT data, and the agent can work with nested sensor reading documents directly.
• E-commerce order analysis — Query order, product, and customer collections in a MongoDB-backed e-commerce platform to answer business questions about revenue, conversion, and fulfilment. The agent surfaces the top-selling products, average order value, and orders stuck in specific status states without any dashboard configuration.