
Ragora
io.github.mregmiPublished by GitHub account mregmiv3.0.0Updated Oct 24, 2026
Search your knowledge bases from any AI assistant using hybrid RAG.
Overview
Hosted Ragora MCP server that lets an AI assistant search your Ragora knowledge bases with hybrid RAG over Streamable HTTP.
- What you can do
- List accessible knowledge bases with descriptions, stats and usage examples
- Search across all of your collections at once with a natural language query
- Search a specific collection by name, with optional tags and metadata filters
- Use per-collection tools generated from each collection's slug to search, fetch a topic, or list documentation versions
- When to use it
- Useful when your documentation, handbooks or other reference material already lives in Ragora collections and you want an assistant to answer questions from them without copying files locally. It suits teams that want one key-scoped search endpoint across several knowledge bases.
- Requirements
- A Ragora account and an API key created under Settings > API Keys, sent as an Authorization Bearer header. The server is a hosted endpoint using Streamable HTTP with POST requests, so no local install is needed, but internet access is required.
Installation
In SourceWeft
- Open Ragora in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.mregmi%2Fragora-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"ragora": {
"type": "http",
"url": "https://mcp.ragora.app/mcp"
}
}
}README
Ragora MCP Server
Search your knowledge bases from any AI assistant using the Model Context Protocol.
Ragora's MCP server is a hosted cloud service — no local installation required. Just configure your AI tool with the server URL and your API key.
Server URL: https://mcp.ragora.app/mcp
Quick Start
1. Get an API Key
Sign up at ragora.app and create an API key at Settings > API Keys.
2. Connect Your AI Tool
Claude Desktop
Option 1: CLI (recommended)
Option 2: Config file
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (Mac) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
Claude Code
Cursor
Add to .cursor/mcp.json in your project root:
VS Code / GitHub Copilot
Add to .vscode/mcp.json in your project root:
Windsurf
Add to ~/.codeium/windsurf/mcp_config.json:
Any MCP Client
Ragora uses Streamable HTTP transport. Point any MCP-compatible client to:
- URL:
https://mcp.ragora.app/mcp - Method:
POST - Header:
Authorization: Bearer sk_live_your_key_here
Available Tools
Tool Parameters
search(query, top_k?)
query(required): Natural language search querytop_k(optional): Number of results to return (default: 5)
search_collection(collection_name, query, top_k?, custom_tags?, filters?)
collection_name(required): Collection name or slug (usediscover_collectionsto find names)query(required): Natural language search querytop_k(optional): Number of results (default: 5)custom_tags(optional): Tags to scope retrievalfilters(optional): Metadata filters
Dynamic Collection Tools
For each collection you have access to, dedicated tools are generated using the collection's slug:
search_{slug}— semantic search with optional version, tags, and filtersget_topic_{slug}— retrieve information about a specific topiclist_versions_{slug}— list available documentation versions
For example, a collection called "Employee Handbook" gets:
search_employee_handbookget_topic_employee_handbooklist_versions_employee_handbook
Configure tool names and descriptions in the Ragora dashboard under Collection > MCP Settings.
Usage Examples
Search all collections:
"Search my docs for webhook event handling"
Search a specific collection:
"Look up the refund policy in the employee handbook"
Discover what's available:
"What workspaces do I have, and what's in them?"
How It Works
- No local install — connect directly via HTTP
- Multi-tenant — your API key determines which collections you can access
- Dynamic tools — tools are generated based on your accessible collections
- Hybrid search — dense (E5-Large) + sparse (BM25) with reciprocal rank fusion
Security
- API keys authenticate all requests via
Authorization: Bearerheader - Each API key is scoped to the user's owned and purchased collections
- Cross-tenant data access is impossible — all queries are filtered by accessible collection IDs
- API keys should never be committed to version control
Troubleshooting
Links
- Ragora — Sign up and manage your knowledge bases
- MCP Integration Guide — Full documentation
- API Keys — Create your API key
- Model Context Protocol — MCP specification
License
MIT
Source: README.md at commit 99626b9
Tools
0Version history
1- v3.0.0LatestSep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts