Ragie Model Context Protocol Server

Created By
andyciggya year ago
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. You can run the server with the command: RAGIE_API_KEY=your_api_key npx @ragieai/mcp-server. You can also customize the server's behavior using command line options.

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 customization.

Use cases of Ragie Model Context Protocol Server?

  1. Integrating knowledge retrieval capabilities into AI applications.
  2. Enhancing chatbots with access to a knowledge base.
  3. Supporting research and data analysis by retrieving relevant information.

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 server's description?

Yes, you can override the default 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
andyciggy
Star
0
Language
JavaScript
License
MIT 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)

2 days ago