PATH. Each serves a distinct purpose. This page explains what they are, how to verify they are available, and which one to reach for in each situation.
Installed Commands
| Command | Entry point | What it does |
|---|---|---|
semantica | semantica.cli:main | General-purpose CLI for pipeline runs, extraction, and graph operations |
semantica-server | semantica.server:main | FastAPI/uvicorn REST API server bound to 0.0.0.0:8000 |
semantica-worker | semantica.worker:main | Background worker process entry point for Semantica deployments |
semantica-explorer | semantica.explorer:main | Interactive browser dashboard for knowledge graph exploration |
semantica-mcp | semantica.mcp_server:main | MCP server (stdio) for Claude Desktop, Cursor, Windsurf, and other MCP clients |
semantica-explorer requires pip install semantica[explorer]. Running it without that extra will immediately print an error and exit. See Explorer Setup for the full walkthrough.Verify the Installation
Confirm each command is reachable and prints its usage:When to Use Each Command
semantica
The general-purpose CLI. Use it for one-off pipeline runs, entity extraction, and graph operations from a shell script or CI job.
semantica-server
Starts the REST API server. Binds to
0.0.0.0:8000. Use this when another service or application needs programmatic access to Semantica over HTTP.semantica-worker
Background task processor. Run alongside
semantica-server when you need async pipeline execution outside the request cycle. Start the server first, then start one or more workers pointing at the same backend.semantica-explorer
Launches the browser dashboard. Requires
pip install semantica[explorer]. Use this to explore a saved knowledge graph interactively. See Explorer Setup.semantica-mcp
Runs the MCP server over stdio. Configure it in your MCP client’s settings file to expose all 12 tools and 3 resources to Claude Desktop, Cursor, Windsurf, or any MCP-aware client. See MCP Server.
Usage Examples
- REST server
- Worker
- MCP client config
- Explorer
- Python module form
http://localhost:8000/docs.Environment Variables
semantica-mcp reads two environment variables:
| Variable | Default | Description |
|---|---|---|
SEMANTICA_KG_PATH | (none) | Path to a saved graph file to load on startup |
SEMANTICA_LOG_LEVEL | WARNING | Log verbosity: DEBUG, INFO, WARNING |
semantica-server reads one:
| Variable | Default | Description |
|---|---|---|
SEMANTICA_CORS_ORIGINS | http://localhost:5173,http://127.0.0.1:5173 | Comma-separated list of allowed CORS origins |
Troubleshooting
command not found
command not found
The executables land in Find where pip placed the scripts:
bin/ (Linux/Mac) or Scripts/ (Windows) of the active Python environment. If the command is not found, that directory is likely not on PATH.Activate your virtual environment first:Command found but crashes on import
Command found but crashes on import
semantica-explorer: uvicorn is required
semantica-explorer: uvicorn is required
The Explorer extras are not included in the base install:
semantica-mcp silent failure inside a MCP client
semantica-mcp silent failure inside a MCP client
The MCP server communicates over stdio. Test it directly from the shell first:A response of
{"jsonrpc":"2.0","id":1,"result":{}} confirms the server is working. If you see nothing, check that the command is on PATH and the base package is installed.Windows: DLL errors on startup
Windows: DLL errors on startup
Install the Microsoft Visual C++ Redistributable. This is a Windows system dependency required by PyTorch and related packages, not a Semantica bug.
Next Steps
Explorer Setup
Build a graph, save it, and launch the browser dashboard.
MCP Server
All 12 tools and 3 resources exposed over the MCP protocol.
Installation
Virtual environments, optional extras, and platform-specific notes.
Quickstart
End-to-end pipeline walkthrough with working code.
