Atlas / MCP servers / bradfair / Cline Personas

Cline PersonasSAFE

mcp/bradfair/cline-personas

An MCP server for managing `.clinerules` files using shared components and persona templates.

Verdict
SAFE
Grade
B
Trust score
89 /100
Exposed tools
11 7r · 2w · 2d
Transport
stdio
License
MIT
Stars
23
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

An MCP server for managing .clinerules files using shared components and persona templates.

Features

  • Component Management: Create, read, update and delete reusable components
  • Persona Templates: Define persona templates with mustache-style variable substitution
  • Dependency Validation: Ensure persona templates only reference existing components
  • Activation System: Activate personas by writing to .clinerules file
  • Version Tracking: Track versions for both components and personas
  • File-based Storage: Store components and personas as JSON files

Installation

  1. Clone the repository
  2. Install dependencies:
npm install
  1. Build the project:
npm run build

Usage

Managing Components

import { ComponentPersonaService } from './src/service';

const service = new ComponentPersonaService(process.cwd());

// Create a new component
service.setComponent('greeting', 'Welcome message', 'Hello {{name}}!', 1);

// Get a component
const component = service.getComponent('greeting');

// List all components
const components = service.listComponents();

Managing Personas

// Create a new persona
service.setPersona(
'welcome',
'Welcome persona',
'{{greeting}}\nPlease enjoy your stay!',
1
);

// Activate a persona
service.activatePersona('welcome');

// Get active persona
const active = service.getActivePersona();

File Structure

.cline-personas/
components/
[component-name].json
personas/
[persona-name].json
src/
component.ts    # Component class and operations
persona.ts      # Persona class and template rendering
service.ts      # Main service implementation
index.ts        # MCP server entry point
test/             # Unit tests

API Documentation

ComponentPersonaService

The main service class providing all operations:

  • Component Operations:
  • `setComponent(name, description, text, versio
Read from source at commit a3c95917c23fOBSERVED · 2026-10-09
02

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.

claude-code
claude mcp add cline-personas -- npx -y [email protected]
claude-desktop
{
  "mcpServers": {
    "cline-personas": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ]
    }
  }
}
03

Exposed tools (11)

7 read · 2 write · 2 destructive. Blast radius: 2 tools can delete or overwrite — an agent that can be talked into calling a tool can be talked into calling this one.

ToolRiskDescription
TestreadDescription
activatePersonareadActivate a specific persona
createOrUpdateComponentwriteCreate or update a component
createOrUpdatePersonawriteCreate or update a persona
deleteComponentdestructiveDelete a component
deletePersonadestructiveDelete a persona
getActivePersonareadGet the currently active persona
listComponentsreadList all available components
listPersonasreadList all available personas
test-componentreadtest description
test-personareadtest description
04

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codePASS
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfaceWARN
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
declared (1 observation(s))
Network
none-observed
Shell
none-observed
Dependencies
not all pinned
Secrets in source
none-found

Findings (2)

MEDIUMFilesystem / path · mcp.destructive_tools · CWE-22, CWE-59
deleteComponent, deletePersona
Why it matters. 2 tool(s) can delete or overwrite
Fix. prefer a read-only mode or scoped tokens; the page states the blast radius
LOWSupply chain · supply.unpinned · CWE-829, CWE-1357
package.json
@modelcontextprotocol/sdk, zod, zod-to-json-schema, @babel/plugin-transform-modules-commonjs, @babel/plugin-transform-runtime, @babel/preset-env, @types/jest, @types/node
Why it matters. 17 dependency range(s) float
Fix. pin exact versions or ship a lockfile

Gates applied: no_behavioural_pass.

Audited 2026-10-09 · audit v0.4.1 · source sha a3c95917c23ffull audit observations/trust-audit/mcp-server/bradfair__cline-personas.json · Report an issue / request a re-scan
05

Audit history

Every audit this server has had. A grade with a past is a grade somebody is still checking.

DateSourceVerdictGradeScoreChange
2026-10-09a3c95917c23fSAFEB89first audit
06

Questions

What is the Cline Personas MCP server?

An MCP server for managing `.clinerules` files using shared components and persona templates.

What tools does Cline Personas expose?

11 in total: 7 read-only, 2 that write, and 2 that can delete or overwrite (deleteComponent, deletePersona). Every one is listed on this page with its risk.

Is Cline Personas safe to connect to an agent?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B. Separately from the audit: 2 of its tools can destroy data, so scope the token you give it to what you actually need.

What credentials does Cline Personas need?

No credential environment variables were found in its source, so it appears to need none.

How does Cline Personas run?

It speaks stdio, so it runs as a local process your client starts. It is published on npm as cline-personas at 0.1.0.

How current is this page?

The grade is for one exact copy of the source (a3c95917c23f), read on 2026-10-09. The repository is watched and re-audited when it changes.

Advertisement