Skip to content
Ren Docs
Book a demo

Give your agent access to Ren

Ren is one backend with many ways in. In this tutorial you’ll connect Ren to the coding agent you already use (for example, Claude Code), run Ren from inside it, and deploy your agent stack so it’s reachable from every client: coding agents, MCPs, and the SDK.

1. Run Ren from your coding agent

Install the Ren plugin into your coding agent so it can pair the Ren CLI and call Ren on your behalf.

  1. Install the Ren plugin for your coding agent.

  2. Pair it with your account. The plugin runs ren init and signs you in.

  3. Confirm the connection:

    Terminal window
    ren whoami

Your coding agent can now create sessions, run agents, and manage resources on Ren directly from your editor.

2. Deploy your agent stack to Ren

Define your agents, skills, and MCPs as code, then deploy them to Ren so they run on managed compute instead of your laptop.

  1. From your coding agent, create an agent and publish a version with its system prompt and model.
  2. Attach skills and MCP servers the agent needs.
  3. Deploy the stack to a project on your pod.

Once deployed, the stack lives on Ren: versioned, observable, and shareable across your org.

3. Reach it from every client

Because the stack runs on Ren’s backend, the same agents are reachable from any entry point:

ClientHow it connects
Coding agentsThrough the Ren plugin and CLI, from inside your editor
MCPsThe Ren MCP tools (such as session.create) expose your agents to tools
TypeScript SDKThe TypeScript SDK wraps the API
CLI / APIThe Ren CLI and REST API drive everything

What you built

You connected your coding agent to Ren, deployed an agent stack to managed compute, and made it reachable from every Ren client.

Next steps