Skip to main content
Dify is an MCP client, so it reaches Renor the way Claude Code or Codex does: one MCP address and one key. What your coding agent saved, a Dify agent can recall, and the other way round.

​
Before you start

  1. In the dashboard, open API keys and choose Create key. The key is shown once; it works for 365 days and you can revoke it there.
  2. Keep it to hand. Dify sends it as Authorization: Bearer <key>.

​
Add Renor to Dify

  1. In Dify, open Tools, then MCP, then Add MCP Server (HTTP).
  2. Server URL: https://mcp.renor.cloud/mcp. Name: Renor.
  3. Under headers, add Authorization with the value Bearer <your key>.
  4. Save. Dify lists the tools Renor serves (Tools). Two do most of the work: get_context (call it before answering, with the current request) and remember (call it when the user asks to keep something).

​
Use it in an agent

Download the example agent and import it with Create from DSL file. Then open the app, add the Renor MCP tools to it (the DSL cannot carry your server’s id, so you pick them once after importing), and set your own model. Its instructions are the same two lines every Renor example uses:

​
Use it in a workflow

Add a Tool node, choose Renor, then get_context, and set query to the user’s message. Feed its result into the model node’s prompt. Add a second Tool node for remember where the user asks to keep something.

​
Check that it works

Start two separate conversations with the agent. In the first say “Remember that I deploy with Kamal to the server orca-7.” In the second, with no history, ask “How do I deploy?”. The answer can only come from Renor. The key belongs to your workspace: a Dify agent reads and writes the same memory as every other agent you have connected (see Several agents, one memory). The example file has not been imported into a live Dify in this repository’s tests; they only check that its text is well formed. If your Dify version rejects it, add the MCP server by hand as above.