boutique-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BOUTIQUE_MCP_AUDIT | No | Set to '1' to opt-in local audit log | |
| BOUTIQUE_MCP_OFFLINE | No | Set to '1' to never touch the network | |
| BOUTIQUE_MCP_CACHE_DIR | No | Disk cache location | ~/.matematic/cache/boutique-mcp |
| BOUTIQUE_MCP_CATALOG_URL | No | Catalog source URL | https://matematicsolutions.com/catalog.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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| boutique_searchA | Search the MateMatic Boutique catalog for connectors and skills. |
| boutique_getA | Full catalog card for one entry: names, descriptions and card URLs in every available language, install command, version, license, source URL. |
| boutique_whats_newA | What was added to or updated in the Boutique catalog since a date. |
| boutique_request_coverageA | Draft a coverage-request issue for a gap in the Boutique catalog. DRAFT ONLY - this tool performs no network call and submits nothing. A human reviews the draft and submits it at the returned URL. |
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 4 tools
Each tool targets a distinct operation: searching, retrieving full details, checking updates, and requesting coverage. No overlap in purpose or expected usage.
All tools share the 'boutique_' prefix and use clear action-oriented names, though 'whats_new' is a noun phrase rather than a verb_noun style like the others. The consistency is strong but not perfect.
With 4 tools, the server is tightly scoped to the catalog domain. Each tool serves a necessary function without redundancy or bloat.
The toolset covers discovery (search, get, whats_new) and contribution (request_coverage), forming a complete lifecycle for interacting with the boutique catalog. No obvious gaps such as missing listing or submission capabilities.