The Agentic Services tab in Organisation Settings is where administrators configure the AI agent runners and MCP servers that power Agentic Ops.
Agentic services configuration

​
Configure an agent provider

Process Central supports agent runners including Claude Code, OpenCode and Codex.
1

Open the Agentic Services tab

Organisation switcher → Organisation Settings → Agentic Services.
2

Enter the runner endpoint and API key

Point it at your agent runner / server endpoint and provide its key.
3

Set the Default Model

See the format note below — this is the most common source of errors.
4

Test the connection

Confirm the runner is reachable before saving.

​
Default Model format (important)

For OpenCode, the model must be written as <provider-id>/<model-id>, where the first segment matches a provider defined in the OpenCode server’s opencode.json: 
openrouter/anthropic/claude-sonnet-4-6
ollama/gpt-oss:latest
A bare vendor prefix (e.g. qwen/...) fails with ProviderModelNotFoundError. The first segment must be the OpenCode provider id, not the model vendor.

​
MCP servers

You can register public MCP servers here and attach them to skills.
How an attached MCP server is used depends on the provider’s runner. For OpenCode, MCP servers are loaded from the OpenCode server’s own opencode.json config — attaching one to a skill in Process Central does not push it to OpenCode. For runners that accept MCP servers per run, the skill’s attached servers are forwarded automatically.
See Agentic Ops for creating and running skills and agent tasks.