How to integrate Render MCP with DeepSeek Harness

Connect DeepSeek Harness to Render MCP. Deploy latest code to staging service, restart production web service now, and more using natural language, with authentication handled for you.

Render logoRender
Api Key

Render is a unified cloud platform for building and running apps and websites. It simplifies deployment, scaling, and management across your projects.

95 Tools

Introduction

DeepSeek Harness (dsh) is an open-source agent runtime from DeepSeek AI, and every part of it is a plugin, so you can swap out the model adapter, the tool registry, or the agent loop. It runs on the Cordis framework and comes with a local Web UI, a headless CLI runner, and a Python SDK. You can point it at DeepSeek V4-Pro and V4-Flash, or at Anthropic, OpenAI, and other OpenAI-compatible providers. It is MIT licensed and still in developer preview.

This guide shows how to connect your Render account to DeepSeek Harness, and you can do it with either the Composio Connect CLI or the Composio Connect MCP. The dsh-base bundle gives shell execution as a first-class tool, so the CLI is the easiest path for personal use. It is quick to set up and needs no server config, and the MCP path works well too, since the harness comes with a built-in MCP client.

Also integrate Render with

What is Composio Connect?

Composio Connect lets anyone plug 1,000+ applications directly into their agent harness, including DeepSeek Harness, through a single hosted MCP endpoint. Each task runs as a session, a scoped runtime that ties together the user, the available toolkits, authentication, and execution state. It can:

  • Discover and load tools on-demand. A small set of meta tools lets the agent search for the right tool at runtime, so you never load hundreds of tool definitions into context.
  • Chain tools in a sandboxed remote workbench. Multi-step workflows run server-side, passing outputs between tools and working with files in the session's sandbox, so long chains finish without a lot of back-and-forth with the LLM.
  • Manage authentication end-to-end. Managed OAuth, per-user connected accounts, and account isolation are all handled for you, so you never wire up auth yourself.

Connect Render to DeepSeek Harness with Composio

Prerequisites: Install DeepSeek Harness

DeepSeek Harness needs Node.js (20 or 22) and pnpm. Build it from source. This is also what the MCP path in Option 2 requires, since the built-in MCP client resolves its dependencies from the checkout:

bash
git clone https://github.com/deepseek-ai/deepseek-harness.git
cd deepseek-harness
pnpm install
pnpm run build
pnpm dsh web

The Web UI listens on http://127.0.0.1:3080 by default. Open that address to confirm it is up.

Then configure your model route. In the Web UI, open Settings → Models: the built-in DeepSeek card accepts a DeepSeek API key, and the same page supports Anthropic, OpenAI, and custom OpenAI-compatible endpoints. Full first-run details are in the DeepSeek Harness docs.

Option 1: Composio CLI (recommended)

DeepSeek Harness runs shell commands as a first-class tool through its dsh-base bundle, so the Composio Universal CLI fits well. There is no MCP server to configure, and multi-step tool chaining is reliable. Install and authenticate:

bash
# Install the Composio CLI
curl -fsSL https://composio.dev/install | bash

# Log in to Composio
composio login

Connect to Render

Ask DeepSeek Harness to connect to Render, or just request any Render-related task. Under the hood the agent calls Composio commands like any other shell tool:

bash
composio search "what can I do with Render?"
composio link render

On the first Render call, composio link render opens an OAuth prompt so you can authorize access. After that, every Render command works with your stored credentials automatically, so you just talk to the agent and it will search, execute, and chain Render tools as needed.

Option 2: Composio MCP

DeepSeek Harness bridges MCP through its built-in @deepseek-ai/dsh-mcp-client plugin. You register one server as a plugin row, and its tools appear under server-qualified names (mcp__<serverName>__<rawName>), the same shape Claude Code and Codex use.

MCP requires the source build. The built-in client depends on the harness's own internal packages (cordis, dsh-llm, dsh-tools, dsh-invariants, dsh-subprocess), which resolve from the git checkout you built in the prerequisites. Run everything below from that checkout with pnpm dsh. For a route that avoids editing config files, see the community plugin at the end of this section.

Auth note: The built-in client passes static headers only and has no OAuth flow, so authenticate to Composio Connect with the x-consumer-api-key header. For Composio's OAuth flow, use the community plugin below.

1. Register the Composio server

The web profile's user patch layer is $DSH_HOME/profiles/web/cordis.patch.yml ($DSH_HOME defaults to ~/.dsh). This is a patch file, so a new plugin goes under an insert: entry. A bare - id: row instead targets an existing entry and fails to boot with patch: entry "…" not found. Add:

bash
- insert:
    - id: mcp-composio
      name: '@deepseek-ai/dsh-mcp-client'
      config:
        serverName: composio
        transport: streamable-http
        url: https://connect.composio.dev/mcp
        headers:
          x-consumer-api-key: !!js process.env.COMPOSIO_API_KEY

2. Set the API key and launch

The header value must resolve to a string at load time. Export your Composio consumer API key (ck_...), which is on the Connect → Settings → Sessions page of the Composio dashboard, in the shell you launch from. If it is unset, process.env.COMPOSIO_API_KEY is undefined and the config fails validation:

bash
export COMPOSIO_API_KEY=ck_your_key
pnpm dsh web

3. Done!

Open http://127.0.0.1:3080 and start a session on Standard or Code mode. (Minimal mode exposes only bash and str_replace_editor, so it hides MCP tools.) Composio's tools register as mcp__composio__*. Ask DeepSeek Harness to connect to Render or request any Render-related task, and Composio authorizes Render on demand on the first call.

The dsh-mcp-client config schema (transport, serverName, url, headers, plus reconnect.* and toolCallTimeoutMs) is the current developer-preview interface and may change between releases.

Alternative: OAuth via the community plugin

To use Composio Connect's OAuth flow instead of a static key, or to skip editing cordis.patch.yml by hand, use the community dsh-mcp-manager plugin. It installs as a self-contained external plugin, ships a bundle patch so it auto-mounts, and adds a Settings → MCP page plus OAuth (authorization code + PKCE, RFC 7591 dynamic client registration, and refresh-token rotation). It needs the web profile and Node.js ^22.19 or >=24, with pnpm on your PATH.

Install it from your source checkout, then restart pnpm dsh web and refresh:

bash
pnpm dsh plugin --profile web add github:hyqhyq3/dsh-mcp-manager

Open Settings → MCP → + Add MCP server, choose HTTP, set the name to composio, the URL to https://connect.composio.dev/mcp, and the auth mode to OAuth. Click Authenticate, and Composio's login and consent screen opens in the browser, then redirects back and registers the tools as mcp__composio__*. The row should read connected (N tools).

