Skip to main content
Glama
enesjakozh
glifxyz

Glif

Official
by glifxyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

servidor glif-mcp

Servidor MCP para ejecutar flujos de trabajo de IA desde glif.app.

Este servidor proporciona herramientas para ejecutar glifs, administrar bots y acceder a metadatos de glifs a través del Protocolo de contexto de modelo (MCP).

Este servidor también permite personalizar todas las herramientas disponibles mediante metaherramientas para agregar y quitar herramientas, entre otras, incluyendo muchos agentes glif completos como conjunto de herramientas (y personalidad). Esto es altamente experimental.

Para obtener más información, consulte https://glif.app o únase a nuestro servidor Discord: https://discord.gg/glif

Características

  • Ejecutar glifs con entradas

  • Obtenga información detallada sobre glifs, ejecuciones y usuarios

  • Acceda a metadatos de glif a través de recursos basados en URI

Related MCP server: mcp-comfyui

Configuración

Ejecución mediante npx (recomendado)

Si tiene nodejs instalado, puede ejecutar nuestro paquete @glifxyz/glif-mcp-server a través de npx:

  1. Obtén tu token API desde https://glif.app/settings/api-tokens

  2. Añade el servidor en el archivo de configuración de Claude Desktop. En macOS, este es: ~/Library/Application Support/Claude/claude_desktop_config.json

    {
  "mcpServers": {
    "glif": {
      "command": "npx",
      "args": ["-y", "@glifxyz/glif-mcp-server@latest"],
      "env": {
        "GLIF_API_TOKEN": "your-token-here"
      }
    }
  }
}

Corriendo desde una caja local

Primero, revise este código e instale las dependencias.

git clone https://github.com/glifxyz/glif-mcp-server
cd glif-mcp-server
npm install
npm run build
# there's now a build/index.js file which is what we'll run next

Luego configure su cliente MCP (por ejemplo, Claude Desktop) para cargar este servidor desde el disco.

{
  "mcpServers": {
    "glif": {
      "command": "node",
      "args": ["/path/to/glif-mcp/build/index.js"],
      "env": {
        "GLIF_API_TOKEN": "your-token-here"
      }
    }
  }
}

También puede especificar los ID de glifs (separados por comas) que se cargarán automáticamente al iniciar el servidor. Esto es útil para realizar pruebas o si desea compartir una configuración de glif predefinida con otra persona.

{
  "mcpServers": {
    "glif": {
      "command": "node",
      "args": ["/path/to/glif-mcp/build/index.js"],
      "env": {
        "GLIF_API_TOKEN": "your-token-here",
        "GLIF_IDS": "cm2v9aiga00008vfqdiximl2m,cm2v98jk6000r11afslqvooil,cm2v9rp66000bat9wr606qq6o",
        "IGNORE_SAVED_GLIFS": true,
      }
    }
  }
}

Ejecutar de forma remota con Smithery

Para instalar glif-mcp para Claude Desktop automáticamente a través de Smithery , que aloja y ejecuta el servidor MCP para usted:

npx -y @smithery/cli install @glifxyz/glif-mcp-server --client claude

Límites de uso

Recursos

  • glif://{id} - Obtener metadatos de glif

  • glifRun://{id} - Obtener detalles de la ejecución

  • glifUser://{id} - Obtener el perfil del usuario

Herramientas

Herramientas generales de Glif

  • run_glif - Ejecuta un glif con el ID y las entradas especificadas

  • glif_info - Obtenga información detallada sobre un glif, incluidos los campos de entrada

  • list_featured_glifs - Obtenga una lista seleccionada de glifs destacados

  • search_glifs - Busca glifs por nombre o descripción

Herramientas de bot

  • list_bots - Obtén una lista de bots destacados y plantillas de simulación

  • load_bot - Obtén información detallada sobre un bot específico, incluidas sus habilidades

  • save_bot_skills_as_tools : guarda todas las habilidades de un bot como herramientas individuales

Herramientas específicas del usuario

  • my_glifs - Obtén una lista de tus glifs

  • my_glif_user_info - Obtenga información detallada sobre su cuenta de usuario, glifs recientes y ejecuciones recientes

Glif->Herramientas Herramientas (metaherramientas)

  • save_glif_as_tool - Guardar un glif como una herramienta personalizada

  • remove_glif_tool - Eliminar una herramienta glif guardada

  • remove_all_glif_tools : elimina todas las herramientas glif guardadas y regresa a un estado original

  • list_saved_glif_tools - Lista todas las herramientas glif guardadas

Cómo convertir glifs en herramientas personalizadas

