Skip to main content
Glama
PhillipRt

Think Tool MCP Server

by PhillipRt

Servidor MCP de Think Tool

insignia de herrería

Implementación oficial de la herramienta "pensar" de Anthropic como servidor MCP : mejora drásticamente las capacidades de razonamiento de Claude con el pensamiento estructurado.

¿Qué es la herramienta Think?

Este servidor MCP implementa la misma herramienta de pensamiento que Anthropic presentó en su blog de ingeniería . Esta herramienta proporciona a Claude un espacio dedicado al razonamiento estructurado durante tareas complejas de resolución de problemas, lo que permite respuestas más reflexivas, precisas y fiables.

Related MCP server: MCP Think Tool Server

Beneficios de rendimiento comprobados

La investigación de Anthropic demuestra mejoras notables al utilizar la herramienta "pensar":

  • 54% de mejora en tareas complejas de atención al cliente

  • Adherencia significativamente mejor a políticas y directrices detalladas

  • Mayor consistencia en múltiples ensayos de la misma tarea

  • Rendimiento mejorado en los puntos de referencia de ingeniería de software

  • Mínima sobrecarga de implementación en comparación con otras técnicas de mejora

La herramienta "pensar" sobresale donde otros enfoques fallan:

  • Mejor que el pensamiento extendido para casos que requieren cadenas de herramientas complejas

  • Más eficaz que la incitación de referencia para escenarios con gran carga política

  • Especialmente potente cuando se combina con indicaciones optimizadas.

Instalación rápida

Para Claude Desktop

npx -y @smithery/cli@latest install @PhillipRt/think-mcp-server --client claude --config "{}"

Para el cursor

npx -y @smithery/cli@latest install @PhillipRt/think-mcp-server --client cursor --config "{}"

Cómo funciona

La herramienta "pensar" implementa exactamente el mismo mecanismo descrito en el blog de ingeniería de Anthropic. A diferencia del pensamiento extendido (que ocurre antes de que Claude empiece a responder), la herramienta "pensar" le permite a Claude hacer una pausa y reflexionar durante la generación de su respuesta.

Mecanismo clave: La herramienta no realiza ninguna acción externa ni recupera información nueva: simplemente le proporciona a Claude un bloc de notas dedicado para trabajar en el razonamiento paso a paso, lo que mejora drásticamente el desempeño en tareas complejas.

Cuando Claude usa la herramienta "pensar":

  1. Se detiene para organizar los pensamientos antes de continuar una compleja cadena de razonamiento.

  2. Crea un enfoque estructurado para problemas de varios pasos.

  3. Verifica el cumplimiento de las políticas de forma más exhaustiva y consistente.

  4. Analiza cuidadosamente los resultados de la herramienta antes de decidir los próximos pasos.

  5. Mantiene una mejor conciencia del contexto a lo largo de interacciones largas.

Cuándo utilizar la herramienta Think

La herramienta "pensar" es especialmente valiosa cuando:

  1. Trabajar con otras herramientas MCP : excelente para analizar resultados de bases de datos, sistemas de archivos o API

  2. Seguimiento de políticas complejas : perfecto para situaciones de servicio al cliente, legales o de cumplimiento.

  3. Toma de decisiones secuenciales : ideal para flujos de trabajo donde los pasos posteriores dependen de los anteriores.

  4. Procesamiento de resultados de búsqueda web : ayuda a Claude a sintetizar información de múltiples fuentes

  5. Resolver desafíos de codificación : mejora las tasas de éxito en tareas de ingeniería de software

Aviso del sistema para obtener resultados óptimos

Las investigaciones de Anthropic demuestran que combinar la herramienta "pensar" con indicaciones optimizadas ofrece las mayores mejoras de rendimiento . Para obtener los mejores resultados, añada la siguiente indicación optimizada del sistema a su interacción con Claude:

Para Claude Desktop (Instrucciones personalizadas)

  1. Vaya a Configuración > Instrucciones personalizadas

  2. Agregue el siguiente mensaje del sistema:

You have access to a "think" tool that provides a dedicated space for structured reasoning. Using this tool significantly improves your performance on complex tasks.

## When to use the think tool

Before taking any action or responding to the user after receiving tool results, use the think tool as a scratchpad to:
- List the specific rules that apply to the current request
- Check if all required information is collected
- Verify that the planned action complies with all policies
- Iterate over tool results for correctness
- Analyze complex information from web searches or other tools
- Plan multi-step approaches before executing them

## How to use the think tool effectively

When using the think tool:
1. Break down complex problems into clearly defined steps
2. Identify key facts, constraints, and requirements
3. Check for gaps in information and plan how to fill them
4. Evaluate multiple approaches before choosing one
5. Verify your reasoning for logical errors or biases

Remember that using the think tool has been shown to improve your performance by up to 54% on complex tasks, especially when working with multiple tools or following detailed policies.

Para el cursor (reglas globales)

