Servidor MCP de Plate

• Nombre en el registroto.plate/mcpverificado en el registro MCP

El nombre en el registro está bajo plate.to. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-20
• Herramientas28
• El servidor se llamaPlate
• Versión del servidor1.0.0
• Versión del protocolo2025-06-18

El 2026-10-20 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 414 ms.

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCP78 de 100responde 100 · definiciones 99 · contexto 89 · conexión 100 · rebajada por las señales de aviso de abajo
• Respondióel 100% de los días16 de 16 comprobaciones diarias
• Mediana de la primera respuesta435 ms
• Espacio en el contexto del agente≈ 4442 tokenslas definiciones de todas sus herramientas (28), que el agente lleva en cada turno
• Definiciones de herramientasA · 99 de 100
• Resultados tipados28 de 28 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Sin una descripción con la que el agente pueda elegir: 1 de 28

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• list_workspaces

  List all Plate workspaces the user is a member of.

• list_projects

  List projects in a workspace.

• list_tasks

  List tasks in a project, or look up a specific task by its public number. To resolve a public ID like 'TES-1': pass taskPrefix='TES' and number=1 — the prefix locates the correct workspace automatically (do NOT hardcode workspaceId when…

• list_sections

  List sections (columns) in a project.

• get_task

  Get full details of a task. You can look up by internal taskId OR by public task identifier. To resolve a public ID like 'TES-1' or 'SCD-409', pass it as taskId — the prefix is used to find the correct workspace automatically…

• list_comments

  List a task's comments, oldest first. The taskId is the internal document ID from list_tasks — NOT the public SCD-XXX number.

• list_members

  List workspace members with their userId, name, email, and role. Use userId as assigneeId when creating or updating tasks.

• list_activity

  List task activity history (status changes, assignments, moves, etc.) over a time range. Use it for time-based questions like which tasks were completed last week or what someone did. Filters: from/to (ISO 8601 dates), actorId (who made…

• list_statuses

  List workflow statuses for a workspace. Use the returned IDs as statusId when creating or updating tasks.

• list_labels

  List task labels for a workspace. Use the returned IDs (or names) as `labels` when creating or updating tasks.

• create_task

  Create a new task in a project section. Only call this tool when creating a brand-new task that does not yet exist. To change the name, status, assignee, or description of an existing task, call update_task instead. To mark an existing…

• update_task

  Update one or more fields on an existing task. Use this instead of create_task when the task already exists. The taskId is the internal document ID from list_tasks — NOT the public task number (e.g. SCD-408). To resolve a public number to…

• complete_task

  Mark an existing task as completed or reopen it. Use this instead of create_task when the task already exists and you only need to change its completion state. The taskId is the internal document ID from list_tasks — NOT the public task…

• delete_task

  Permanently delete a task. Comments and attachments are removed automatically. The taskId is the internal document ID from list_tasks — NOT the public task number (e.g. SCD-408).

• create_project

  Create a new project in a workspace. If a project with the same name already exists in the workspace, returns the existing project instead of creating a duplicate — check the `created` field in the response to tell the two cases apart.

• update_project

  Rename a project or update its description.

• create_section

  Create a new section (column) in a project. If a section with the same name already exists in the project, returns the existing section instead of creating a duplicate — check the `created` field in the response to tell the two cases apart.

• update_section

  Rename a section.

• delete_comment

  Delete a comment from a task.

• create_comment

  Add a comment to a task. The taskId is the internal document ID from list_tasks — NOT the public task number (e.g. SCD-408).

• create_tasks

  Create multiple tasks in a project in one action. Use this instead of calling create_task multiple times when the user asks to create several tasks at once. All tasks are created atomically — if validation fails for any item, nothing is…

• update_tasks

  Update multiple existing tasks in one action. Use this instead of calling update_task multiple times when the user asks to change several tasks at once. All updates are applied atomically.

• complete_tasks

  Mark multiple tasks as completed in one action. Use this instead of calling complete_task multiple times. Already-completed tasks are left as-is.

• delete_tasks

  Permanently delete multiple tasks in one action. Use this instead of calling delete_task multiple times. All tasks are validated before any are deleted.

• create_sections

  Create multiple sections in a project in one action. Use this instead of calling create_section multiple times.

• update_sections

  Rename multiple sections in one action. Use this instead of calling update_section multiple times.

• create_comments

  Add multiple comments to tasks in one action. Use this instead of calling create_comment multiple times.

• delete_comments

  Delete multiple comments in one action. Use this instead of calling delete_comment multiple times. All comments are validated before any are deleted.