Tenemos una herramienta general run_glif , pero (a) no es muy descriptiva y (b) requiere primero una llamada glif_info para aprender a llamar a dicho glif. Además, es necesario saber que glif existe.

Estamos experimentando con varias metaherramientas nuevas que convierten glifs específicos en nuevas herramientas independientes:

Un ejemplo de sesión rápida:

  • ¿Cuales son algunos nuevos y geniales gráficos?

  • [toolcall: list_featured_glifs ...]

  • Vale, me gusta el generador de portadas de libros de ciencia ficción de los años 70. Conviértelo en una herramienta llamada "scifi_book_image".

  • [toolcall: save_glif_as_tool glifId=... toolName=scifi_book_image ]

  • [Ahora el usuario puede simplemente escribir "crear una imagen de libro de ciencia ficción de bla"]

Puede enumerar estas herramientas especiales con list_saved_glif_tools y eliminar cualquiera que no le guste con remove_glif_tool

Tenga en cuenta que Claude Desktop requiere reiniciarse para cargar nuevas definiciones de herramientas. Cline y Cursor parecen recargarse automáticamente al realizar cambios y volver a consultar las herramientas disponibles.

Información sobre los glifs del usuario autenticado:

  • my_glifs - glifs publicados por el usuario actual (sin drats)

  • my_liked_glifs - glifs que le gustan al usuario actual

  • my_runs - carreras públicas del usuario actual

Registros MCP

insignia de herrería

Desarrollo

Instalar dependencias:

npm install

Construir el servidor:

npm run build

Para desarrollo con reconstrucción automática:

npm run dev

Para ejecutar el conjunto de pruebas:

npm run test

Y ejecutar continuamente pruebas sobre los cambios:

npm run test:watch

Depuración

Dado que los servidores MCP se comunican a través de stdio, la depuración puede ser complicada. Recomendamos usar el Inspector MCP :

npm run inspector

El Inspector proporcionará una URL para acceder a las herramientas de depuración en su navegador.

También puedes consultar los registros glif-mcp dentro de los registros de Claude directamente si estás usando Claude Desktop.

Lanzando una nueva versión

  1. Edite package.json y src/index.ts y aumente el número de versión

  2. Ejecute npm install para actualizar las versiones almacenadas en el archivo de bloqueo

  3. Confirme y envíe sus cambios a GitHub y combínelos con el archivo principal

  4. Si tienes gh instalado, cambia a la versión principal y ejecuta npm run release Esto creará una etiqueta de Git para la nueva versión, la subirá a GitHub y usará gh release create para publicar la nueva versión con un registro de cambios generado automáticamente. Si no tienes gh , puedes hacer lo anterior manualmente en la interfaz web de GitHub.

  5. Una acción de GitHub utilizará el secreto NPM_TOKEN para publicarla en NPM

Licencia

Este proyecto está licenciado bajo la licencia MIT: consulte el archivo de LICENCIA para obtener más detalles.

Available Tools

6 tools
my_user_infoA
Read-only
Inspect

Get detailed information about your Glif account, including profile info, recent workflows, and recent runs.

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?

Annotations already declare readOnlyHint=true, confirming no side effects. The description adds value by specifying returned data categories (profile, workflows, runs), going beyond the annotation. No contradictions.

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?

Single, front-loaded sentence that efficiently communicates purpose and key return categories. No wasted words.

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 zero parameters and a simple read-only operation, the description adequately covers what the tool returns (profile, workflows, runs). No output schema, but the listing of categories provides sufficient context for an agent.

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?

No parameters in input schema (100% coverage by schema). Baseline is 4; description does not need to add parameter details. No additional semantics required.

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 tool's purpose: retrieving detailed account info including profile, recent workflows, and recent runs. It distinguishes itself from siblings like my_workflows (which likely focuses on workflows alone) and search_workflows.

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 getting the current user's account details, but lacks explicit guidance on when to use versus siblings (e.g., when to use my_workflows instead for workflow-only data). No when-not or alternative suggestions.

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

my_workflowsA
Read-only
Inspect

Get a list of your published workflows (glifs). Shows your AI workflows with run counts and creation dates.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4/5.0
Behavior3/5

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

Annotations include readOnlyHint=true, which is consistent with the description. The description adds minor behavioral context (what data is shown) but does not cover potential issues like pagination or rate limits. No contradiction with annotations.

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 no fluff. The purpose is front-loaded, and the second sentence adds relevant details. Every word earns its place.

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 no parameters and no output schema, the description adequately explains what the tool returns. It could mention pagination or ordering but is largely sufficient for a simple list tool.

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 input schema has no parameters, so schema coverage is 100%. The description adds value by clarifying that the list is scoped to the user's own workflows, which is not evident from the schema alone.

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 'get a list', the resource 'your published workflows (glifs)', and specific details like 'run counts and creation dates'. It distinguishes from sibling tools such as list_featured_workflows and search_workflows.

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 personal workflows but does not explicitly state when to use this tool over alternatives like list_featured_workflows or search_workflows. No when-not or alternative naming is provided.

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

run_workflowAInspect

Run a workflow (glif) with the specified ID and inputs. Workflows can generate images, text, audio, and more. Inputs can include text, URLs, or base64-encoded media.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the workflow (glif) to run
inputsYesArray of input values. Can be text, media URLs, or base64-encoded media (data:image/png;base64,... or data:image/jpeg;base64,...)

TDQS

A3.9/5.0
Behavior3/5

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

Annotations indicate non-read-only and non-destructive behavior. The description adds that it generates media but does not disclose potential side effects, idempotency, or reliability characteristics.

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 concise with two sentences, front-loading purpose and adding relevant context about output types and input formats without redundancy.

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

Completeness3/5

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

The description mentions potential output types but lacks details on return values, as there is no output schema. It also omits guidance on error handling or post-invocation steps, leaving gaps for an agent.

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 input schema covers both parameters, and the description adds value by specifying acceptable input formats (text, URLs, base64-encoded media) beyond the array-of-strings type, aiding correct usage.

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 'Run' and the resource 'workflow (glif)', specifying that workflows generate various outputs. This distinguishes it from sibling tools like list_featured_workflows and search_workflows.

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 by stating its function but does not provide explicit guidance on when to use it versus alternatives. It lacks exclusion criteria or context about prerequisites.

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

search_workflowsA
Read-only
Inspect

Search for workflows (glifs) by name, description, or keywords. Find AI tools for image generation, text processing, and more.

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query string

TDQS

A3.8/5.0
Behavior3/5

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

Annotations include readOnlyHint: true, which is consistent. The description adds that it searches by name, description, or keywords, but no additional behavioral details beyond what annotations provide.

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, front-loaded with purpose, no unnecessary words. Efficient and clear.

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 simple tool (one parameter, no output schema), the description adequately covers what it does and the types of results it returns. Could mention return format but not critical.

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?

Schema coverage is 100% with one parameter. The description adds context that the query can be by name, description, or keywords, which adds meaning beyond the schema's 'Search query string'.

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 tool name and description clearly state the action (search) and resource (workflows/glifs). It distinguishes from sibling tools like list_featured_workflows by implying a general search across all workflows.

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?

The description provides no guidance on when to use this tool versus alternatives like list_featured_workflows or my_workflows. No context on when to search vs list.

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

workflow_infoA
Read-only
Inspect

Get detailed information about a workflow (glif) including its input fields, recent runs, and creator info.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the workflow (glif) to show details for

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already indicate read-only (readOnlyHint: true). The description adds valuable detail about the return content (input fields, recent runs, creator info), making behavior transparent beyond the annotation.

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?

Single sentence that is concise, front-loaded with the action, and contains no extraneous words.

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?

Given the tool's simplicity (one parameter, no output schema), the description provides sufficient context—what the tool does and what it returns—making it complete.

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

Parameters3/5

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

Schema covers the single parameter 'id' fully (100% coverage). The description does not add additional meaning about the parameter beyond the schema, leading to baseline score.

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 clearly states it retrieves detailed information about a specific workflow, including inputs, runs, and creator. It distinguishes from siblings like list_featured_workflows (list) and run_workflow (execute), but does not explicitly contrast with alternatives.

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 on when to use this tool versus siblings such as search_workflows or my_workflows. The description only explains the tool's function without providing use-case context.

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.

  1. 6 tool updatesv0.9.5
    • First observedlist_featured_workflows
    • First observedmy_user_info
    • First observedmy_workflows
    • First observedrun_workflow
    • First observedsearch_workflows
    • First observedworkflow_info
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.9/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: listing featured workflows, user info, personal workflows, running a workflow, searching workflows, and workflow details. No overlap or ambiguity.

Naming Consistency3/5

Naming patterns are mixed: some use verb+noun (list_featured_workflows, run_workflow, search_workflows), some use possessive+noun (my_user_info, my_workflows), and one uses noun+noun (workflow_info). This inconsistency could confuse an agent.

Tool Count5/5

6 tools is well-scoped for a workflow platform, covering essential operations without being overwhelming or too sparse.

Completeness3/5

Missing CRUD operations for workflows (create, update, delete), which are important for managing workflows. The set focuses on consumption and view only, leaving gaps for workflow creation and management.

Maintenance

ActivityStale
ResponsivenessUnresponsive

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches