Ragie Model Context Protocol Server
The Ragie Model Context Protocol Server allows AI models to efficiently retrieve information from a Ragie knowledge base via the Model Context Protocol (MCP).
Search the knowledge base: Query for relevant information using the
retrievetoolCustomizable search: Control parameters like number of results (
topK), rank relevance (rerank), and recency bias (recencyBias)Access various information types: Retrieve documents, policies, product specifications, technical documentation, and historical data
Integration capabilities: Connect with MCP clients like Cursor and Claude desktop
Project-specific configuration: Set up for specific projects or across all projects
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Ragie Model Context Protocol Serverretrieve information about our company's remote work policy"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
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-serverCommand 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_idCursor Configuration
To use this MCP server with Cursor:
Option 1: Create an MCP configuration file
Save a file called
mcp.json
For tools specific to a project, create a
.cursor/mcp.jsonfile 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.jsonfile 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
Save a file called
ragie-mcp.shon your system:
#!/usr/bin/env bash
export RAGIE_API_KEY="your_api_key"
npx -y @ragieai/mcp-server --partition optional_partition_idGive the file execute permissions:
chmod +x ragie-mcp.shAdd 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:
Create the MCP config file
claude_desktop_config.json:
For MacOS: Use
~/Library/Application Support/Claude/claude_desktop_config.jsonFor 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.
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 informationtopK(number, optional, default: 8): The maximum number of results to returnrerank(boolean, optional, default: true): Whether to try and find only the most relevant informationrecencyBias(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 serverragie: For interacting with the Ragie APIzod: For runtime type validation
Development setup
Running the server in dev mode:
RAGIE_API_KEY=your_api_key npm run dev -- --partition optional_partition_idBuilding the project:
npm run buildLicense
MIT License - See LICENSE.txt for details.
Available Tools
1 toolretrieveA
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
| Name | Required | Description | Default |
|---|---|---|---|
| topK | No | The maximum number of results to return. Defaults to 8. | |
| query | Yes | The query to search for data in the Knowledge Base | |
| filter | No | The 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. | |
| rerank | No | Whether to try and find only the most relevant data. Defaults to false. | |
| recencyBias | No | Whether to favor data towards more recent documents. Defaults to false. |
TDQS
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.
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.
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.
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.
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.
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
With only one tool, there is no potential for confusion between tools. The tool's purpose is clearly defined.
With a single tool named 'retrieve', there is no pattern to evaluate. Naming is neither consistent nor inconsistent—it's neutral.
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.
The server only supports retrieval. Essential actions like adding, updating, or deleting documents are missing, leaving significant gaps in functionality.
Maintenance
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
Driflyte MCP server which lets AI assistants query topic-specific knowledge from web and GitHub.
An MCP server that integrates with Discord to provide AI-powered features.
MCP server for AI dialogue using various LLM models via AceDataCloud
An MCP server that gives your AI access to the source code and docs of all public github repos
Related MCP Servers
- AlicenseBqualityFmaintenanceAn MCP server that enables users to retrieve information from AWS Knowledge Bases using RAG (Retrieval-Augmented Generation) via Bedrock Agent Runtime.1309MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that implements Retrieval-Augmented Generation to efficiently retrieve and process important information from various sources, providing accurate and contextually relevant responses.
- AlicenseNot gradedqualityBmaintenanceRAG Knowledge - MCP server providing AI-powered tools and automation by MEOK AI Labs13MIT
- AlicenseNot gradedqualityBmaintenanceA plugin-based MCP server that enables AI assistants to interact with external systems through custom tools, resources, and prompts.4AGPL 3.0
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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