MCP Document Server

Created By
Omerisra6a year ago
A simple server implementing the Model Context Protocol for document search
Overview

What is MCP Document Server?

MCP Document Server is a simple server that implements the Model Context Protocol (MCP) for document search and retrieval, allowing users to efficiently manage and access documents.

How to use MCP Document Server?

To use the MCP Document Server, install the necessary dependencies, build the TypeScript code, and start the server. You can then interact with the server using the Cursor tool to search for and create documents.

Key features of MCP Document Server?

  • Document storage and retrieval using MCP
  • Semantic search capabilities
  • Compatible with Cursor and other MCP clients
  • Pluggable document service architecture with local storage and Confluence integration
  • Support for both Markdown and HTML document formats

Use cases of MCP Document Server?

  1. Searching for documents in a local storage system.
  2. Integrating with Confluence to retrieve workspace documents.
  3. Creating and managing documents through a user-friendly interface.

FAQ from MCP Document Server?

  • Can I use MCP Document Server with other document services?

Yes! The server is designed to be extensible, allowing you to add new document services easily.

  • Is there a way to search documents using keywords?

Yes! You can use the search tool with a keyword parameter to find documents.

  • How do I set up the Confluence integration?

You need to set specific environment variables for Confluence before starting the server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Omerisra6
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year 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.

a day ago