JD
Back to Projects
Trunkline
trunkline.dev

An MCP registry that gives an organization a single endpoint for all of its tools, skills, and shared knowledge.

Next.jsMCPSaaSDeveloper Tools

Role

Creator & Developer

Timeline

2025 – Present

Stack

Next.jsTypeScriptTailwind CSSMCP Protocol

Problem

Teams adopting AI coding agents end up with a patchwork of config files, local servers, and shared docs that nobody can find. Tools built on one team stay invisible to the rest of the org. Onboarding a new engineer usually means rebuilding their setup from scratch.

Solution

Trunkline gives an organization one MCP endpoint to register against. Teams add their servers once and every member's agent picks up the tools automatically. Skills, guides, and runbooks live next to the tools so the same registry covers both code and documentation. Auth is handled with scoped API keys and role-based permissions. Pricing is per tool call rather than per seat, so the whole team can sign on without seat math.

Highlights

  • ·One MCP endpoint per organization, covering every registered tool
  • ·Auto-discovery: teammates pick up new tools without local config
  • ·Skills, guides, and runbooks stored alongside the tool registry
  • ·Scoped API keys and role-based access for tool-level permissions
  • ·Per-call pricing instead of per-seat licensing