Mongodb

Created By
srca year ago
Overview

What is MongoDB MCP?

MongoDB MCP is a collection of Model Context Protocol (MCP) servers designed to enhance AI assistants like Claude by providing unique functionalities.

How to use MongoDB MCP?

To use MongoDB MCP, set up the server by configuring the MongoDB URI and running the provided Docker command. Each server has specific setup instructions available in their respective directories.

Key features of MongoDB MCP?

  • Integration with various APIs for real-time data access
  • Support for web, news, image, video, and maps search
  • Web scraping capabilities to extract content from web pages
  • Location services for GPS-aware searches
  • Extensible architecture for adding new specialized servers

Use cases of MongoDB MCP?

  1. Enhancing AI assistants with real-time information retrieval
  2. Providing structured data access for various applications
  3. Enabling specialized functions like media processing and database interactions

FAQ from MongoDB MCP?

  • What is the purpose of MCP servers?

MCP servers allow AI assistants to interact with external tools and APIs, extending their capabilities beyond their training data.

  • How can I contribute to the MongoDB MCP project?

Contributions are welcome! You can fork the repository, create a feature branch, and submit a pull request with your ideas or improvements.

Server Config

{
  "mcpServers": {
    "mongodb": {
      "command": "docker",
      "args": [
        "run",
        "-e",
        "MONGODB_URI=mongodb://username:password@host:27017/mydatabase",
        "mongodb-mcp-server"
      ],
      "env": {
        "MONGODB_URI": "mongodb://username:password@host:27017/mydatabase"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
src
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago