AI Workbench MCP server

AI Workbench MCP

<!-- mcp-name: io.github.alptugharun/ai-workbench-mcp -->

A tiny, read-only MCP server for reusable AI prompts and assistant blueprints.

AI Workbench MCP exposes a small local catalog over Model Context Protocol stdio. It is intentionally boring in the best way: no network calls, no shell execution, no account access, no file writes, no hidden provider request.

It gives an MCP host three tools:

Why this exists

A lot of AI repos jump straight from "here is a prompt" to "this is an agent." I wanted a smaller boundary that is easy to inspect.

The server keeps the useful parts local and makes its limits obvious:

• read-only tool contracts;
• explicit MCP trust hints;
• bounded input sizes;
• strict top-level schemas;
• no runtime dependencies outside the Python standard library;
• real stdio handshake tests;
• named tests for every public tool.

Quick start

Install the published alpha package:

python -m pip install "alptugharun-ai-workbench-mcp==0.1.0a1"

Then point a stdio-capable MCP host at the server:

Launch command:

alptugharun-ai-workbench-mcp

This repository documents the stdio server itself. For the host we have actually exercised, use the copy/paste Cursor setup and 3-tool verification guide. Other MCP clients can differ, so use their current documentation rather than assuming Cursor's configuration is portable.

Security model

Every public tool declares:

{
  "readOnlyHint": true,
  "destructiveHint": false,
  "idempotentHint": true,
  "openWorldHint": false
}

The implementation does not import HTTP clients, subprocess modules, filesystem-write helpers, browser libraries, or provider SDKs.

That does not mean "trust any MCP server." It means this repository keeps its own boundary narrow and testable.

Verify it yourself

python -m unittest discover -s tests -v
python examples/smoke_client.py

CI runs the package and protocol tests on Linux and Windows.

Package / registry status

PyPI: alptugharun-ai-workbench-mcp==0.1.0a1 is published through GitHub OIDC Trusted Publishing. The release workflow also signs the wheel with keyless Sigstore.

Shortened. The full README is on GitHub.