Skip to main content
Glama
enesjakozh
PhillipRt

Think Tool MCP Server

by PhillipRt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

シンクツールMCPサーバー

鍛冶屋のバッジ

MCP サーバーとしての Anthropic の「think」ツールの公式実装- 構造化された思考により Claude の推論能力が劇的に向上します。

シンクツールとは何ですか?

このMCPサーバーは、Anthropicがエンジニアリングブログ記事で紹介した「思考」ツールをそのまま実装しています。この思考ツールは、複雑な問題解決タスクにおいて、クロードに構造化された推論のための専用スペースを提供し、より思慮深く、正確で、信頼性の高い回答を可能にします。

Related MCP server: MCP Think Tool Server

実証済みのパフォーマンスメリット

Anthropic の調査では、「think」ツールを使用すると顕著な改善が見られることが示されています。

  • 複雑な顧客サービス業務が54%改善

  • 詳細なポリシーとガイドラインの遵守が大幅に向上

  • 同じタスクの複数の試行間の一貫性の向上

  • ソフトウェアエンジニアリングベンチマークにおけるパフォーマンスの向上

  • 他の拡張技術と比較して実装オーバーヘッドが最小限

「think」ツールは、他のアプローチが不十分な場合に優れています。

  • 複雑なツールチェーンを必要とするケースでは**、拡張思考よりも優れています**

  • 政策重視のシナリオではベースラインプロンプトよりも効果的

  • 最適化されたプロンプトと組み合わせると特に強力になります

クイックインストール

クロードデスクトップ向け

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

カーソル用

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

仕組み

「考える」ツールは、Anthropicのエンジニアリングブログで説明されているメカニズムをそのまま実装しています。クロードが応答を開始する前に行われる長時間の思考とは異なり、「考える」ツールでは、応答生成中にクロードが一時停止してじっくり考えることを可能にします。

**主なメカニズム:**このツールは外部アクションを実行したり、新しい情報を取得したりするのではなく、Claude に推論を段階的に実行するための専用のスクラッチパッドを提供するだけであり、複雑なタスクのパフォーマンスが大幅に向上します。

クロードが「考える」ツールを使用するとき:

  1. 複雑な推論の連鎖を続ける前に**、思考を整理するために一時停止する**

  2. 多段階の問題に対する構造化されたアプローチを作成する

  3. ポリシーの遵守をより徹底的かつ一貫して検証します

  4. 次のステップを決定する前にツールの出力を注意深く分析します

  5. 長時間のインタラクションでも優れたコンテキスト認識を維持します

思考ツールを使うべき時

「考える」ツールは、次のような場合に特に役立ちます。

  1. 他の MCP ツールとの連携- データベース、ファイルシステム、API からの出力を分析するのに最適です

  2. 複雑なポリシーに従う- 顧客サービス、法務、コンプライアンスのシナリオに最適

  3. 順次決定を行う- 後のステップが前のステップに依存するワークフローに最適

  4. ウェブ検索結果の処理- クロードが複数のソースから情報を統合するのに役立ちます

  5. コーディングの課題を解決- ソフトウェアエンジニアリングタスクの成功率を向上

最適な結果を得るためのシステムプロンプト

Anthropicの調査によると**、「考える」ツールと最適化されたプロンプトを組み合わせることで、パフォーマンスが最も向上することが示されています**。最良の結果を得るには、Claudeインタラクションに以下の最適化されたシステムプロンプトを追加してください。

Claude Desktop 向け (カスタム手順)

  1. 「設定」>「カスタム指示」に移動します

  2. 次のシステム プロンプトを追加します。

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.

カーソル（グローバルルール）

カーソル ルールとしてシンク ツールを追加するには:

  1. カーソル設定を開く

  2. 一般 > AIのルールに移動します

  3. 次の内容の新しいルールを追加します。

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.

手動インストール

サーバーをローカルで実行したい場合:

  1. リポジトリをクローンします:

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

  2. 依存関係をインストールします:

    npm install

  3. ビルドと実行:

    npm run build
npm start

  4. Claude Desktop を手動で構成します。

    • 構成ファイルを見つけるか作成します。

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

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

    • サーバー構成を追加します:

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

ライセンス

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
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 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

Resources

Related MCP Connectors

Related MCP Servers

  • MCP Think Tool

    DannyMac180
    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

  • MCP Think Tool Server

    cgize
    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

  • MCP Think Tool

    piotrpalek
    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
    -

Appeared in Searches