MCP server for Azure Cosmos DB using the Go SDK

Created By
abhirockzza year ago
Sample implementation of a MCP server for Cosmos DB built using the Go SDK
Overview

What is MCP server for Azure Cosmos DB?

MCP server for Azure Cosmos DB is a sample implementation that allows developers to interact with Azure Cosmos DB using the Go SDK. It serves as a model context protocol (MCP) server that facilitates CRUD operations on Cosmos DB.

How to use MCP server for Azure Cosmos DB?

To use the MCP server, clone the repository from GitHub, build the project using Go, and configure the server with the necessary permissions and authentication details. You can then run the server and connect it with tools like VS Code Insiders in Agent Mode.

Key features of MCP server for Azure Cosmos DB?

  • Sample implementation of MCP server using Go SDK
  • Supports CRUD operations on Azure Cosmos DB
  • Easy configuration with JSON files
  • Integration with development tools like VS Code

Use cases of MCP server for Azure Cosmos DB?

  1. Developing applications that require interaction with Azure Cosmos DB.
  2. Testing and debugging Cosmos DB operations in a local development environment.
  3. Learning and experimenting with the Go SDK for Azure Cosmos DB.

FAQ from MCP server for Azure Cosmos DB?

  • What programming language is used for the MCP server?

The MCP server is implemented in Go (Golang).

  • Do I need an Azure account to use this project?

Yes, you need an Azure account with permissions to access Cosmos DB.

  • Can I run this server locally?

Yes, you can run the MCP server locally after proper configuration.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
abhirockzz
Star
2
Language
Go
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)

a day ago
Crevio

2 days ago