Opendock
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.
Overview
Opendock MCP is an MCP server for the Build phase that integrates coding agents with the Opendock Neutron API through the opendock-mcp stdio package.
What is this MCP server?
- 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
- 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
Community signal: 2 GitHub stars.
What problem does it solve?
Developers integrating Opendock waste time copying Neutron API docs and curl examples into chat without structured tools the agent can invoke safely.
Who is it for?
Solo or small-team backend builders 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 do I get? / Deliverables
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
Recommended MCP Servers
Journey fit
Opendock MCP is a bridge to a third-party logistics API during product construction, which aligns with Build when you wire external services into your app or internal tools. Integrations is the canonical subphase for MCP servers that wrap vendor HTTP APIs (here Neutron) rather than owning UI or growth analytics.
How it compares
Stdio MCP wrapper for Opendock Neutron API, not a hosted marketplace of unrelated skills.
Common Questions / FAQ
Who is Opendock MCP for?
It is for developers and indie 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.