Enable SurfSense to connect to MCP servers

[manojag115]

I am adding support for MCP connectors that let users define custom REST API endpoints as AI tools. Wanted to get this group aligned on some design decisions and details!

Example scenario: User adds dog.ceo/api/breeds/image/random as a tool named "get_random_dog". When asked "show me a cute dog", the AI calls this API and displays the image.

UI Design

Location

Dashboard → Connectors → "More Integrations" → MCP Connector

Form Fields

• Connector Name: Display name (e.g., "Dog API Tools")
• Tools Array: Multiple tools per connector
• Tool Name: get_random_dog
• Description: "Fetches a random dog image"
• HTTP Method: GET/POST/PUT/PATCH/DELETE
• URL: https://dog.ceo/api/breeds/image/random
• Parameters Schema: JSON Schema for request parameters

Authentication (tool-level)

• None
• Bearer Token
• API Key (header name + key)
• Basic Auth (username + password)

Implementation details

Invocation Flow is very similar to other tools like generate_podcast:

• Dynamically loaded in registry.py via load_mcp_tools()
• Each tool config creates a StructuredTool instance
• Returns LangChain tools that AI can invoke
• Same invocation mechanism

Design Questions

• Tool-level auth: Should each tool have its own auth config or should there be one per connector and all tools within the connector share that?
• Any testing interface we should provide to try out the api call before integrating?
• Error handling UI: How should failed API calls appear in chat?
• Should we have grouping of tools under each custom connector or should we just have individual tools under one custom connector? Right now i am thinking the user can have multiple custom connectors, with each connector having multiple tools.

[manojag115]

cc: @MODSetter any thoughts?

[MODSetter]

@manojag115 Don’t tool definitions come from the MCP server itself? Why would we need to define tools manually?

Cursor is a good example of this in action. Try adding an MCP server there. In short, you just need to paste your MCP JSON config and then fetch the tool definitions. Having an option to enable or disable those tools would be great.

LMK if any of this doesn’t make sense.

[manojag115]

@MODSetter yeah make sense. Will take a stab at it tomorrow.
I am thinking of adding:

• MCP server option in the connectors list
• text box for 1 tool config
• multiple text boxes per connector
• enable/disable connectors in "active connectors" tab

Stay tuned for a PR.