Recued Docs

Guides

Connect to Recued

How each kind of app connects to your server. MCP agents, chat apps, and chat platforms all come in through doors at the same gate.

Everything that reaches your server from outside comes in through a door. A door is a way in that you open on purpose. Every door leads to the same gate. The gate marks who is asking, checks the grants, and writes the audit diary. This page goes app by app. Pick the thing you are connecting. Follow its shape.

#MCP agents

MCP is a shared language that AI apps use to call your server's tools. Claude Desktop, Cursor, a custom agent, or a peer Recued can connect over MCP:

  1. Open the MCP door. Choose the tools it may show. The door makes its own secret key.
  2. Give the agent your server's MCP address and that secret key.
  3. The agent's calls arrive marked with its name. They pass your grants. They land in the audit diary.

The agent sees only what the door grants: warehouse reads, timelines, and recipes as tools. Close the door, and its secret key stops working.

A peer Recued connects the same way, with one extra. Its owner can put a question to you and hold their own run until you answer. See Ask a peer.

#OpenAI-compatible chat apps

Some chat apps let you type in a custom base URL and an API key. Any app like that can talk to a Recued server that has given it access. The app does not need MCP. This is the way a seller's customers use an "ask my operated knowledge" product. It speaks the standard shape:

  • Base URL: your server's gateway address.
  • API key: the door's secret key. The app sends it as a normal bearer key, which is a secret key sent with each request. Customers get theirs through a claim link.
  • GET /v1/models: returns one model. Its name is an alias the server owner picks (recued-seller by default). The alias is only a label, not a choice. The server decides which real model answers. Its owner sets that.
  • POST /v1/chat/completions: one request is one chat turn, and the gate checks it.

A turn runs on the server's chat engine. Answers come from what the connected contract grants. A contract is the saved list of what one actor may do. Granted recipes can be called as tools. They follow the same approval rules as everything else. The privacy alias rule applies too. Known names, emails, phone numbers, and addresses are swapped for placeholder aliases before text leaves for the model. Your chat history stays in your own app. The server does not mix it into the owner's chat history.

#Streaming, and what the gateway is not

Two things to know. Streaming works: set stream: true and the answer comes back as chunks, the way OpenAI sends them. The whole turn still runs first, and the gate still checks it. While it runs, the gateway keeps the connection open with small keep-alive lines, so a long turn does not time out. Then it sends the answer in pieces. Ask for stream_options.include_usage and you also get the token counts at the end. And expect chat completions only. This is a chat surface. It is not a full copy of the OpenAI platform.

#Chat platforms

Slack and Telegram connect as messenger doors. Messages and slash commands POST straight to your server. They never go through Recued's cloud. Replies, notifications, and approvals can reach you in the same channel.

#Your own devices are different

The webclient and the Browser Bridge do not come in through doors. They pair. Pairing links a device to your server. It is a narrower, more trusted link. It is only for machines you own. See Pairing and devices.

#What every connection shares

No matter which app it is, the same things hold. The caller has a name. Its access is exactly what its door or contract grants. Every call is written in the audit diary. Rate and usage limits apply where the door sets them. And taking access back is one action: close the door, or issue a new secret key.

Recued Docs

Search documentation

Start typing to search the documentation.