Dock
Let agents read and update Dock workspace tables, rich docs, formulas, and media so product specs and runbooks live where humans and agents collaborate.
Overview
Dock MCP is a Build-phase MCP server that connects coding agents to Try Dock’s tables, docs, formulas, and media via trydock.ai/api/mcp.
What is this MCP server?
- AI workspace combining tables, docs, formulas, images, and 4K video
- Remote MCP at trydock.ai/api/mcp (streamable-http)
- Designed for humans, teams, and multiple agents on shared data
- Open MCP package repository at github.com/try-dock-ai/mcp
- Server version 1.1.0 with website at trydock.ai
- Package version 1.1.0
- 1 remote endpoint: https://trydock.ai/api/mcp (streamable-http)
- Reference repository: https://github.com/try-dock-ai/mcp
What problem does it solve?
Agent sessions drift from your real specs and task boards when context lives only in the IDE and scattered markdown files.
Who is it for?
Small teams and solo builders who centralize specs, ops notes, and agent workflows in Dock alongside development.
Skip if: Developers who want repo-only workflows with no external workspace or who need deep GitHub Issues/Jira-native MCP instead.
What do I get? / Deliverables
Agents can ground plans and updates in Dock’s shared tables and docs so PM artifacts stay synchronized with implementation work.
- Agent-driven reads and updates to Dock tables, docs, and formulas
- Shared PM artifacts aligned with implementation threads in your IDE agent
Recommended MCP Servers
Journey fit
Dock is where execution artifacts accumulate across build, operate, and grow, but the first journey moment is structuring work during active product build. PM subphase fits unified tables, docs, and formulas that track backlogs, specs, and delivery status for solo builders wearing every hat.
How it compares
Collaborative workspace MCP, not an infra deployer or a single-purpose API integration skill.
Common Questions / FAQ
Who is ai.trydock/dock for?
Solo builders and lean teams that run product and ops in Dock and want coding agents to read and write that workspace over MCP.
When should I use ai.trydock/dock?
Use it during build and PM-heavy phases when specs, tables, and docs should stay the single source of truth while agents implement features.
How do I add ai.trydock/dock to my agent?
Create or use a Dock account at trydock.ai, configure your agent’s MCP client with remote URL https://trydock.ai/api/mcp per Dock and github.com/try-dock-ai/mcp guidance.