Skip to content

[Feature Request]: Expanded the capabilities of the MCP Server #8644

@Drasek

Description

@Drasek

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (Language Policy).
  • Non-english title submitions will be closed directly ( 非英文标题的提交将会被直接关闭 ) (Language Policy).
  • Please do not modify this template :) and fill in all the required fields.

Is your feature request related to a problem?

I am connecting my RAGFlow instance to my n8n server (i have several datasources (ragflow, supabase, etc.) and combine them there) and are getting errors from models that the input token limits are broken. So i looked into it to reduce input size from the MCP Server of RAGFlow. While i was at it i changed more stuff, for example i need the metadata from the documents in my flow.

Describe the feature you'd like

Expand the capabilities of the MCP Server of RAGFlow.

Describe implementation you've considered

I am on v0.19.1 full - so i can not provide a direct pull request because you added support for @click library in the last commits (not in a release till now) which breaks with codebase from the v0.19.1 - so i thought i could provide you my code (please remember i am a bloody amateuer) to look at and grab stuff from it to expand the capabilities of the MCP Server in the next releases.

Documentation, adoption, use case

- exposed lots of options to the MCP Client side (and reduced default number of results to 10), so modified the list_tools function heavily
- added lots of stuff to the answer data to the MCP Client, including metadata - so modified the retrieval function heavily

Its mainly those 2 functions + helper functions i changed.

Additional information

Added my server.py - (changed it to txt to be able to upload it) - yeah i know thats a pretty weird way for a feature request instead of a pull, but do not know how to do it else, as long as i am not going to a selfbuild nightly version.

server.txt

Metadata

Metadata

Assignees

No one assigned

    Labels

    💞 featureFeature request, pull request that fullfill a new feature.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions