mcp-jp-fts
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| index_directoryA | Recursively indexes all text files in the given root_path. WARNING: This will remove all existing index entries that start with this root_path before re-indexing. |
| delete_indexB | Delete all indexed documents under the specified root path. |
| search_documentsA | Search for documents matching the Japanese query string. Optionally filter by a root path and/or file extensions. Args: query: Japanese search query limit: Max results to return path_filter: Only return results under this path extensions: List of file extensions to include (e.g., [".py", ".md"]) |
| list_indexed_filesA | List paths of all indexed files with pagination. |
| update_fileA | Update the index for a single file. If the file exists, it is re-indexed. If the file does not exist, it is removed from the index. |
| watch_directoryC | Start watching a directory for changes and automatically update the index. |
| get_index_statsA | Get statistics about the current index and watched directories. Returns a JSON string containing:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a distinct purpose: delete, stats, index directory, list files, search, update single file, watch directory. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case, e.g., delete_index, get_index_stats, search_documents.
7 tools cover the core operations for a file indexing server without being excessive or insufficient.
The tool set includes full lifecycle management: initial indexing, incremental updates, watching, listing, searching, stats, and bulk deletion. No obvious gaps.