Install and Connect to a Workspace

Clone the open-source Context Engine Studio, point it at your workspace, and run it locally.

By the end of this page, the Context Engine Studio runs at http://localhost:3000 against your workspace.

Prerequisites

You need four things before you start:

A workspace with OAuth credentials that have Read & Write access. See Provision Your First Workspace and Authentication and Credentials.
Node.js 20.9 or later, which Next.js 16 requires. The repository's .nvmrc pins Node 24.
pnpm 10 or later. Running corepack enable installs the exact version the repository pins.
An Anthropic API key with access to claude-opus-4-8. The studio does not start without one, even if you never open the chat.

Steps

Clone the repository

git clone https://github.com/clinia/context-engine-studio.git
cd context-engine-studio

Configure the connection to your workspace

Copy .env.example to .env.local and fill in the four required values. The example file already lists each of them with a comment.

cp .env.example .env.local

Variable	What to put
`CLINIA_CONTEXT_ENGINE_API_URL`	Your workspace's base URL, `https://<workspace-id>.w.clinia.cloud`.
`CLINIA_CONTEXT_ENGINE_OAUTH_CLIENT_ID`	The client ID of your credential.
`CLINIA_CONTEXT_ENGINE_OAUTH_CLIENT_SECRET`	The client secret, which the Console shows once, when you create the credential.
`ANTHROPIC_API_KEY`	Your Anthropic API key.

Install and start

pnpm install
pnpm dev

Open the studio

Open http://localhost:3000. An empty workspace opens on the Add your first patient screen. A workspace that already has patients opens on the first of them.

When the studio does not start

Three configuration mistakes cause most of the problems at this stage:

A missing client ID or secret stops the studio at startup, with an error that names both variables.
Read-only credentials let the studio start and browse, then fail when you create a patient or ingest a record.
CLINIA_CONTEXT_ENGINE_API_URL is the workspace's base URL, without /v1 or /mcp. The studio adds /mcp itself to reach the MCP server the chat assistant uses.

Next steps

Explore a Patient to ingest the synthetic dataset and walk through what the studio shows.
Authentication and Credentials to rotate or replace the credential the studio uses.

On this page