The plugin catches the OAuth code on a loopback redirect (http://127.0.0.1:<port>/mcp-manager/callback/<id>), so Composio's OAuth provider must allow that loopback URL. Server configs and tokens persist at ~/.dsh/mcp-manager.json, so treat that file as a secret. Being a community plugin on a preview harness, its commands may change, so check the plugin repo if a step drifts.

What is the Render MCP server, and what's possible with it?

The Render MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Render account. It provides structured and secure access to your cloud infrastructure, so your agent can perform actions like deploying applications, managing services, monitoring site health, restarting instances, and scaling resources on your behalf.

  • Automated application deployment: Instantly deploy new web apps or services without manual steps, letting your agent handle setup and rollouts.
  • Service monitoring and status checks: Ask your agent to check the health and uptime of your apps or services, so you’re always up to speed on what’s running smoothly—and what’s not.
  • Instance management and restarts: Enable your agent to restart, stop, or scale up/down your running services to quickly respond to changes or issues.
  • Resource scaling and configuration: Let your agent adjust resource allocations, increasing or decreasing capacity based on current needs or traffic spikes.
  • Error diagnostics and log retrieval: Have your agent fetch logs or error reports to help troubleshoot issues before they become major problems.

Way Forward

With Render connected, DeepSeek Harness can now act on your behalf whenever you ask it to.

From here, you can extend the harness further:

  • Connect more apps: Calendar, Slack, Notion, Linear, and hundreds of others are available through the same Composio Connect setup, and each new integration adds to what your agent can do for you.
  • Build workflows across tools: Once multiple apps are connected, DeepSeek Harness can chain actions together, so it can turn an email into a calendar invite, a Slack message into a Linear ticket, or a meeting note into a follow-up draft.
  • Use the plugin system: Wrap common Render flows as dsh plugins or prompt templates so recurring tasks become one-line commands, and bundle your most-used Render tools into a named profile you can boot on demand.

If you run into trouble or want to share what you've built, join the community or check out the Docs for more configuration options.

TOOLS

Supported Tools

Every Render action and event your agent gets out of the box.

Add Header Rule

Tool to add a custom HTTP header rule to a Render service.

Add or Update Secret File

Tool to add or update a secret file for a Render service.

Add Resources to Environment

Tool to add resources to a Render environment.

Add Route

Tool to add redirect or rewrite rules to a Render service.

Create Custom Domain

Tool to add a custom domain to a Render service.

Create Environment Group

Tool to create a new environment group.

Create Environment

Tool to create a new environment within a Render project.

Create Postgres Instance

Tool to create a new Postgres instance on Render.

Create Registry Credential

Tool to create a registry credential.

Delete Environment Group Variable

Tool to remove an environment variable from an environment group.

Delete Environment Group Secret File

Tool to remove a secret file from an environment group.

Delete Environment

Tool to delete a specified environment.

Delete Key Value

Tool to delete a Key Value instance.

Delete Owner Log Stream

Tool to delete a log stream for an owner.

Delete Owner Metrics Stream

Tool to delete a metrics stream for a workspace.

Delete Registry Credential

Tool to delete a registry credential.

Delete Secret File

Tool to delete a secret file from a Render service.

Delete Service

Tool to delete a service.

Disconnect Blueprint

Tool to disconnect a blueprint from your Render account.

Get Active Connections

Tool to get active connection count metrics for Render resources.

Get Bandwidth Sources

Tool to get bandwidth usage breakdown by traffic source.

Get CPU Usage

Tool to retrieve CPU usage metrics for Render resources.

Get CPU Limit

Tool to retrieve CPU limit metrics for Render resources.

Get Disk Capacity

Tool to get disk capacity metrics for Render resources.

Get Disk Usage

Tool to retrieve disk usage metrics for Render resources.

Get Instance Count

Tool to get instance count metrics for Render resources.

Get Memory Usage

Tool to get memory usage metrics for one or more resources.

Get Memory Limit

Tool to get memory limit metrics for Render resources over a specified time range.

Get Memory Target

Tool to get memory target metrics for Render resources.

Get User

Tool to get the authenticated user.

Link Service to Environment Group

Tool to link a service to an environment group.

List Application Filter Values

Tool to list queryable instance values for application metrics.

List Blueprints

Tool to list all blueprints.

List Deploys

Tool to list recent deploys for a Render service with pagination and filtering.

List Disks

Tool to list all disks.

List Environment Groups

Tool to list environment groups.

List Environments

Tool to list environments for a project.

List Environment Variables for Service

Tool to list all environment variables configured directly on a Render service (with pagination).

List Instances

Tool to list instances of a service.

List Key Value Instances

Tool to list all Key Value instances.

List Logs

Tool to list logs for a specific workspace and resource.

List Log Label Values

Tool to list log label values for a workspace.

List Maintenance Runs

Tool to list maintenance runs.

List Notification Overrides

Tool to list notification overrides for services.

List Workspace Members

Tool to list workspace members.

List Owners

Tool to list owners (users and teams).

List Postgres Instances

Tool to list Postgres instances.

List Postgres Exports

Tool to list all exports for a Postgres instance.

List PostgreSQL Users

Tool to list PostgreSQL user credentials for a Render PostgreSQL database instance.

List Projects

List Projects

List Registry Credentials

Tool to list registry credentials.

List Resource Log Streams

Tool to list resource log stream overrides.

List Routes

Tool to list redirect/rewrite rules for a service.

List Secret Files

Tool to list secret files for a Render service.

List Services

Tool to list all services.

List Task Runs

Tool to list task runs.

List Tasks

Tool to list tasks.

List Webhooks

Tool to list all webhooks.

List Workflows

Tool to list workflows.

List Workflow Versions

Tool to list workflow versions.

Restart Service

Tool to restart a service.

Resume Service

Tool to resume a suspended service.

Retrieve Custom Domain

Tool to retrieve a specific custom domain for a service.

Retrieve deploy

Retrieve deploy

Retrieve Environment Group

Tool to retrieve a specific environment group by ID.

Retrieve Environment Variable

Tool to retrieve a specific environment variable from a Render environment group.

Retrieve Environment Group Secret File

Tool to retrieve secret file from an environment group.

Retrieve Environment Variable

Tool to retrieve a specific environment variable from a Render service.

Retrieve Owner

Tool to retrieve a specific owner (workspace) by ID.

Retrieve Owner Notification Settings

Tool to retrieve notification settings for a specific owner (workspace).

Retrieve Postgres Instance

Tool to retrieve a specific Postgres instance.

Retrieve Project

Tool to retrieve a specific project by ID.

Retrieve Registry Credential

Tool to retrieve a registry credential by ID.

Retrieve Secret File

Tool to retrieve a secret file from a Render service.

Retrieve Service

Tool to retrieve a specific service by ID.

Stream Task Runs Events

Tool to stream real-time task run events via Server-Sent Events (SSE).

Subscribe to Logs

Tool to subscribe to real-time logs via WebSocket connection.

Suspend Service

Tool to suspend a service.

Trigger Deploy

Tool to trigger a new deploy for a specified service.

Update Environment Group

Tool to update an environment group's name.

Update Environment Group Variable

Tool to add or update an environment variable in an environment group.

Update Environment Group Secret File

Tool to add or update a secret file in an environment group.

Update Environment Variable

Tool to add or update an environment variable for a Render service.

Update Environment Variables for Service

Tool to update environment variables for a Render service.

Update Header Rules

Tool to replace all header rules for a Render service.

Update Owner Log Stream

Tool to update log stream configuration for an owner.

Update Owner Notification Settings

Tool to update notification settings for a specific owner (workspace).

Update Postgres Instance

Tool to update a Postgres instance configuration.

Update Project

Tool to update a project's name.

Update Registry Credential

Tool to update a registry credential.

Update Resource Log Stream

Tool to update log stream override for a resource.

Update Routes

Tool to update redirect/rewrite rules for a service.

Update Secret Files for Service

Tool to update secret files for a Render service.

Update Service

Tool to update a service configuration.

Verify Custom Domain

Tool to verify DNS configuration for a custom domain.

FAQ

Frequently asked questions

With a standalone Render MCP server, the agents and LLMs can only access a fixed set of Render tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Render and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. DeepSeek Harness fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Render tools.

Yes, absolutely. You can configure which Render scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Render data and credentials are handled as safely as possible.

Start with Render.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Render tool your agent needs.Free to start.

Start building