AI Clients
This page covers the AI clients Hawknet supports today and how to connect an MCP-compatible client manually if Hawknet does not auto-configure it yet.
Supported AI Clients
Hawknet auto-configures supported clients during install. After installing, restart your AI client so it picks up the new MCP server entry.
| Client | Setup | Config Location |
|---|---|---|
| Claude Code | Automatic | ~/.claude.json |
| Claude Desktop | Automatic | App-managed config |
| Cursor | Automatic | ~/.cursor/mcp.json |
| Codex CLI | Automatic | ~/.codex/config.toml |
| OpenCode | Automatic | ~/.config/opencode/opencode.json |
| Google Antigravity | Automatic | App-managed config |
Manual Setup Examples
These are manual setup examples for the supported clients people ask about most. They use Hawknet’s default macOS/Linux install path. On Windows, swap in your Hawknet executable path before saving.
Fastest fallback: add Hawknet with Claude Code's built-in MCP command.
claude mcp add --scope user hawknet -- ~/.hawknet/bin/hawknet This writes the server entry to your user-level Claude Code config.
Paste this into Claude Desktop if you need to wire Hawknet manually.
{
"mcpServers": {
"hawknet": {
"command": "/absolute/path/to/hawknet",
"args": [],
"env": {}
}
}
} Replace /absolute/path/to/hawknet with your Hawknet binary path, usually ~/.hawknet/bin/hawknet.
Paste this into Cursor's MCP config file.
{
"mcpServers": {
"hawknet": {
"command": "${userHome}/.hawknet/bin/hawknet",
"args": []
}
}
} If your file already contains other MCP servers, merge the hawknet entry into the existing mcpServers object.
Fastest fallback: let Codex add the local MCP server for you.
codex mcp add hawknet -- ~/.hawknet/bin/hawknet Codex writes the resulting server entry into ~/.codex/config.toml.
Paste this into your global OpenCode config under the mcp section.
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"hawknet": {
"type": "local",
"command": ["/absolute/path/to/hawknet"],
"enabled": true
}
}
} Replace /absolute/path/to/hawknet with your Hawknet binary path before saving.
Add an Unsupported MCP Client
If your AI client supports MCP but Hawknet does not configure it automatically yet, add Hawknet as a stdio MCP server manually.
- Install Hawknet first.
- Open your AI client’s MCP settings.
- Add a server named
hawknet. - Point it at the Hawknet executable.
- Restart your AI client after saving the config.
Use these values:
| Setting | Value |
|---|---|
| Server name | hawknet |
| Command | ~/.hawknet/bin/hawknet |
| Transport | stdio |
| Arguments | None |
If your client does not expand ~, use the full absolute path instead.
Important: your AI client should launch the Hawknet executable directly. Do not point the client at Hawknet’s internal daemon endpoint. Let Hawknet handle that connection for you.
Quick Check
After adding Hawknet manually:
- Open Roblox Studio with any place file.
- Make sure the Hawknet plugin shows Connected.
- Ask your AI client to do something simple, like “Show me the children of Workspace.”
If it does not connect, check Troubleshooting.