Skip to main content
Glama
enesjakozh
GongRzhe

Langflow Document Q&A Server

by GongRzhe
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

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

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYesThe query prompt to search for in the documents

TDQS

C2.6/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions querying a 'document Q&A system', which implies a read-only operation, but doesn't specify behavioral traits like response format, error handling, rate limits, or authentication needs. The description is too minimal to provide adequate transparency for safe and effective use.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence: 'Query the document Q&A system with a prompt'. It's front-loaded and efficiently conveys the core action without unnecessary words. However, it could be slightly more informative without losing conciseness, such as by specifying the system's purpose or output type.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (a query tool with no annotations and no output schema), the description is incomplete. It lacks details on what the tool returns, how results are formatted, any limitations, or error conditions. Without annotations or an output schema, the description should provide more context to help the agent understand the tool's behavior and outcomes, but it falls short.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with the 'query' parameter documented as 'The query prompt to search for in the documents'. The description adds no additional meaning beyond this, as it doesn't elaborate on query syntax, examples, or constraints. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool 'Query the document Q&A system with a prompt', which provides a basic verb ('Query') and resource ('document Q&A system'), making the purpose somewhat clear. However, it's vague about what 'document Q&A system' entails and doesn't specify the scope or type of documents, leaving room for ambiguity. Without sibling tools, it doesn't need differentiation, but the purpose could be more specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no guidance on when to use this tool, such as what types of queries it supports, prerequisites, or limitations. It simply states the action without context, leaving the agent to infer usage from the tool name and parameters alone. This lack of explicit or implied guidelines reduces its helpfulness in selecting the tool appropriately.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2.9/5.0
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.

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

Related MCP Servers

Appeared in Searches

Latest Blog Posts

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/GongRzhe/Langflow-DOC-QA-SERVER'

If you have feedback or need assistance with the MCP directory API, please join our Discord server