Mongo MCP Server

Created By
BootcampToProda year ago
A Spring Boot AI-powered Model Context Protocol Server for interacting with MongoDB
Overview

What is spring-boot-ai-mongo-mcp-server?

The spring-boot-ai-mongo-mcp-server is a Spring Boot application designed to serve as an AI-powered Model Context Protocol Server that facilitates interaction with MongoDB.

How to use spring-boot-ai-mongo-mcp-server?

To use this server, clone the repository from GitHub, configure your MongoDB connection settings, and run the Spring Boot application. You can then send requests to the server to interact with your data.

Key features of spring-boot-ai-mongo-mcp-server?

  • AI-powered model context management for MongoDB.
  • Easy integration with Spring Boot applications.
  • RESTful API for data interaction.

Use cases of spring-boot-ai-mongo-mcp-server?

  1. Managing AI model contexts in a MongoDB database.
  2. Building applications that require dynamic data interaction with AI models.
  3. Facilitating data storage and retrieval for AI applications.

FAQ from spring-boot-ai-mongo-mcp-server?

  • What programming language is used?

The server is built using Java and Spring Boot.

  • Is there any documentation available?

Yes, you can find the documentation in the GitHub repository.

  • How can I contribute to the project?

Contributions are welcome! Please check the contribution guidelines in the repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
BootcampToProd
Star
1
Language
Java
License
-

Recommend Servers

View All
Voyei

3 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

13 hours ago