Skip to main content
Glama
Code-MeMX

code-me-brand

Official
by Code-MeMX
OverviewSchemaRelated ServersScoreDiscussions
Local

Code-Me Brand MCP Server

Este es un servidor Model Context Protocol (MCP) diseñado exclusivamente para inyectar la identidad de marca, filosofía, tono de voz y lineamientos visuales de Code-Me directamente en cualquier cliente LLM (como Claude Desktop, Antigravity, Cursor, etc.).

Al estar empaquetado con los archivos de contexto en formato .mdx directamente en el código fuente, este servidor responde con latencia cero, permitiendo a la IA acceder a todas las reglas de forma instantánea sin hacer consultas externas.

🚀 Instalación y Uso

1. Despliegue en la Nube (Online SSE)

El servidor soporta de forma nativa SSE (Server-Sent Events) sobre HTTP, listo para desplegarse en plataformas como Render, Railway o Heroku.

Si defines la variable de entorno PORT, el servidor levantará una API de Express en automático:

# Instalar dependencias
npm install

# Iniciar servidor online
PORT=3000 npm start

  • Endpoint de Conexión SSE: http://<tu-dominio>/mcp

  • Endpoint de Mensajes: http://<tu-dominio>/message

2. Uso Local (Cursor / Claude Desktop)

Por defecto, si no se detecta la variable PORT, el servidor se ejecuta en modo local usando STDIO (Standard Input/Output).

git clone https://github.com/Code-MeMX/mcp-brand.git
cd mcp-brand
npm install

Para Cursor:

Abre la configuración del servidor en tu cliente MCP (ej. claude_desktop_config.json):

{
  "mcpServers": {
    "code-me-brand": {
      "command": "node",
      "args": [
        "/ruta/absoluta/a/este/repositorio/index.js"
      ]
    }
  }
}

Related MCP server: tenets

🛠 Herramientas (Tools)

El servidor expone herramientas para que la IA pueda leer activamente el manual de marca según lo necesite:

  • get_brand_identity: Extrae la filosofía central, misión, visión y significado del nombre (Corporativa).

  • get_tone_of_voice: Extrae las reglas de lenguaje, Spanglish, y cómo hablarle a papás o alumnos.

  • get_visual_guidelines: Extrae la lógica detrás de logotipos, tipografías y el estilo visual técnico de la marca.

  • get_mascota: Extrae la personalidad y reglas de comportamiento de Bitxo, nuestra mascota tipo Rubber Duck.

✍️ Plantillas Generativas (Prompts)

Para facilitar la creación de contenido, el servidor ofrece "Prompts" listos para usarse. Estos prompts empaquetan las instrucciones maestras de marca y guían a la IA para hacer el trabajo duro por ti:

  • write_social_post: Crea publicaciones de redes sociales ajustando el tono a la audiencia (teens vs padres).

  • generate_tagline: Genera slogans poderosos usando el framework "Regenera tu Futuro".

  • write_sales_pitch: Redacta correos o mensajes de venta agresivos pero profesionales para escuelas/inversionistas.

  • validate_tone: Actúa como un Linter de Escritura, revisando textos aburridos y reescribiéndolos con la actitud Hacker y Spanglish de la marca.

  • write_class_intro: Diseña introducciones súper gamificadas para las clases de los alumnos.

  • write_parent_newsletter: Genera boletines serios pero aspiracionales para tranquilizar e informar a los padres.

  • generate_bitxo_dialogue: Genera mensajes de interfaz o tooltips como si los estuviera diciendo la mascota Bitxo.

Code-Me: Regenera tu futuro.

Available Tools

4 tools
get_brand_identityA

Retrieves the Code-Me brand identity (naming, philosophy, tagline). Use this to understand the core mission and vision.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden. It clearly communicates a read-only operation via 'Retrieves', and the purpose adds context about what the data represents. It doesn't delve into return formatting or side effects, but for a simple getter, this is acceptable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no redundancy. The first sentence states the core function, the second explains the intended use. Very efficient and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-parameter, read-only tool with a clear purpose, the description is complete. It lists the key components of the brand identity and explains when to use it, covering all necessary context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the baseline is 4. The description adds no parameter details because none exist; the schema already covers everything (empty schema).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it retrieves the Code-Me brand identity, listing specific elements (naming, philosophy, tagline). This distinguishes it from sibling tools like tone of voice, visual guidelines, and mascota.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear context for when to use this tool: to understand the core mission and vision. It doesn't explicitly mention alternatives or when not to use it, but the guidance is sufficient for the intended use case.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_mascotaA

