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.

DevJock speaks the Model Context Protocol (MCP) over HTTP. MCP is a standard way for a model to discover and call tools at runtime. In DevJock, agents use MCP to reach the tools they need, and DevJock itself is reachable over MCP by outside clients.

Agents call tools

A tool is a single callable action an agent can invoke while it works, for example reading a task, creating a memory, or calling an external service. Tools are grouped under MCP servers. When an agent runs, the tools available to it are advertised, and the model decides which to call and with what arguments. You do not wire calls by hand; you make the right tools available and the agent selects among them.

Register external MCP servers

You can connect MCP servers that DevJock did not author. Register a server under the Developer group in MCP Servers, point DevJock at its HTTP endpoint, and supply any credentials it requires. Once registered, the tools that server exposes become available to your agents alongside the built-in DevJock tools. This is how you extend the fleet with your own services or third-party MCP servers without changing agent prompts.

DevJock as an MCP endpoint

DevJock also exposes its own MCP endpoint over HTTP, so an external client can drive DevJock the same way an internal agent does. Through it a client can create and read tasks, work with memories and files, run agents, and use chat. Access uses OAuth bearer authentication, and the surface is the AI and Agents API. The DevJock plugin for Claude Code connects this way.

Keep protocol wiring light. Register the server, confirm its tools appear, and let agents call them. For the exact tool and endpoint list, use the live interactive API reference from the app's user menu.

Agents

How an agent pairs a prompt with a model and the tools it can call.

Embed

Drop the DevJock chat widget into your own product.