read_guideLABSCO SUMMARY
talk_to_app closes the loop — build it, deploy it, then say something to it.
Most build-a-bot tooling stops at deploy. Here the same session sends a message to the deployed app and reads the reply back, so a change is verified where it lands rather than in a separate console. read_guide is the sensible first call: it returns the canonical workflow instead of leaving the model to infer the order.
What it is
Omilia's own server for OCP. 31 tools that create an orchestrator app, spin up agents, attach knowledge, wire an HTTP tool, deploy and talk to the result. It runs locally and calls OCP over authenticated HTTPS.
What you get
- 31 tools
- Discovery — read_guide, list_groups, list_agents, list_knowledge_bases, list_pathfinder_projects, search_orchestrator_apps, search_miniapps, search_numbers, search_variable_collections, search_dialog_logs
- Orchestrator apps created, read, wired to a Concierge, deployed and messaged — create_orchestrator_app, get_orchestrator_app, add_concierge_to_orc_app, deploy_orc_app, talk_to_app
- Concierge and Task agents created, instructed, and given sub-agents or escalation queues — create_agent, update_agent_instructions, update_concierge, add_agent_to_concierge, add_escalation_queue_to_agent
- WebService miniapps as HTTP tools, created, read, edited, prompted and attached to a Task agent — create_webservice_miniapp, get_miniapp, edit_webservice_miniapp, set_miniapp_prompt, create_webservice_agent, add_tool_to_webservice_agent
- Knowledge attached — create_pathfinder_project, add_faq_to_agent to crawl a URL into an FAQ, add_knowledge_base_to_agent
- Variables and dialog logs read — get_collection_variables, get_dialog_logs
Requirements
Node 20 or later and uv. npx github:omilia/mcp init runs a wizard that picks your client, collects credentials with masked input, checks prerequisites and prints a pass or fail smoke test before it exits. Authentication is either OCP_USERNAME, OCP_PASSWORD and OCP_KEYCLOAK_REALM (default master), or a personal access token in OCP_ACCESS_TOKEN. Credentials are held in memory only. Claude Desktop, Claude Code, Cursor, VS Code and Codex are supported.
Setup effort
One command plus credentials — npx github:omilia/mcp init, then supply credentials
USE CASES
01
Standing up an agent from nothing
Create the orchestrator app, add a Concierge, deploy it, then send it a message and read the reply — one sequence, one session.
02
Giving an agent knowledge it did not have
Crawl a URL into a Pathfinder FAQ and attach it, or link a knowledge base that already exists.
03
Letting the agent call your own API
Create a WebService miniapp for the endpoint, set its prompts, and attach it to a Task agent as a tool.
04
Working out why a conversation went wrong
Search the dialog logs by group, app and date, then pull the full log for the dialog id that matters.
31 tools
Listed in project docs. Your client may show a different list.
list_groupslist_agentslist_knowledge_baseslist_pathfinder_projectssearch_orchestrator_appssearch_miniappssearch_numberssearch_variable_collectionssearch_dialog_logscreate_orchestrator_appget_orchestrator_appadd_concierge_to_orc_appdeploy_orc_apptalk_to_appcreate_agentupdate_agent_instructionsupdate_conciergeadd_agent_to_conciergeadd_escalation_queue_to_agentcreate_webservice_miniappget_miniappedit_webservice_miniappset_miniapp_promptcreate_webservice_agentadd_tool_to_webservice_agentcreate_pathfinder_projectadd_faq_to_agentadd_knowledge_base_to_agentget_collection_variablesget_dialog_logsBEFORE YOU INSTALL
What to know first
Tools you get
31 tools named in the project's documentation. With a PAT, five tools fail and need a Keycloak Bearer token: create_pathfinder_project, list_pathfinder_projects, add_faq_to_agent, list_knowledge_bases and add_knowledge_base_to_agent. That leaves 26 working.
Requires
- OCP_BASE_URL in your environment
- OCP_ACCESS_TOKEN — or OCP_USERNAME and OCP_PASSWORD — in your environment
INSTALLATION
Connect your client
Server setup
TERMINAL
npx github:omilia/mcp initAnswer the wizard's prompts: pick your client, choose how to authenticate, and enter your OCP base URL and credentials. It checks for Node 20+ and uv, installs the config, and prints a PASS/FAIL smoke-test summary before exiting.
Restart your client, then ask it to use the read_guide tool to show the index of available OCP guides.
MCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add OCP --scope user \
--env OCP_BASE_URL=<YOUR_OCP_BASE_URL> \
--env OCP_ACCESS_TOKEN=<YOUR_OCP_ACCESS_TOKEN> \
-- npx -y github:omilia/mcp runThe blocks above sign in with a personal access token (OCP_ACCESS_TOKEN). To use your OCP username and password instead — the project's recommended method — put OCP_USERNAME, OCP_PASSWORD and OCP_KEYCLOAK_REALM in the same env block; the server picks the method from whichever variables are set. The realm is master by default; Kubernetes deployments use ocp. npx github:omilia/mcp init asks for all of this for you.
Claude Desktop — npx, Cursor — npx
JSON
{
"mcpServers": {
"OCP": {
"command": "npx",
"args": [
"-y",
"github:omilia/mcp",
"run"
],
"env": {
"OCP_BASE_URL": "<YOUR_OCP_BASE_URL>",
"OCP_ACCESS_TOKEN": "<YOUR_OCP_ACCESS_TOKEN>"
}
}
}
}The blocks above sign in with a personal access token (OCP_ACCESS_TOKEN). To use your OCP username and password instead — the project's recommended method — put OCP_USERNAME, OCP_PASSWORD and OCP_KEYCLOAK_REALM in the same env block; the server picks the method from whichever variables are set. The realm is master by default; Kubernetes deployments use ocp. npx github:omilia/mcp init asks for all of this for you.
Claude Desktop — MCPB bundle
CLAUDE DESKTOP — MCPB BUNDLE · TERMINAL
curl -LO https://github.com/omilia/mcp/raw/main/ocp-mcp-server.mcpbOpen Claude Desktop → Settings → Connectors (or Extensions).
Click Install Extension and select ocp-mcp-server.mcpb (or double-click the .mcpb file in Finder).
Claude Desktop prompts you for OCP_BASE_URL and OCP_ACCESS_TOKEN.
Click Install, then restart the conversation.
The blocks above sign in with a personal access token (OCP_ACCESS_TOKEN). To use your OCP username and password instead — the project's recommended method — put OCP_USERNAME, OCP_PASSWORD and OCP_KEYCLOAK_REALM in the same env block; the server picks the method from whichever variables are set. The realm is master by default; Kubernetes deployments use ocp. npx github:omilia/mcp init asks for all of this for you.
VS Code
VS CODE · JSON
{
"servers": {
"OCP": {
"command": "npx",
"args": [
"-y",
"github:omilia/mcp",
"run"
],
"env": {
"OCP_BASE_URL": "<YOUR_OCP_BASE_URL>",
"OCP_ACCESS_TOKEN": "<YOUR_OCP_ACCESS_TOKEN>"
}
}
}
}The blocks above sign in with a personal access token (OCP_ACCESS_TOKEN). To use your OCP username and password instead — the project's recommended method — put OCP_USERNAME, OCP_PASSWORD and OCP_KEYCLOAK_REALM in the same env block; the server picks the method from whichever variables are set. The realm is master by default; Kubernetes deployments use ocp. npx github:omilia/mcp init asks for all of this for you.
Codex
CODEX · TERMINAL
npx github:omilia/mcp init --client codex --printThe blocks above sign in with a personal access token (OCP_ACCESS_TOKEN). To use your OCP username and password instead — the project's recommended method — put OCP_USERNAME, OCP_PASSWORD and OCP_KEYCLOAK_REALM in the same env block; the server picks the method from whichever variables are set. The realm is master by default; Kubernetes deployments use ocp. npx github:omilia/mcp init asks for all of this for you.
