Ragie Model Context Protocol Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Ragie Model Context Protocol Server?

The Ragie Model Context Protocol Server is a server that implements the Model Context Protocol (MCP) to enable AI models to retrieve information from a Ragie knowledge base.

How to use Ragie Model Context Protocol Server?

To use the server, you need to install it using Node.js and provide your Ragie API key as an environment variable. You can start the server with the command: RAGIE_API_KEY=your_api_key npx @ragieai/mcp-server.

Key features of Ragie Model Context Protocol Server?

  • Implements the Model Context Protocol for knowledge retrieval.
  • Provides a retrieve tool for querying the knowledge base.
  • Supports command line options for custom descriptions and partition IDs.

Use cases of Ragie Model Context Protocol Server?

  1. Integrating knowledge retrieval capabilities into AI applications.
  2. Enabling chatbots to access a structured knowledge base.
  3. Assisting developers in building applications that require dynamic information retrieval.

FAQ from Ragie Model Context Protocol Server?

  • What is required to run the server?

You need Node.js version 18 or higher and a valid Ragie API key.

  • Can I customize the tool description?

Yes, you can override the default tool description using command line options.

  • Is there a way to specify which partition to query?

Yes, you can specify the partition ID using command line options.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Payai X402 Tools

an hour ago
Payai X402 Tools

an hour 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