FastMCP Development Assistant
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch-fastmcp-readmeB | FastMCPのGitHubリポジトリからREADMEファイルを取得します |
| fetch-fastmcp-versionsB | FastMCPパッケージのnpm上の全バージョンと最新バージョン情報を取得します |
| fetch-mcp-architecture-docB | MCP公式サイトからアーキテクチャドキュメントを取得します |
| fetch-npm-typesA | 指定されたNPMパッケージのTypeScript型定義を取得します。メインパッケージの型定義または@types/パッケージから取得します。 |
| analyze-npm-typesB | 指定されたNPMパッケージのTypeScript型定義の包括的な分析を実行します。パッケージの型定義状態、おすすめのアプローチ、代替手段を提示します。 |
| get-cache-statsB | NPM型定義キャッシュの統計情報と設定を表示します。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| git-commit | Generate a Git commit message |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Application Logs |
TDQS
Scored across 6 tools
Most tools have distinct purposes, but 'analyze-npm-types' and 'fetch-npm-types' could cause confusion as both involve NPM package TypeScript definitions. The former analyzes and recommends, while the latter simply fetches, but the overlap in naming and domain might lead to misselection without careful reading of descriptions.
All tool names follow a consistent verb-noun pattern with kebab-case (e.g., 'analyze-npm-types', 'fetch-fastmcp-readme'). The verbs are clear and descriptive, and there are no deviations in style or convention throughout the set.
With 6 tools, the count is reasonable for a development assistant focused on FastMCP and NPM types. It covers key areas like fetching documentation, analyzing types, and cache stats, though it might be slightly lean for broader development tasks, but well-scoped for its stated purpose.
The tool set covers fetching and analyzing NPM types and FastMCP resources, but there are notable gaps. For a 'Development Assistant', it lacks tools for actions like installing packages, running tests, or managing projects, which could limit agent workflows. However, within its narrow focus on types and documentation, it provides basic coverage.