MCP Configuration Editor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_BACKUP_DIR | No | バックアップディレクトリのパス (Path to the backup directory). デフォルトは設定ファイルと同じディレクトリの backups/ (Default is backups/ in the same directory as the config file) | |
| MCP_CONFIG_PATH | No | MCP設定ファイルのパス (Path to the MCP configuration file) | ~/.aws/amazonq/mcp.json |
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 |
|---|---|
| list_serversA | 設定されている全てのMCPサーバーをリスト表示する。 |
| get_serverB | 特定のMCPサーバーの設定を取得する。 |
| add_serverA | 新しいMCPサーバー設定を追加する。 |
| update_serverA | 既存のMCPサーバー設定を更新する。 |
| remove_serverC | MCPサーバー設定を削除する。 |
| validate_configA | 現在のMCP設定ファイルを検証する。 |
| export_configA | MCP設定全体をJSON形式でエクスポートする。 |
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
Every tool has a clearly distinct purpose with no ambiguity. The tools cover specific operations like adding, listing, getting, updating, removing servers, exporting config, and validating config - each targeting a unique action on the MCP configuration domain.
All tools follow a consistent verb_noun pattern with snake_case naming throughout (e.g., add_server, list_servers, validate_config). The naming convention is predictable and uniform across all seven tools.
Seven tools is well-scoped for an MCP configuration editor server. This provides complete CRUD operations for server configurations plus utility functions for export and validation, with each tool earning its place in the set.
The tool surface provides complete coverage for the MCP configuration domain with full CRUD lifecycle management (add, get, update, remove, list) plus essential utilities for export and validation. There are no obvious gaps or dead ends for agents working with server configurations.