
Opendock
- 2 repo stars
- Updated February 19, 2026
- Pollamin/opendock-mcp
Opendock MCP is an MCP server that integrates coding agents with the Opendock Neutron API through the opendock-mcp stdio package.
About
Opendock MCP is a Model Context Protocol server that connects coding agents to the Opendock Neutron API, the programmatic layer behind Opendock’s scheduling and logistics platform. developers and small teams building warehouse, carrier, or dock-management features use it during integration work so the agent can call Neutron operations while scaffolding backends, scripts, or admin tools. The published package uses stdio transport via npm identifier opendock-mcp at version 5.1.1, which suits Claude Desktop and local Claude Code setups that run MCP servers as child processes. Place it on Build / Integrations because value appears when you are implementing against a live vendor API, not when you are only researching market ideas. You will still need Opendock credentials and API familiarity from Opendock’s own docs. It is an API-integration MCP, not a turnkey SEO or listing product.
- stdio npm package opendock-mcp (registry version 5.1.1) for local MCP clients
- MCP surface for the Opendock Neutron API used in dock and yard scheduling workflows
- GitHub repository Pollamin/opendock-mcp for server implementation reference
- Fits agent-driven exploration and automation against Opendock backend capabilities
- Developer-tool category integration rather than a hosted-only remote in the published schema
Opendock by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add opendock-mcp -- npx -y opendock-mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| repo stars | ★ 2 |
|---|---|
| Package | opendock-mcp |
| Transport | STDIO |
| Auth | None |
| Last updated | February 19, 2026 |
| Repository | Pollamin/opendock-mcp ↗ |
What it does
Expose Opendock Neutron API operations to your agent through MCP so logistics or dock-scheduling features can be built and tested from Claude Code or Cursor.
Who is it for?
Best when you're backend developers shipping software that must talk to Opendock Neutron during development and testing.
Skip if: Non-developers seeking a no-code logistics product, or teams with no Opendock tenant and API access.
What you get
After you install opendock-mcp locally, your agent can use MCP tools aligned to the Neutron API while you build scheduling, dock, or logistics features.
- Local MCP tool surface mapped to Opendock Neutron API operations
- Faster agent-assisted integration testing against Opendock endpoints
- Repeatable dev workflow for logistics features without manual API paste loops
By the numbers
- npm package identifier opendock-mcp at version 5.1.1
- Transport type stdio per published MCP registry packages entry
- Described scope: MCP for the Opendock Neutron API
README.md
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-mcp
Or install globally:
npm install -g opendock-mcp
Tools
69 tools across 11 categories:
| 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 |
| Load Types | list_load_types, get_load_type, get_load_type_availability, create_load_type, update_load_type, delete_load_type |
| Appointments | list_appointments, search_appointments, get_appointment, create_appointment, update_appointment, delete_appointment, get_public_appointment, undo_appointment_status, create_recurring_appointments, delete_recurring_appointments, add_appointment_tag, remove_appointment_tag |
| 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 |
| Audit Log | get_audit_log |
| Settings Metadata | get_settings_metadata, get_setting_metadata, validate_settings_metadata |
| 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_type, get_appointment_avg_duration_by_status, get_appointment_avg_duration_by_dock_and_status, get_appointment_count_for_carrier, get_appointment_count_by_status_for_carrier, get_appointment_count_for_docks, get_reserve_count_for_user, get_dock_dwell_time, get_carrier_status_percentages, list_appointment_metrics, export_appointment_metrics_excel, get_appointment_status_times, get_first_available_appointment, get_warehouse_insights, get_warehouse_capacity_usage, export_yard_data_excel |
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-password
Option 2: Pre-existing JWT token
OPENDOCK_TOKEN=your-jwt-token
Optionally set the API URL:
OPENDOCK_API_URL=https://neutron.opendock.com # production (default)
OPENDOCK_API_URL=https://neutron.staging.opendock.com # staging
Usage 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-mcp
Set 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-mcp
Development
git clone https://github.com/Pollamin/opendock-mcp.git
cd opendock-mcp
npm install
npm run build
License
MIT
Recommended MCP Servers
How it compares
Stdio MCP wrapper for Opendock Neutron API, not a hosted marketplace of unrelated skills.
FAQ
Who is Opendock MCP for?
It is for developers and teams using MCP agents to build or automate against the Opendock Neutron API for dock and logistics scheduling.
When should I use Opendock MCP?
Use it during Build when you are implementing integrations, debugging Neutron calls, or prototyping agent-assisted workflows against Opendock from your IDE.
How do I add Opendock MCP to my agent?
Install and configure the npm package opendock-mcp (v5.1.1) as a stdio MCP server in Claude Desktop, Cursor, or Windsurf, supplying Opendock Neutron API credentials per Opendock and the opendock-mcp GitHub README.