About Cline Personas MCP Server
Cline Personas MCP Server manages reusable components and persona templates for `.clinerules` files. It is intended for developers organizing Cline configurations, with template variables, dependency checks, version tracking, and JSON file storage.
Key features
- 01Create, read, update, and delete components
- 02Manage persona templates
- 03Use Mustache-style variables
- 04Validate template component dependencies
- 05Activate personas in `.clinerules`
- 06Track component and persona versions
Use cases
- 01Reuse rule components across projects
- 02Define persona templates for different tasks
- 03Check that referenced template components exist
- 04Apply a chosen persona to `.clinerules`
MCP support
The MCP server provides component and persona management, including template rendering and activation operations.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMECline Personas MCP Server
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
.clinerulesfile - Version Tracking: Track versions for both components and personas
- File-based Storage: Store components and personas as JSON files
Installation
- Clone the repository
- Install dependencies:
npm install
- 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, version)getComponent(name)listComponents()deleteComponent(name)
-
Persona Operations:
setPersona(name, description, template, version)getPersona(name)listPersonas()deletePersona(name)activatePersona(name)getActivePersona()renderPersona(name)
Development
Run tests:
npm test
Build the project:
npm run build
Run the MCP server:
npm start
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.