
Opendock
io.github.PollaminPublished by GitHub account Pollaminv5.1.1Updated Oct 28, 2026
MCP for the Opendock Neutron API.
Overview
Connects an AI assistant to the Opendock Neutron API for warehouse dock scheduling: warehouses, docks, appointments, carriers and metrics.
- What you can do
- Read and manage warehouses, docks and load types, including availability and hours
- List, search, create, update and delete appointments, plus recurring appointments and tags
- Look up carriers, companies and organization settings, and read the audit log
- Inspect and validate settings metadata
- Query appointment volume, duration, dwell time and capacity metrics, and export yard or appointment data to Excel
- When to use it
- Useful when you manage dock or yard scheduling in Opendock and want an assistant to look up availability, book or change appointments, and pull operational metrics without switching to the web app.
- Requirements
- Node.js 18 or later, run locally via npx or a global npm install. An Opendock account with API access. Credentials are supplied by environment variable: OPENDOCK_USERNAME and OPENDOCK_PASSWORD, or a pre-existing token in OPENDOCK_TOKEN; OPENDOCK_API_URL optionally selects production or staging.
Installation
In SourceWeft
- Open Opendock in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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:
Or install globally:
Tools
69 tools across 11 categories:
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.
Option 2: Pre-existing JWT token
Optionally set the API URL:
Usage with Claude Desktop
Add to your claude_desktop_config.json:
Usage with Claude Code
Set the required environment variables before launching Claude Code, or pass them in the MCP config.
Testing
Use the MCP Inspector to test interactively:
Development
License
MIT
Source: README.md at commit 00b5941
Tools
0Version history
1- v5.1.1LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.