FAQai

app.faqaiPublished by faqai.appv0.5.1Updated Oct 24, 2026

Turn any document into a production-ready RAG dataset from Claude, Cursor, or any MCP host.

VerifiedSTDIODesktop onlyKnowledge & Memory

Overview

AI-generated overview

Lets an assistant turn documents into a production-ready RAG dataset through the FAQai API.

What you can do
FAQai is a local MCP server that connects an assistant to the FAQai service for building RAG datasets from documents. The registry description says it can turn any document into a production-ready RAG dataset from Claude, Cursor, or any MCP host. The manifest does not list individual tools, so the exact operations are not documented here.
When to use it
Consider it when you already use FAQai and want to prepare RAG datasets from documents without leaving your MCP host. It is a desktop-only local process, so it suits Claude Desktop or Cursor-style setups rather than browser-based hosts.
Requirements
Runs locally over stdio, typically via the npm package @faqai/mcp-server, so Node.js is needed. Requires a FAQai API key in the FAQAI_API_KEY environment variable, and the key requires a paid plan. An optional FAQAI_BASE_URL variable can override the default API base URL. Network access to the FAQai API is required.
Before you install
The FAQAI_API_KEY secret is required and tied to a paid plan, so usage may incur costs. Documents submitted for dataset creation are sent to the third-party FAQai service. The manifest lists no tools, so review what the server can read, write, or delete before installing.

Installation

In SourceWeft

  1. Open FAQai in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.5.1LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.