VendorOps MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VENDOROPS_DB_PATH | No | Path to the SQLite database file. By default, VendorOps creates data/vendorops.db and seeds it with 30 synthetic vendors. | data/vendorops.db |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_vendorsA | Search vendor records by a name, category, or owner substring. Optionally filter by exact category or vendor status. |
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 1 tool
With only a single tool, there are no overlapping purposes or ambiguity. The tool clearly defines its own scope.
The single tool name follows a clear verb_noun pattern (search_vendors), which is consistent and predictable.
The server name VendorOps implies broader vendor management, but only one search tool is provided. This is too few for the apparent scope, leaving the toolset feeling thin.
The toolset covers only searching vendors, with no create, update, delete, or other lifecycle operations. This is a severe gap for a vendor operations server.