fvi-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FVI_TOKEN | Yes | Collection-scoped MCP token | |
| FVI_API_URL | No | API base URL (include /api) | http://localhost:5001/api |
| FVI_COLLECTION_ID | Yes | Collection id |
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 |
|---|---|
| get_design_collection_contextB | Return metadata-first context for the configured FreeVectorIcons design collection. |
| list_design_collection_assetsB | List metadata for assets in the configured design collection. |
| search_design_collection_assetsB | Search design collection asset metadata by name, type, category, style, or tag. |
| get_design_assetB | Get metadata for one asset by asset id or collection item id. |
| get_design_asset_download_urlB | Get a short-lived download URL for an uploaded design asset. |
| get_design_asset_contentA | Get inline text content for safe design assets such as catalog SVGs, uploaded SVGs, and Markdown files. |
| create_design_asset_uploadB | Create a signed upload target and collection asset record for parking a DRL/FVI design asset. |
| park_design_assetC | Upload inline text or base64 content directly into the configured FVI collection for DRL handoff. |
| create_design_asset_versionB | Upload inline text or base64 content as a new version of an existing uploaded design asset. |
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 targets a distinct operation on design assets, such as creating, uploading versions, retrieving metadata or content, listing, searching, and collection context. No two tools overlap in purpose.
All tool names follow the verb_noun pattern with underscores, using consistent verbs (create, get, list, park, search) and nouns (design_asset, design_collection_assets, etc.). The pattern is uniformly applied.
With 9 tools covering creation, retrieval, listing, searching, and context, the set is well-scoped for managing a design asset collection without being too sparse or bloated.
The tool set covers most common operations but lacks update and delete functionality for assets, which could create dead ends for agents needing to modify or remove assets.