Skip to content

protege-mcp v0.3.0

Choose a tag to compare

View all tags
@hakjuoh hakjuoh released this 29 Jun 16:31
v0.3.0
70a2f82

In-Protégé chat assistant (Architecture Approach B). A new Ontology Assistant tab and view let you converse with an assistant that reads and edits your live ontology — without leaving Protégé.

Rather than calling a model API directly, the chat drives a coding-agent CLI you already have installed — Claude Code (claude) or OpenAI Codex (codex) — pointed back at this plugin's own MCP server. So every edit flows through the same tool layer an external MCP client uses: it appears in the GUI, joins the undo stack, and obeys the read-only / confirm-each-write gates. No API key is stored by Protégé — each CLI uses your existing login.

Highlights

  • Ontology Assistant tab + view — a streaming chat transcript with Send/Stop, a live token/cost readout, and a server/egress status line. Try a read ("What classes are in this ontology?") or an edit ("Create a class FooBar under Thing with label 'Foo Bar'."); Edit ▸ Undo reverts any edit.
  • Pick your provider — Use Claude / Use Codex (only installed CLIs are shown); the model picker is populated from the active provider and is editable for any model your account supports (blank = the CLI's own default).
  • No API key, no new outbound socket from the plugin — each CLI uses your existing login (Claude keychain/subscription; codex login). A one-time banner discloses that your prompts and the ontology content the assistant reads are sent to your model provider via the CLI.
  • Inherited safety — edits go through the MCP server's gates, so read-only mode and the confirm-each-write modal apply unchanged and the chat cannot escalate past them; a Confirm each edit checkbox toggles confirmation live.
  • New Settings ▸ Ontology Assistant — optional per-provider CLI path overrides (for when a Dock/Finder-launched Protégé lacks your shell PATH) and an egress-consent reset.

Notes

  • The 47 MCP tools are unchanged; the chat reuses them over loopback HTTP. The MCP server starts automatically on the first chat message.
  • Requires a Java 17+ JVM (unchanged), plus at least one installed and logged-in CLI (claude or codex) to use the chat assistant.

Install: download protege-mcp-0.3.0.jar below, or use Protégé ▸ File ▸ Check for plugins.

Assets 3
Loading