DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to give any chat model web search and MCP tools with Respan Gateway

Attach a tool vendor or MCP server so a plain chat call can use it.

Credentials. Tool vendor keys are stored in gateway.toml through env references, so keep the environment variables out of shared logs and version control.

Who it is forA developer building an assistant who needs web search or other tools available to whichever model the app calls.

The problemTool support differs by model and client, so tools must be wired separately for each combination.

The outcomeA plain chat request through the gateway can call search tools, whatever the client or model.

What you need first

  • Python with pip, or a Rust toolchain with cargo, or Docker
  • An API key for at least one model vendor, such as OPENAI_API_KEY
  • An existing app or SDK that accepts a custom base URL
  • Optional: a Respan API key for tracing and a tool vendor key for MCP tools

Steps

  1. Run respan-gateway init to create gateway.toml.
  2. Add a [tools.search] table with the vendor and key settings shown in the README, for example vendor = "linkup" with key = "env:LINKUP_API_KEY".
  3. Add a [plugins.tool_loop] table whose servers list includes "search".
  4. Run respan-gateway check to validate the file, then start the gateway with respan-gateway.
  5. Send a chat request that asks a question needing current web data and check the reply for tool use in the live log.

Prompt for your agent

In the respan-gateway repo, add a search tool vendor and the tool_loop plugin to gateway.toml, validate it, then send a chat request to the gateway that needs web search and report the answer. Verify that the live log at localhost:8080/ui/ shows the tool call.

Caveat. The README example uses the linkup tool vendor, so you need a key for that vendor before search tools will work.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page