Connecting
- In your AI app, add a remote MCP server pointed at
https://workspace.beunec.com/mcp. - The app opens an Aselius sign-in page. Sign in with your Aselius account and approve the connection. This is a standard OAuth sign-in, so your password is never shared with the app.
- The app then lists what Aselius offers: the four tools below and the engines and specialties you can choose. Everything comes from Aselius itself, so there is nothing else to install or configure.
What it can do
| Tool | What it does |
|---|---|
start_task | Starts a task on the Rivine engine and specialty you name, for example Rivine Research · PDF or Rivine Cicero · Contract Review. |
get_task | Shows a task's status, the steps it has taken so far, and any question it is waiting on. |
answer_task | Answers a question the engine asked. The task continues from exactly where it stopped. |
cancel_task | Stops a running task. |
When a task finishes, results arrive as one-tap preview links to preview.aselius.beunec.com alongside the plain file downloads, so any app can show them.
Note: Your app can attach an optional idempotency key when it starts a task. If the same request is sent twice, for example after a dropped connection, Aselius recognises it and never starts or bills the task a second time.
What it does not offer
Aselius MCP runs engine tasks; it is not a copy of the Workspace interface. It does not expose Rivine Code, Rivine Browse or Rivine Assist, because they need a live code sandbox, your own browser session, or a document already open on screen. Use the Aselius web app for those.
Billing
A task started over MCP spends from the same prepaid wallet as every other surface, at the same engine start floor as the web app. It is available on every plan.