MCP.so
ログイン

MCP Server for Find Reference

@Menabar

MCP Server for Find Reference について

概要はまだありません

基本情報

カテゴリ

その他

ランタイム

node

トランスポート

stdio

公開者

Menabar

設定

標準の設定はありません

このサーバーの README には解析可能な MCP 設定ブロックが含まれていません。インストール手順はリポジトリをご確認ください。

リポジトリ

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is MCP Server for Find Reference?

MCP Server for Find Reference provides two tools—get-text-matches and get-parse-tree—that recursively search files in a given directory. get-text-matches returns exact text matches with file, line, and column. get-parse-tree returns parse tree metadata for a string. It is designed for developers analyzing source code.

How to use MCP Server for Find Reference?

Add the server to AMP using http://localhost:3001 and name it get-text-matches. Run with node server.js. Then prompt the MCP server with commands like “use the get-text-match tool to find temp_x, specify the full path.” You may need to explicitly tell it which tool to use.

Key features of MCP Server for Find Reference

  • Returns exact text matches with file, line, and column.
  • Returns parse tree metadata for a given string.
  • Both tools run recursively over all files in a directory.
  • Can be instructed to use or avoid a specific tool.

Use cases of MCP Server for Find Reference

  • Finding all occurrences of a variable name in a codebase.
  • Analyzing variable types and scopes in JavaScript files.
  • Understanding parse tree structure of code snippets.

FAQ from MCP Server for Find Reference

Why does the server need to be told to use a specific tool?

The client may try to find information itself because it has direct file access. Therefore, the server must be explicitly instructed to use get-text-match or get-parse-tree.

What if the server selects the wrong tool?

You can tell it to specifically not use a tool, for example: “use the parse tree tool, not get text, to find temp_x.”

Is it necessary to specify the full path?

Not always, but occasionally the server uses . as the directory instead of the full path. Specifying the full path is recommended.

Does the server have access to any directory?

The server trusts the client to tell it what local directory to check. You can hard code a path if desired.

Does the server support case‑insensitive matching?

Not yet; case‑insensitive matches are planned for a future update.

コメント

「その他」の他のコンテンツ