opendock-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@opendock-mcp list my warehouses"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Opendock MCP Server
An MCP server that connects AI assistants (Claude, etc.) to the legendary Opendock Neutron API.
Install
No clone or build needed — just use npx:
npx -y opendock-mcpOr install globally:
npm install -g opendock-mcpRelated MCP server: yt-mcp-server-odoo
Tools
69 tools across 11 categories:
Category | Tools |
General |
|
Warehouses |
|
Docks |
|
Load Types |
|
Appointments |
|
Carriers |
|
Companies |
|
Orgs |
|
Audit Log |
|
Settings Metadata |
|
Metrics |
|
Prerequisites
Node.js 18+
An Opendock account with API access
Authentication
The server supports two authentication methods:
Option 1: Username/password (recommended) — the server handles login and token refresh automatically.
OPENDOCK_USERNAME=user@example.com
OPENDOCK_PASSWORD=your-passwordOption 2: Pre-existing JWT token
OPENDOCK_TOKEN=your-jwt-tokenOptionally set the API URL:
OPENDOCK_API_URL=https://neutron.opendock.com # production (default)OPENDOCK_API_URL=https://neutron.staging.opendock.com # stagingUsage with Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"opendock": {
"command": "npx",
"args": ["-y", "opendock-mcp"],
"env": {
"OPENDOCK_USERNAME": "user@example.com",
"OPENDOCK_PASSWORD": "your-password"
}
}
}
}Usage with Claude Code
claude mcp add opendock -- npx -y opendock-mcpSet the required environment variables before launching Claude Code, or pass them in the MCP config.
Testing
Use the MCP Inspector to test interactively:
OPENDOCK_USERNAME=user@example.com OPENDOCK_PASSWORD=your-password \
npx @modelcontextprotocol/inspector npx -y opendock-mcpDevelopment
git clone https://github.com/Pollamin/opendock-mcp.git
cd opendock-mcp
npm install
npm run buildLicense
MIT
Available Tools
71 toolsadd_appointment_tagB
Add a tag to an appointment
Inputs: id (required), tag (required).
create_appointmentB
Schedule a new appointment
Inputs: warehouseId (required), dockId (required), loadTypeId (required), startTime (required), +4 more.
create_carrierB
Create a new carrier user
Inputs: email (required), phone, firstName, lastName, +1 more.
create_companyC
Create a new carrier company
Inputs: name, scac, mc, usdot, +1 more.
create_dockC
Create a new dock
Inputs: warehouseId (required), name, doorNumber, instructions, +6 more.
create_load_typeC
Create a new load type
Inputs: direction (required), warehouseId, orgId, name, +6 more.
create_recurring_appointmentsB
Create a recurring appointment series from an existing appointment
Inputs: id (required), numWeeks (required), weekDays (required), copyFields (required).
create_warehouseB
Create a new warehouse (billable event — implies additional subscription costs)
Inputs: name (required), facilityNumber, country, timezone, +8 more.
delete_appointmentC
Cancel/delete an appointment
Inputs: id (required).
delete_dockC
Delete a dock
Inputs: id (required), hardDelete.
delete_load_typeC
Delete a load type
Inputs: id (required).
delete_recurring_appointmentsA
Delete all recurring appointments in a series (excludes the original)
Inputs: id (required).
delete_warehouseB
Delete a warehouse
Inputs: id (required).
export_appointment_metrics_excelC
Retrieve file link with the appointment list as XLSX. The link points to an external file.
Inputs: emailCCs (required), dockIds, loadTypeIds, carrierIds, +6 more.
export_yard_data_excelA
Retrieve file link with the yard data list as XLSX. The link points to an external file.
Inputs: no named parameters.
find_and_book_appointmentA
Find the next available slot for a load type and book it in one step.
Calls the first-available-appointment endpoint to get open slots across all docks and load types, filters to the requested loadTypeId (and optionally a preferred dock), then creates the appointment automatically. Use this instead of manually chaining get_first_available_appointment + create_appointment.
Inputs: loadTypeId (required), warehouseId (required), dockId, carrierId, +2 more.
get_appointmentB
Get details for a specific appointment
Inputs: id (required).
get_appointment_avg_duration_by_dock_and_statusC
Appointment duration average by dock and status
Inputs: no named parameters.
get_appointment_avg_duration_by_load_typeB
Appointment duration average by load type
Inputs: no named parameters.
get_appointment_avg_duration_by_statusC
Appointment duration average by status
Inputs: no named parameters.
get_appointment_count_by_status_for_carrierB
Appointment count by status for current carrier
Inputs: no named parameters.
get_appointment_count_for_carrierC
Appointment count per carrier
Inputs: carrierId (required).
get_appointment_count_for_docksC
Appointment count per dock
Inputs: dockIds (required).
get_appointment_status_timesC
The average time spent in each appointment status
Inputs: no named parameters.
get_appointment_volume_by_carrierC
Appointment volume by carrier
Inputs: no named parameters.
get_appointment_volume_by_dateC
Appointment volume by date
Inputs: no named parameters.
get_appointment_volume_by_day_of_weekC
Appointment duration average by dock and day of week
Inputs: no named parameters.
get_appointment_volume_by_load_typeB
Appointment volume by load type and week day
Inputs: no named parameters.
get_appointment_volume_by_time_of_dayC
Appointment volume by time of day
Inputs: no named parameters.
get_audit_logB
Get the audit log for an object (warehouse, dock, appointment, etc.)
Inputs: objectId (required).
get_booked_carriersB
Get carriers that have booked appointments
Inputs: no named parameters.
get_carrierB
Get details for a specific carrier
Inputs: id (required).
get_carrier_status_percentagesB
Retrieve carrier insights data with each status percentage
Inputs: no named parameters.
get_companyA
Get details for a specific carrier company
Inputs: id (required).
get_dockC
Get details for a specific dock
Inputs: id (required).
get_dock_availabilityC
Get availability for a specific dock
Inputs: id (required), startDate (required), endDate (required).
get_dock_dwell_timeB
Retrieve dock metrics of dwell time by day of week
Inputs: fromDate, toDate, warehouseId, dockId.
get_first_available_appointmentA
Finds the next available appointment time for each dock and loadtype, starting from the current date and time onward
Inputs: no named parameters.
get_load_typeC
Get details for a specific load type
Inputs: id (required).
get_load_type_availabilityB
Get available appointment slots for a load type
Inputs: id (required), startDate (required), endDate (required).
get_orgA
Get details for an organization
Inputs: id (required).
get_profileA
Get the current authenticated user's profile
Inputs: no named parameters.
get_public_appointmentA
Get public appointment details (no auth required)
Inputs: id (required).
get_reserve_count_for_userC
Reserve count for user
Inputs: userId.
get_setting_metadataA
Get a specific setting metadata entry by entity type and setting key
Inputs: entityType (required), settingKey (required).
get_settings_metadataB
Get all settings metadata for an entity type
Inputs: entityType (required).
get_versionA
Get the opendock-mcp server version
Inputs: no named parameters.
get_warehouseB
Get details for a specific warehouse
Inputs: id (required).
get_warehouse_capacity_usageB
Retrieve warehouse dock capacity usage information per warehouse
Inputs: dockIds.
get_warehouse_hoursB
Get hours of operation for a warehouse's docks
Inputs: id (required), startDate, endDate.
get_warehouse_insightsD
Retrieve warehouse insights
Inputs: no named parameters.
list_appointment_metricsC
Retrieve an appointment list that matches the criteria described in the request body
Inputs: dockIds, loadTypeIds, carrierIds, tags, +5 more.
list_appointmentsA
List and search appointments using NestJSX/Crud query syntax. Supports advanced filtering, field selection, joins, and sorting.
SEARCH (s=): JSON search with operators. When s= is provided, startDate/endDate/status/warehouseId/dockId convenience filters are ignored. Operators: $eq, $ne, $gt, $lt, $gte, $lte, $cont, $contL (case-insensitive contains), $starts, $ends, $in, $notin, $between, $isnull, $notnull Combinators: $and, $or Examples: Scheduled after a date: s='{"$and":[{"status":"Scheduled"},{"start":{"$gt":"2026-03-15T08:00:00.000-07:00"}}]}' Changed since a date: s='{"lastChangedDateTime":{"$gt":"2026-03-15T08:00:00.000Z"}}' Soft-deleted since a date: s='{"$and":[{"lastChangedDateTime":{"$gt":"2026-07-07T00:00:00.000Z"}},{"isActive":false}]}' Has tag "Late": s='{"tags":{"$contL":"Late"}}' Empty tags: s='{"tags":{"$or":{"$isnull":true,"$eq":"{}"}}}'
JOIN: Fetch related data in a single request. Each join is a separate array element. Examples: Get carrier info: join=["user","user.company"] Carrier email + company name only: join=["user||email,companyId","user.company||name"]
FIELDS: Comma-separated list of fields to return. Example: fields="refNumber,start,lastChangedDateTime,status"
SORT: Each sort is "field,direction". Use array for multi-sort. Examples: sort=["start,ASC"] or sort=["start,DESC","status,ASC"]
Inputs: page, limit, offset, warehouseId, +9 more.
list_carriersB
List carriers with optional filters
Inputs: page, limit, name.
list_companiesB
List carrier companies with optional filters and pagination
Inputs: page, limit, s, sort, +2 more.
list_docksB
List docks with optional filters
Inputs: warehouseId, page, limit.
list_load_typesB
List load types with optional filters
Inputs: warehouseId, page, limit.
list_warehousesB
List warehouses with optional filters and pagination
Inputs: page, limit, name, city, +2 more.
remove_appointment_tagB
Remove a tag from an appointment
Inputs: id (required), tag (required).
search_appointmentsA
Free-text search for appointments. Use this when searching by keyword across appointment fields. For structured filtering/querying, use list_appointments instead.
Inputs: searchStr, scheduledStart, scheduledEnd, statuses, +9 more.
sort_docksB
Save dock sort order
Inputs: docks (required).
undo_appointment_statusB
Undo the latest status change for an appointment
Inputs: id (required).
update_appointmentC
Modify or reschedule an existing appointment
Inputs: id (required), startTime, endTime, dockId, +5 more.
update_carrierC
Update a carrier user
Inputs: id (required), phone, firstName, lastName, +1 more.
update_companyC
Update a carrier company
Inputs: id (required), name, scac, mc, +2 more.
update_dockC
Update a dock
Inputs: id (required), name, doorNumber, instructions, +6 more.
update_favorite_carriersC
Update the list of favorite carriers for an organization
Inputs: orgId (required), carrierIds (required).
update_load_typeC
Update a load type
Inputs: id (required), name, direction, operation, +5 more.
update_orgC
Update an organization
Inputs: id (required), name, settings, favoriteCarrierIds.
update_warehouseC
Update a warehouse
Inputs: id (required), name, facilityNumber, street, +13 more.
validate_settings_metadataC
Validate settings for an entity type
Inputs: entityType (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 71 tools
Most tools have clearly distinct names and descriptions, but the numerous similar analytic tools (e.g., get_appointment_volume_by_*) may cause confusion for an agent selecting the exact metric needed.
The naming follows a consistent verb_noun pattern with snake_case, but there are minor deviations like find_and_book_appointment and undo_appointment_status.
With 71 tools, the count is excessive for the domain of dock appointment management. Many tools are analytical metrics that could be consolidated, and the server includes trivial utilities like get_version.
Core CRUD is covered for most entities, but notable gaps exist: no delete_carrier, delete_company, or tools for managing organizations beyond update_org.
Maintenance
Related MCP Connectors
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
One MCP server for the services your AI needs: memory, files, Microsoft 365, kanban and more.
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
Related MCP Servers
- AlicenseBqualityDmaintenanceAn MCP server that integrates with the OpenClaw API to enable AI assistants to send messages across multiple platforms, execute system commands, and manage calendar events and emails.51MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to interact with Odoo ERP, allowing natural language queries, record creation, updates, and deletions.LGPL 3.0
- AlicenseNot gradedqualityFmaintenanceMCP server for the OCPI SDK that enables AI-assisted communication with EV charging infrastructure via the Open Charge Point Interface protocol.59 npm3Apache 2.0
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to manage Defined Networking / Managed Nebula infrastructure, supporting tasks like network topology design, host provisioning, and security auditing through natural language.4MIT