MCP server for the Opendock dock scheduling and warehouse management API.
MCP server for the Opendock dock scheduling and warehouse management API. Exposed over MCP by the opendock mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Set the required environment variables before launching Claude Code, or pass them in the MCP config.
opendock-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Everything the assistant can do here goes through one of these:
Category — ToolsGeneral — get_version, get_profileWarehouses — list_warehouses, get_warehouse, get_warehouse_hours, create_warehouse, update_warehouse, delete_warehouseDocks — list_docks, get_dock, create_dock, update_dock, delete_dock, sort_docks, get_dock_availabilityAppointments — list_appointments, search_appointments, get_appointment, create_appointment, update_appointment, delete_appointment, get_public_appointmentCarriers — list_carriers, get_carrier, create_carrier, update_carrier, get_booked_carriersCompanies — list_companies, get_company, create_companyOrgs — get_org, update_org, update_favorite_carriersMetrics — get_appointment_volume_by_date, get_appointment_volume_by_carrier, get_appointment_volume_by_load_type, get_appointment_volume_by_time_of_dayYou will need 4 environment variables: OPENDOCK_USERNAME, OPENDOCK_PASSWORD, OPENDOCK_TOKEN, OPENDOCK_API_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Opendock's toolset — Category, General, Warehouses and 6 more — is a fair guide to whether it matches your workflow. It is maintained by Pollamin; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Category | Tools |
| General | get_version, get_profile |
| Warehouses | list_warehouses, get_warehouse, get_warehouse_hours, create_warehouse, update_warehouse, delete_warehouse |
| Docks | list_docks, get_dock, create_dock, update_dock, delete_dock, sort_docks, get_dock_availability |
| Appointments | list_appointments, search_appointments, get_appointment, create_appointment, update_appointment, delete_appointment, get_public_appointment, undo_appointment_status, create_recurring_appointments, delete_recurring_appoin |
| Carriers | list_carriers, get_carrier, create_carrier, update_carrier, get_booked_carriers |
| Companies | list_companies, get_company, create_company |
| Orgs | get_org, update_org, update_favorite_carriers |
| Metrics | get_appointment_volume_by_date, get_appointment_volume_by_carrier, get_appointment_volume_by_load_type, get_appointment_volume_by_time_of_day, get_appointment_volume_by_day_of_week, get_appointment_avg_duration_by_load_t |
{
"mcpServers": {
"opendock": {
"command": "npx",
"args": ["-y", "opendock-mcp"],
"env": {
"OPENDOCK_USERNAME": "user@example.com",
"OPENDOCK_PASSWORD": "your-password"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| OPENDOCK_USERNAME | Configuration value read at startup. | Optional |
| OPENDOCK_PASSWORD | Configuration value read at startup. | Optional |
| OPENDOCK_TOKEN | Credential the server authenticates with. | Yes |
| OPENDOCK_API_URL | Endpoint or connection string the server talks to. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.