Skip to main content
Glama
ragieai

Ragie Model Context Protocol Server

by ragieai

IMPORTANT!

This project is no longer needed. Ragie now supports MCP natively as a streamable HTTP server. See docs here: [https://docs.ragie.ai/docs/mcp-overview]

If you would like users within your company to be able to access you knowledge base in applications like Claude or ChatGPT, you may need MCP Bridge

image

Ragie Model Context Protocol Server

A Model Context Protocol (MCP) server that provides access to Ragie's knowledge base retrieval capabilities.

Description

This server implements the Model Context Protocol to enable AI models to retrieve information from a Ragie knowledge base. It provides a single tool called "retrieve" that allows querying the knowledge base for relevant information.

Related MCP server: RAG Information Retriever

Prerequisites

  • Node.js >= 18

  • A Ragie API key

Installation

The server requires the following environment variable:

  • RAGIE_API_KEY (required): Your Ragie API authentication key

The server will start and listen on stdio for MCP protocol messages.

Install and run the server with npx:

RAGIE_API_KEY=your_api_key npx @ragieai/mcp-server

Command Line Options

The server supports the following command line options:

  • --description, -d <text>: Override the default tool description with custom text

  • --partition, -p <id>: Specify the Ragie partition ID to query

Examples:

# With custom description
RAGIE_API_KEY=your_api_key npx @ragieai/mcp-server --description "Search the company knowledge base for information"

# With partition specified
RAGIE_API_KEY=your_api_key npx @ragieai/mcp-server --partition your_partition_id

# Using both options
RAGIE_API_KEY=your_api_key npx @ragieai/mcp-server --description "Search the company knowledge base" --partition your_partition_id

Cursor Configuration

To use this MCP server with Cursor:

Option 1: Create an MCP configuration file

  1. Save a file called mcp.json

  • For tools specific to a project, create a .cursor/mcp.json file in your project directory. This allows you to define MCP servers that are only available within that specific project.

  • For tools that you want to use across all projects, create a ~/.cursor/mcp.json file in your home directory. This makes MCP servers available in all your Cursor workspaces.

Example mcp.json:

{
  "mcpServers": {
    "ragie": {
      "command": "npx",
      "args": [
        "-y",
        "@ragieai/mcp-server",
        "--partition",
        "optional_partition_id"
      ],
      "env": {
        "RAGIE_API_KEY": "your_api_key"
      }
    }
  }
}

Option 2: Use a shell script

  1. Save a file called ragie-mcp.sh on your system:

#!/usr/bin/env bash

export RAGIE_API_KEY="your_api_key"

npx -y @ragieai/mcp-server --partition optional_partition_id
  1. Give the file execute permissions: chmod +x ragie-mcp.sh

  2. Add the MCP server script by going to Settings -> Cursor Settings -> MCP Servers in the Cursor UI.

Replace your_api_key with your actual Ragie API key and optionally set the partition ID if needed.

Claude Desktop Configuration

To use this MCP server with Claude desktop:

  1. Create the MCP config file claude_desktop_config.json:

  • For MacOS: Use ~/Library/Application Support/Claude/claude_desktop_config.json

  • For Windows: Use %APPDATA%/Claude/claude_desktop_config.json

Example claude_desktop_config.json:

{
  "mcpServers": {
    "ragie": {
      "command": "npx",
      "args": [
        "-y",
        "@ragieai/mcp-server",
        "--partition",
        "optional_partition_id"
      ],
      "env": {
        "RAGIE_API_KEY": "your_api_key"
      }
    }
  }
}

Replace your_api_key with your actual Ragie API key and optionally set the partition ID if needed.

  1. Restart Claude desktop for the changes to take effect.

The Ragie retrieval tool will now be available in your Claude desktop conversations.

Features

Retrieve Tool

The server provides a retrieve tool that can be used to search the knowledge base. It accepts the following parameters:

  • query (string): The search query to find relevant information

  • topK (number, optional, default: 8): The maximum number of results to return

  • rerank (boolean, optional, default: true): Whether to try and find only the most relevant information

  • recencyBias (boolean, optional, default: false): Whether to favor results towards more recent information

The tool returns:

  • An array of content chunks containing matching text from the knowledge base

Development

This project is written in TypeScript and uses the following main dependencies:

  • @modelcontextprotocol/sdk: For implementing the MCP server

  • ragie: For interacting with the Ragie API

  • zod: For runtime type validation

Development setup

Running the server in dev mode:

RAGIE_API_KEY=your_api_key npm run dev -- --partition optional_partition_id

Building the project:

npm run build

License

MIT License - See LICENSE.txt for details.

Available Tools

1 tool
retrieveA

Look up information in the Knowledge Base. Use this tool when you need to:

  • Find relevant documents or information on specific topics

  • Retrieve company policies, procedures, or guidelines

  • Access product specifications or technical documentation

  • Get contextual information to answer company-specific questions

  • Find historical data or information about projects

ParametersJSON Schema
NameRequiredDescriptionDefault
topKNoThe maximum number of results to return. Defaults to 8.
queryYesThe query to search for data in the Knowledge Base
filterNoThe metadata search filter on documents. Returns chunks only from documents which match the filter. The following filter operators are supported: $eq - Equal to (number, string, boolean), $ne - Not equal to (number, string, boolean), $gt - Greater than (number), $gte - Greater than or equal to (number), $lt - Less than (number), $lte - Less than or equal to (number), $in - In array (string or number), $nin - Not in array (string or number). The operators can be combined with AND and OR. Read Metadata & Filters guide for more details and examples.
rerankNoWhether to try and find only the most relevant data. Defaults to false.
recencyBiasNoWhether to favor data towards more recent documents. Defaults to false.

TDQS

A3.5/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must carry the full burden. It only implies a read-only operation by saying 'Look up information', but fails to explicitly state it is read-only, does not disclose authentication needs, rate limits, or error behavior. This is a significant gap for a retrieval tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is relatively concise, using a bullet list of use cases. It is front-loaded with the purpose statement. However, some redundancy exists with 'Use this tool when you need to' repeated for each item.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 5 parameters, including a complex nested filter object, and no output schema. The description does not explain the return format, pagination, or how results are structured. It only vaguely mentions 'information', leaving the agent without sufficient context to interpret the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and all parameters have descriptions in the schema. The tool description does not add additional meaning beyond what the schema provides. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Look up information in the Knowledge Base' and lists specific use cases (e.g., 'Find relevant documents', 'Retrieve company policies'). It directly addresses what the tool does with a specific verb and resource.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides a bullet list of when to use the tool, such as 'Find relevant documents or information' and 'Get contextual information'. It implicitly guides usage but does not explicitly state when not to use or mention alternatives, though no sibling tools exist.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

TDQS

B3.2/5.0
Disambiguation5/5

With only one tool, there is no potential for confusion between tools. The tool's purpose is clearly defined.

Naming Consistency3/5

With a single tool named 'retrieve', there is no pattern to evaluate. Naming is neither consistent nor inconsistent—it's neutral.

Tool Count1/5

A knowledge base server with only one retrieval tool is extremely minimal. Agents cannot perform any CRUD operations, making this count far too low for the implied scope.

Completeness1/5

The server only supports retrieval. Essential actions like adding, updating, or deleting documents are missing, leaving significant gaps in functionality.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    A plugin-based MCP server that enables AI assistants to interact with external systems through custom tools, resources, and prompts.
    4
    AGPL 3.0

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ragieai/ragie-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server