smaregi-mcp
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 |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| smaregi_configureA | スマレジAPIの接続設定を保存します |
| smaregi_auth_statusA | スマレジAPIの認証状態を確認します |
| smaregi_server_infoA | MCPサーバーのバージョンと接続先情報を表示します |
| smaregi_api_getC | スマレジAPIにGETリクエストを送信します |
| smaregi_api_postC | スマレジAPIにPOSTリクエストを送信します |
| smaregi_api_putC | スマレジAPIにPUTリクエストを送信します |
| smaregi_api_deleteC | スマレジAPIにDELETEリクエストを送信します |
| smaregi_api_patchC | スマレジAPIにPATCHリクエストを送信します |
| smaregi_api_list_pathsA | スマレジAPIの既知エンドポイント一覧を表示します |
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 9 tools
Each tool has a distinct purpose: HTTP methods (GET, POST, PUT, PATCH, DELETE) are clearly separated, and auxiliary tools (list_paths, auth_status, configure, server_info) handle specific non-API operations with no overlap.
All tools use a consistent snake_case pattern with the 'smaregi_' prefix. HTTP method tools follow 'smaregi_api_<method>' and other tools use descriptive names like 'smaregi_auth_status', maintaining a predictable structure.
With 9 tools, the server covers essential API operations (all common HTTP methods) and administrative functions (auth, configuration, info). This count is well-scoped for a general-purpose API wrapper without being bloated or sparse.
The tool set fully covers the lifecycle of interacting with a REST API: all CRUD methods (GET, POST, PUT, PATCH, DELETE) are present, plus endpoint discovery (list_paths), authentication status, configuration, and server info. No obvious gaps for the stated purpose.