Connect an MCP Server

DevJock agents call tools over the Model Context Protocol (MCP). By registering an external MCP server, you let your agents use the tools that server exposes, alongside the tools DevJock provides. This guide covers the flow at a high level. For exact fields and options, see the MCP servers and tools reference.

Add the server

Open the Developer group in the app and go to MCP Servers. Add a new server and give it a clear name so it is easy to recognize when you assign tools later.

Provide the server's endpoint, the URL where DevJock reaches it. If the server requires authentication, supply its credentials here. DevJock stores them with the server record so agents do not handle secrets directly.

Once saved, DevJock can connect to the server and read the list of tools it offers.

Make its tools available to an agent

Registering a server makes its tools known to DevJock. To let a specific agent call them, associate the tools with that agent under Agents in the Developer group. An agent only calls tools that are made available to it, so you control which servers each agent can reach.

Verify the connection

After assigning tools, start a chat session with the agent or run it against a task and confirm it can invoke the tool. If a call fails, check the endpoint and credentials on the server record, then confirm the tool is still associated with the agent.

Where this fits

DevJock itself exposes an MCP-over-HTTP API, so the same protocol that lets your agents call outside tools also lets outside clients call DevJock. Registered servers and their tools live under MCP Servers in the Developer group.