Langflow Document Q&A Server
The Langflow Document Q&A Server allows you to query documents with natural language prompts. With this server, you can:
Query Documents: Search through documents by providing natural language queries using the
query_docstoolRetrieve Answers: Get responses based on document content and your provided query
Langflow Integration: Connect to a Langflow backend that processes and responds to queries
Configurable API Endpoint: Set custom Langflow API endpoints via environment variables
MCP Compliance: Integrate seamlessly with tools like Claude Desktop through Model Context Protocol
Debugging Support: Use tools like the MCP Inspector for troubleshooting server communications
Enables document question-answering capabilities by connecting to a Langflow backend, allowing users to upload documents and query them using natural language through a Langflow Document Q&A Flow.
Click on "Deploy 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., "@Langflow Document Q&A Server what are the key findings in the quarterly report?"
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.
Langflow-DOC-QA-SERVER
A Model Context Protocol server for document Q&A powered by Langflow
This is a TypeScript-based MCP server that implements a document Q&A system. It demonstrates core MCP concepts by providing a simple interface to query documents through a Langflow backend.
Prerequisites
1. Create Langflow Document Q&A Flow
Open Langflow and create a new flow from the "Document Q&A" template
Configure your flow with necessary components (ChatInput, File Upload, LLM, etc.)
Save your flow
2. Get Flow API Endpoint
Click the "API" button in the top right corner of Langflow
Copy the API endpoint URL from the cURL command Example:
http://127.0.0.1:7860/api/v1/run/<flow-id>?stream=falseSave this URL as it will be needed for the
API_ENDPOINTconfiguration
Related MCP server: Chalee MCP RAG
Features
Tools
query_docs- Query the document Q&A systemTakes a query string as input
Returns responses from the Langflow backend
Development
Install dependencies:
npm installBuild the server:
npm run buildFor development with auto-rebuild:
npm run watchInstallation
To use with Claude Desktop, add the server config:
On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%/Claude/claude_desktop_config.json
{
"mcpServers": {
"langflow-doc-qa-server": {
"command": "node",
"args": [
"/path/to/doc-qa-server/build/index.js"
],
"env": {
"API_ENDPOINT": "http://127.0.0.1:7860/api/v1/run/480ec7b3-29d2-4caa-b03b-e74118f35fac"
}
}
}
}Installing via Smithery
To install Document Q&A Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @GongRzhe/Langflow-DOC-QA-SERVER --client claudeEnvironment Variables
The server supports the following environment variables for configuration:
API_ENDPOINT: The endpoint URL for the Langflow API service. Defaults tohttp://127.0.0.1:7860/api/v1/run/480ec7b3-29d2-4caa-b03b-e74118f35facif not specified.
Debugging
Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:
npm run inspectorThe Inspector will provide a URL to access debugging tools in your browser.
📜 License
This project is licensed under the MIT License.
Available Tools
1 toolquery_docsC
Query the document Q&A system with a prompt
Inputs: query (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'query_docs' has a clear and distinct purpose for querying documents, so agents cannot misselect among multiple options.
The naming is trivially consistent as there is only one tool. It follows a verb_noun pattern ('query_docs'), which is clear and predictable, and there are no other tools to cause inconsistency or mixed conventions.
The tool count is too low for a server with the apparent scope of a 'Document Q&A Server'. A single query tool feels thin and incomplete, as it lacks supporting operations like document upload, management, or retrieval, which are typical for such a domain.
The tool surface is significantly incomplete for a document Q&A system. While 'query_docs' allows querying, there are obvious gaps such as no tools for adding, updating, deleting, or listing documents, which are essential for a functional document management and query workflow.
Maintenance
Related MCP Connectors
Ingest, manage, and retrieve documents for RAG-powered AI applications
Build a RAG pipeline station by station and search your own documents with cited answers.
Query any docs site via MCP. Submit a URL, ask questions, get cited answers.
Query Klaaro datasets, documents, and extracted records from any agent.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables semantic search and question-answering over FAQ documents using RAG (Retrieval-Augmented Generation) with OpenAI embeddings and in-memory vector similarity.-
- AlicenseNot gradedqualityDmaintenanceEnables RAG (Retrieval-Augmented Generation) capabilities with document processing, vector storage, and intelligent Q\&A using OpenAI embeddings and semantic search.MIT
- AlicenseNot gradedqualityCmaintenanceEnables document-based Q&A with multi-modal RAG, hybrid retrieval, knowledge graph reasoning, and multi-agent orchestration via MCP tools.4MIT
- FlicenseNot gradedqualityDmaintenanceEnables querying internal documents via a FastAPI REST API and MCP server, using retrieval-augmented generation and an agentic loop that can invoke tools like document search and calculations.-