Skip to main content
Glama
Langflow Document Q&A Server

Langflow Document Q&A Server

by GongRzhe

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

  1. Open Langflow and create a new flow from the "Document Q&A" template

  2. Configure your flow with necessary components (ChatInput, File Upload, LLM, etc.)

  3. Save your flow

image

2. Get Flow API Endpoint

  1. Click the "API" button in the top right corner of Langflow

  2. Copy the API endpoint URL from the cURL command Example: http://127.0.0.1:7860/api/v1/run/<flow-id>?stream=false

  3. Save this URL as it will be needed for the API_ENDPOINT configuration

image

Related MCP server: Chalee MCP RAG

Features

Tools

  • query_docs - Query the document Q&A system

    • Takes a query string as input

    • Returns responses from the Langflow backend

Development

Install dependencies:

npm install

Build the server:

npm run build

For development with auto-rebuild:

npm run watch

Installation

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"
      }
    }
  }
}

image

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 claude

Environment Variables

The server supports the following environment variables for configuration:

  • API_ENDPOINT: The endpoint URL for the Langflow API service. Defaults to http://127.0.0.1:7860/api/v1/run/480ec7b3-29d2-4caa-b03b-e74118f35fac if 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 inspector

The Inspector will provide a URL to access debugging tools in your browser.

📜 License

This project is licensed under the MIT License.

Available Tools

1 tool
query_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

    C2.9/5.0

    Scored across 1 tool

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count2/5

    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.

    Completeness2/5

    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

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers