About Owl MCP
Owl MCP is an MCP server published by ai4curation in the AI category: mCP server for modifying OWL files written in Rust. It has been installed 0 times through Conduid.
The repository has 13 stars and 6 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.
Install
npx owl-mcpThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about Owl MCP
Powered by Claude · Grounded in docs
Security checks
- ·README presentNot checked yet.
- ·License declaredNot checked yet.
- ·Tests presentNot checked yet.
- ·Dependencies pinnedNot checked yet.
- ·No dynamic code executionNot checked yet.
- !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.
README
OWL-MCP
OWL-MCP is a Model-Context-Protocol (MCP) server for working with Web Ontology Language (OWL) ontologies.
Quick Start
This walks you through using owl-mcp with Goose, but any MCP-enabled AI host will work.
Install Goose
You can use either the Desktop or CLI version of Goose from here:
Follow the instructions for setting up an LLM provider (Anthropic recommended)
Install OWL-MCP extension
You can either install directly from this link:
- Install OWL-MCP
Or to do this manually, in the Extension section of Goose, add a new entry for owlmcp:
uvx owl-mcp
This video shows how to do this manually:
Try it out
You can ask to create an ontology, and add axioms to an ontology:
How this works
The MCP server provides function calls for finding, adding, or removing OWL axioms, using OWL functional syntax. Each function call is accompanied by the file path of the OWL file on your disk. Any format supported by py-horned-owl is accepted (we following OBO guidelines and recommend functional syntax for source).
The server takes care of keeping an instance of the ontology in memory and syncing it with disk. Any CRUD operation simultaneously updates the in-memory model and syncs this with disk. If you have Protege running, Protege will also sync with local disk, and show updates.
The server is well adapted for working with OBO-style ontologies - when OWL strings are sent back to the client, labels for opaque IDs are included after #s comments, as is common for obo-format.
Key Features
- MCP Server Integration: Connect AI assistants directly to OWL ontologies using the standardized Model-Context-Protocol
- Thread-safe operations: All ontology operations are thread-safe, making it suitable for multi-user environments
- File synchronization: Changes to the ontology file on disk are automatically detected and synchronized
- Event-based notifications: Register observers to be notified of changes to the ontology
- Simple string-based API: Work with OWL axioms as strings in functional syntax without dealing with complex object models
- Configuration system: Store and manage settings for frequently-used ontologies
- Label support: Access human-readable labels for entities with configurable annotation properties
README mirrored from the source repository 17 days ago. The original is authoritative.

