[Feature Request] Implement SeekDB Search MCP Server

[MileyFu]

Develop a Rust MCP Server containing only the search tool. This service needs to connect to OceanBase, receive query strings, perform Vector Search, and return relevant text segments.

[YixinZ-NUS]

Hi! I found this issue through the OceanBase Developer Activities and I would like to work on it. Please let me know if you would like me to submit an implementation plan before I start coding. Could you please assign this issue to me?

[YixinZ-NUS]

Thanks for the assignment! I’m on it.

[YixinZ-NUS]

Hi @MileyFu, I skimmed the code and wanted make sure I’m aligned on scope.

Could you confirm the intended scope - Should this PR deliver a demo with a runnable local MCP server, an example config.toml and sample SeekDB under examples/mcp, without changing the codes for the server?

Also could you explain to me the intended config for MCP tools?

1. Should local MCP servers be configured via llm.mcp_server, while provider-hosted tools / remote MCP go under llm.extra.tools?
2. In the current code, llm.mcp_server appears to be active only for openai_chat, not openai_responses. Is openai_chat + llm.mcp_server the intended .toml setup?

Thanks!

[alabulei1]

Hi @YixinZ-NUS,

Thanks for your questions.

Yes, we don’t plan to change the EchoKit server code for this issue. Instead, you can provide an example using the SeekDB MCP server. https://github.com/second-state/echokit_server/tree/main/examples/mcp

1. The parameter for calling an MCP server is llm.mcp_server. The llm.extra.tools parameter is currently used only for the built-in web search.
2. Using openai_chat together with llm.mcp_server is the intended .toml setup. However, since the Responses API is gaining wider adoption, it would be great if you could also provide an example based on the Responses API. This may require changes to the EchoKit server code, which would be highly appreciated.

Let me know if you have any questions.

[YixinZ-NUS]

Thanks a lot for the clarification and guidance @alabulei1 ! For the Responses API, I agree it’d be valuable, but since it may require server-side changes, I suggest we track it as a separate issue. If that works for you, I’ll proceed with the example PR first and then open a follow-up issue for Responses API support right after.

In the meantime, I can add a short note in the example docs pointing to the follow-up work, so users know it’s planned.

[alabulei1]

Hi @YixinZ-NUS,

No problem. Thanks for your contribution. Here is the issue for the Response API. #24

[YixinZ-NUS]

Hi @MileyFu and @alabulei1, I've submitted PR #41, implementing the MCP server that interacts with SeekDB and perform Vector Search. Please let me know if you have any feedback—I’m happy to make further adjustments. Thanks!

[MileyFu]

Hi @YixinZ-NUS good news. Ocean base told us that issue #24 can also be included in the hackathon. ❤️