DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to give a bot access to apps through MCP or OpenAPI with Rakazo

Add your own HTTPS MCP server, Treg endpoint, or OpenAPI document as a tool source for a bot.

Authorization notice. Rakazo is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Credentials. Tool sources may need tokens or keys, and the README says connector credentials are encrypted on the server and never returned by the API, so store them only through Rakazo.

Who it is forA developer or operator who already runs an MCP server or has an OpenAPI description of an internal service and wants a bot to call it.

The problemA bot cannot act on your own services unless it has a tool source that describes what those services can do.

The outcomeA bot that can call a connected HTTPS MCP server or OpenAPI-described API through Integrations.

What you need first

  • Docker Engine and the Compose plugin
  • curl and OpenSSL
  • A model provider account or key, such as an OpenRouter API key or a supported provider connected during onboarding

Steps

  1. Start a running Rakazo instance using the Quick start or a source checkout.
  2. Sign in and open Integrations.
  3. Add an HTTPS MCP server or an OpenAPI JSON document as a tool source.
  4. Attach the tool source to a bot and send it a request that needs that tool.

Prompt for your agent

In the Rakazo repo at https://github.com/elie222/rakazo, use the Integrations area of a running instance at <instance-url> to add the HTTPS MCP server <mcp-url> as a tool source. Report the tool source name and one tool it exposes. Verify that a test bot request uses the tool and returns a result.

Caveat. Treg is usage-metered, self-hosters must supply their own Treg token, and hosted resale requires a written agreement under Treg's integration terms.

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