Azure Cosmos DB MCP CLient & Server

Created By
patrice-truonga year ago
Azure Cosmos DB MCP Client and Server
Overview

What is Azure Cosmos DB MCP Client & Server?

Azure Cosmos DB MCP Client & Server is a project that demonstrates how to create a client-server architecture using Azure Cosmos DB. It includes a frontend application built with NextJS that displays a product catalog and features an AI Assistant to help users find products and view past orders.

How to use Azure Cosmos DB MCP?

To use the project, set up an Azure Cosmos DB account, create a storage account, and follow the installation steps provided in the documentation. Clone the repository, install dependencies, configure environment variables, and run the server and frontend applications.

Key features of Azure Cosmos DB MCP?

  • Frontend application for product catalog display
  • AI Assistant for product search and order retrieval
  • Integration with Azure Cosmos DB for data storage
  • Step-by-step installation and configuration guide

Use cases of Azure Cosmos DB MCP?

  1. Building a product catalog for e-commerce applications.
  2. Implementing AI-driven product search functionalities.
  3. Managing orders and customer interactions in a cloud environment.

FAQ from Azure Cosmos DB MCP?

  • What technologies are used in this project?

The project uses NextJS for the frontend, Node.js for the server, and Azure Cosmos DB for data storage.

  • Is there any authentication in this project?

No, the project does not include authentication; user emails are hard-coded for demo purposes.

  • How can I contribute to this project?

You can contribute by submitting issues or pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
patrice-truong
Star
1
Language
TypeScript
License
MIT license

Recommend Servers

View All
Voyei

2 hours ago
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)

a day ago