DevJock.aiIntegrations and Mappings
How DevJock connects to the outside world through MCP, mappings, model providers, embedding, and the Claude Code plugin.
DevJock is meant to sit inside your existing stack, not replace it. This section covers the ways the platform reaches out to other systems and the ways other systems reach into it.
What lives here
- MCP servers and tools. DevJock exposes an MCP-over-HTTP API, so agents and external clients can call its capabilities as tools. You can also register outside MCP servers for your agents to use.
- Mappings. Links between DevJock entities and records in external systems, so a task, agent, or other object stays connected to its counterpart elsewhere.
- LLM model providers. A large catalog of models reached through a gateway, with zero-data-retention options where the provider supports them.
- Embedding DevJock. An embeddable chat widget you can drop into your own site or app.
- The Claude Code plugin. A plugin that connects Claude Code to your DevJock workspace.
Start here
MCP servers and tools
Register MCP servers and expose or consume tools over HTTP.
Mappings
Link DevJock entities to records in external systems.
LLM model providers
Reach many model providers through one gateway, with ZDR options.
Claude Code plugin
Connect Claude Code to your DevJock workspace.
Embedding DevJock
Add the DevJock chat widget to your own site or app.
Use the Claude Code Plugin
Install the DevJock plugin for Claude Code and connect it to a workspace so you can reach agents, tasks, and memories without leaving your terminal.
MCP Servers and Tools
How DevJock uses the Model Context Protocol to let agents call tools, register external servers, and expose itself to outside clients.