Para agregar la herramienta Pensar como regla de cursor:

  1. Abrir configuración del cursor

  2. Vaya a General > Reglas para IA

  3. Añade una nueva regla con el siguiente contenido:

After any context change (viewing new files, running commands, or receiving tool outputs), use the "mcp_think" tool to organize your reasoning before responding.

Specifically, always use the think tool when:
- After examining file contents or project structure
- After running terminal commands or analyzing their outputs
- After receiving search results or API responses
- Before making code suggestions or explaining complex concepts
- When transitioning between different parts of a task

When using the think tool:
- List the specific rules or constraints that apply to the current task
- Check if all required information is collected
- Verify that your planned approach is correct
- Break down complex problems into clearly defined steps
- Analyze outputs from other tools thoroughly
- Plan multi-step approaches before executing them

The think tool has been proven to improve performance by up to 54% on complex tasks, especially when working with multiple tools or following detailed policies.

Instalación manual

Si prefiere ejecutar el servidor localmente:

  1. Clonar el repositorio :

    git clone https://github.com/PhillipRt/think-mcp-server.git
    cd think-mcp-server
  2. Instalar dependencias :

    npm install
  3. Construir y ejecutar :

    npm run build
    npm start
  4. Configurar Claude Desktop manualmente :

    • Busque o cree el archivo de configuración:

      • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

      • Ventanas: %APPDATA%\Claude\claude_desktop_config.json

    • Añade la configuración de tu servidor:

    {
      "mcpServers": {
        "think-tool": {
          "command": "node",
          "args": ["path/to/think-mcp-server/dist/server.js"]
        }
      }
    }

Licencia

Licencia MIT

Available Tools

1 tool
thinkA

Use the tool to think about something. It will not obtain new information or change the database, but just append the thought to the log. Use it when complex reasoning or some cache memory is needed.

ParametersJSON Schema
NameRequiredDescriptionDefault
thoughtYesA thought to think about.

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key traits: 'It will not obtain new information or change the database' clarifies it's a read-only, non-destructive operation, and 'just append the thought to the log' explains the action. This covers safety and basic behavior, though it could add details like log format or persistence.

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

Conciseness4/5

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

The description is appropriately sized with two sentences that efficiently convey purpose and usage. It is front-loaded with the core action and avoids unnecessary details. Every sentence adds value, though minor improvements in clarity could enhance conciseness further.

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 (one parameter, no annotations, no output schema), the description is reasonably complete. It covers purpose, usage, and behavioral traits adequately. However, it could be more specific about what 'think' involves or the log's nature, which would improve completeness for an agent's understanding.

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?

The input schema has 100% description coverage, with the 'thought' parameter documented as 'A thought to think about.' The description adds no additional parameter semantics beyond this, such as format or constraints. Given the high schema coverage, a baseline score of 3 is appropriate, as the schema already provides adequate parameter information.

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 the tool's purpose: 'Use the tool to think about something' and 'append the thought to the log.' It specifies the verb ('think') and resource ('thought log'), though it doesn't distinguish from siblings since none exist. The purpose is clear but could be more specific about what 'think' entails operationally.

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 provides explicit guidance on when to use the tool: 'Use it when complex reasoning or some cache memory is needed.' This gives clear context for its application. However, it lacks exclusions or alternatives, which is acceptable since no sibling tools are present to differentiate from.

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. 1 tool updatev1.0.0
    • First observedthink

TDQS

A3.9/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap with other tools. The tool 'think' has a clearly distinct purpose of internal reasoning and logging, with no competing tools to confuse it with.

Naming Consistency5/5

The single tool name 'think' follows a simple verb pattern, and with only one tool, there is no inconsistency to evaluate. The naming is straightforward and appropriate for its function.

Tool Count2/5

A single tool is generally too few for most server purposes, as it limits functionality and can feel thin. For a 'Think Tool MCP Server', one tool might suffice for basic reasoning, but it lacks breadth and could be considered under-scoped for typical agent workflows.

Completeness3/5

The tool 'think' covers its specific purpose of reasoning and logging, but the server's domain is unclear from the single tool. There are no obvious gaps for the tool itself, but the overall surface is minimal, making it hard to assess completeness for any broader domain.

Maintenance

ActivityInactive
ResponsivenessNo issues

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that implements the 'think' tool, providing Claude with a dedicated space for structured thinking during complex problem-solving tasks to improve reasoning capabilities.
    130
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    Implements Anthropic's 'think' tool for Claude, providing a dedicated space for structured reasoning during complex problem-solving tasks that improves performance in reasoning chains and policy adherence.
    4
    156 npm
    38
    MIT
  • F
    license
    A
    quality
    D
    maintenance
    An MCP server implementation of Anthropic's Think Tool prompt engineering technique that enables Claude to break down complex problems and enhance its reasoning capabilities by providing a simple tool that echoes back thoughts.
    1
    2
    -