Skip to content

docs: add mongoDB link for crewAI implementation - #6721

Open
tmcneil-mdb wants to merge 1 commit into
crewAIInc:mainfrom
tmcneil-mdb:docs/update-memory-page
Open

docs: add mongoDB link for crewAI implementation#6721
tmcneil-mdb wants to merge 1 commit into
crewAIInc:mainfrom
tmcneil-mdb:docs/update-memory-page

Conversation

@tmcneil-mdb

Copy link
Copy Markdown

Summary

Added a reference to the MongoDB StorageBackend implementation in the Memory concept page to help users discover a production-ready option for persisting CrewAI Memory beyond the default local LanceDB store. The link points to the MongoDB's setup tutorial.

Validation

  • Previewed the changes locally with Mintlify
  • Confirmed the updated page renders correctly
  • Ran the Mintlify broken-link check

Copilot AI review requested due to automatic review settings July 29, 2026 20:17
@coderabbitai

coderabbitai Bot commented Jul 29, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 47a030be-5759-4177-b4c5-5cd356969381

📥 Commits

Reviewing files that changed from the base of the PR and between d52d0a1 and 1b62497.

📒 Files selected for processing (1)
  • docs/edge/en/concepts/memory.mdx

📝 Walkthrough

Walkthrough

The custom storage backend guidance now points to a MongoDB StorageBackend implementation and production setup tutorial.

Changes

Memory storage documentation

Layer / File(s) Summary
Custom backend guidance
docs/edge/en/concepts/memory.mdx
The Storage Backend section now links to MongoDB implementation guidance for production deployments.

Suggested reviewers: copilot

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title matches the main change by calling out the MongoDB link added to the CrewAI memory docs.
Description check ✅ Passed The description accurately describes the MongoDB StorageBackend reference and the validation performed.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Ready to approve

The change is a straightforward documentation update with correct formatting and a clearly scoped external reference link.

This review doesn't count toward merge requirements. Sign up for the private preview to control whether Copilot approvals count.

Pull request overview

Adds a discoverability link on the Memory concept page to point users to MongoDB’s production-ready StorageBackend implementation and setup tutorial, complementing the default local LanceDB storage option.

Changes:

  • Updates the “Storage Backend” section to include an external link to MongoDB’s CrewAI Memory StorageBackend tutorial for production deployments.
File summaries
File Description
docs/edge/en/concepts/memory.mdx Adds a MongoDB tutorial link as a production-oriented StorageBackend option in the Memory docs.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 0
  • Review effort level: Low

We're testing this review assessment. Please use 👍 or 👎 to tell us if it's correct.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants