Semantic Workbench is a versatile tool designed to help prototype intelligent assistants quickly. It supports the creation of new assistants or integration of existing ones within a cohesive interface, providing a user-friendly UI for creating conversations, configuring settings, and exposing various behaviors. The workbench is framework-agnostic and connects to assistants via a RESTful API.
GitHub Codespaces provides a turn-key development environment without needing to configure your local machine:
This creates a cloud-based development environment with all dependencies pre-installed.
If you prefer to install locally:
code semantic-workbench.code-workspace
If not using dev containers, follow these steps:
cd workbench-service
pip install -e .
cd workbench-app
npm install
This will start both the backend service and the frontend app.
Run the provided script:
# For Linux/macOS
./tools/run-workbench-chatbot.sh
# For Windows
.\tools\run-workbench-chatbot.ps1
Open your browser and navigate to:
https://localhost:4000
You may receive a security warning about the self-signed certificate. Click "Advanced" and "Proceed to localhost" to continue.
The workbench requires at least one assistant service to interact with. Choose one of these sample assistants:
In VS Code:
This starts a simple assistant that echoes your messages back.
In VS Code:
You'll need to provide your LLM API keys either in a .env file or through the assistant configuration page.
If you need to reset all service data:
# For Linux/macOS
./tools/reset-service-data.sh
# For Windows
.\tools\reset-service-data.ps1
Alternatively, you can delete the data directory:
rm -rf ~/workbench-service/.data
To completely refresh your development environment:
# From repository root
make clean install
For a faster refresh of just the workbench components:
# From repository root
make clean
# Then from workbench-app directory
cd workbench-app
make install
# Then from workbench-service directory
cd ../workbench-service
make install
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"cursor-rules-mcp": {
"command": "npx",
"args": [
"-y",
"cursor-rules-mcp"
]
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.