Retrieves the Code-Me mascot rules and personality (Bitxo).

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the burden. The verb 'Retrieves' implies a safe, non-destructive read operation, which is appropriate for a getter with no parameters. It does not disclose return format or potential side effects, but for a simple getter this is acceptable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no wasted words. It efficiently conveys the tool's purpose and specific subject (Bitxo).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (no params, simple getter), the description is sufficient. It explains what is retrieved (rules and personality), which serves as a proxy for return value expectations, even without an output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the description need not explain parameter semantics. Schema coverage is trivially 100%, and the baseline for zero params is 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Retrieves' and specifies the resource as 'Code-Me mascot rules and personality (Bitxo)'. This distinguishes it from sibling tools like get_brand_identity and get_tone_of_voice, which target different aspects of brand assets.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for retrieving mascot-related information but does not explicitly state when to use this tool over alternatives or provide exclusions. With sibling tools present, explicit guidance would improve clarity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_tone_of_voiceA

Retrieves the Code-Me tone of voice rules and language guidelines. Use this to validate or generate text for different audiences (parents, students, teachers).

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full responsibility for behavioral disclosure. It clearly indicates the operation is a read-only retrieval ('Retrieves'), and specifies the content scope (tone of voice rules). For a zero-parameter getter, this is adequate transparency without hidden side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences with the primary purpose front-loaded ('Retrieves...') and usage guidance immediately following. No redundant or filler content, every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple zero-parameter retrieval tool with no output schema, the description is complete: it states what the tool returns and how to use it. No missing information that would impair selection or invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, so the description does not need to add parameter-level details. Per the baseline for 0 params, a score of 4 is appropriate because the empty schema is entirely self-explanatory.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Retrieves') with a clear resource ('Code-Me tone of voice rules and language guidelines'). It distinguishes from sibling tools like get_brand_identity and get_visual_guidelines by focusing on tone/language, making its purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use the tool: 'Use this to validate or generate text for different audiences (parents, students, teachers).' This provides clear context for usage, though it does not explicitly call out alternatives or exclusions, which would be a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_visual_guidelinesA

Retrieves the Code-Me visual guidelines including colors, typography, logos, and illustration rules.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must convey behavioral expectations. It states 'Retrieves,' implying a read-only operation, and lists the content areas. However, it does not mention permissions, return format, or potential side effects. The tool is simple and non-destructive, so the minimal disclosure is acceptable, but richer context would be beneficial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, focused sentence that immediately states the purpose and content scope. It contains no filler or redundant information, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-parameter retrieval tool, the description adequately captures the essential information. However, the existence of sibling tools (get_brand_identity, get_tone_of_voice) introduces potential ambiguity about which tool to use, and the description does not address this. Adding a note about when to choose this tool would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the input schema fully describes the interface. With 0 parameters, the baseline score is 4, and there is no need for the description to elaborate on parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Retrieves') and a clear resource ('Code-Me visual guidelines'), and further specifies the content scope (colors, typography, logos, illustration rules). It does not explicitly differentiate from siblings like get_brand_identity, but the content list provides some distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given on when to use this tool versus the sibling tools (get_brand_identity, get_tone_of_voice, get_mascota). There are no conditions, alternatives, or exclusions mentioned, leaving the agent without information on choosing the appropriate tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 4 tool updatesv1.0.0
    • First observedget_brand_identity
    • First observedget_mascota
    • First observedget_tone_of_voice
    • First observedget_visual_guidelines
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.2/5.0
Disambiguation5/5

Each tool retrieves a distinct brand asset: identity, tone, visual guidelines, and mascot. There is no overlap in purpose or content, making selection unambiguous.

Naming Consistency5/5

All tool names follow the consistent 'get_' prefix followed by the specific asset type (identity, tone_of_voice, visual_guidelines, mascota). This is a uniform and predictable naming pattern.

Tool Count5/5

Four tools is well-suited for a brand information server. Each tool covers a distinct main aspect of the brand, and the count feels neither too sparse nor bloated for the domain.

Completeness5/5

The tool set comprehensively covers the primary dimensions of a brand identity: mission/philosophy, tone, visual style, and mascot. For a read-only retrieval server, this is a complete surface with no obvious gaps.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • MCP Prompt Enhancer

    soniankur948
    F
    license
    Not graded
    quality
    C
    maintenance
    Intelligently analyzes codebases to enhance LLM prompts with relevant context, featuring adaptive context management and task detection to produce higher quality AI responses.
    2
    -

  • tenets

    jddunn
    A
    license
    Not graded
    quality
    A
    maintenance
    Provides intelligent code context aggregation using NLP-based ranking (BM25, TF-IDF, embeddings) and automatically injects guiding principles (coding standards, architecture rules) into every prompt to maintain consistency across AI conversations.
    8
    MIT

  • Marketing Brain

    Felipe-Cal
    F
    license
    A
    quality
    D
    maintenance
    Provides standardized brand guidelines and structured content templates for marketing assets like blogs, emails, and social media. It serves as a central source of truth for brand voice and strategy through an extensible file-based system.
    1
    -

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Code-MeMX/mcp-brand'

If you have feedback or need assistance with the MCP directory API, please join our Discord server