Skip to main content
Glama
jacwalste

VendorOps MCP

by jacwalste
README.md
# VendorOps MCP

VendorOps is a Model Context Protocol (MCP) server for a synthetic internal
vendor-management workflow. It gives AI applications structured access to
vendor records, contracts, spending, renewals, and security reviews.

The project is intentionally built in small, reviewable slices. Phase 1 uses
Python, the official MCP Python SDK, SQLite, Pydantic, and pytest to expose
read-only vendor data over a local stdio connection.

All vendor and contract data in this repository is synthetic.

## Development

Install the locked dependencies:

```bash
uv sync
```

Run the test suite:

```bash
uv run pytest
```

Run the local stdio server:

```bash
uv run vendorops-mcp
```

The server waits for an MCP host to send protocol messages over stdin. It does
not open a network port or print a user interface.

By default, VendorOps creates `data/vendorops.db` and seeds it with 30 synthetic
vendors. Set `VENDOROPS_DB_PATH` to use a different SQLite file.

## Current MCP Capabilities

### Tools

- `search_vendors`: Search vendor records by name, category, or owner, with
  optional category and status filters.

TDQS

A3.9/5.0

Scored across 1 tool

Disambiguation5/5

With only a single tool, there are no overlapping purposes or ambiguity. The tool clearly defines its own scope.

Naming Consistency5/5

The single tool name follows a clear verb_noun pattern (search_vendors), which is consistent and predictable.

Tool Count2/5

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.

Completeness1/5

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.

Maintenance

ActivitySlowing
ResponsivenessNo issues