jbaruch/koog
Koog 1.0 idioms, gotchas, and scaffolding skills for Kotlin agents on the JVM
88
88%
Does it follow best practices?
Impact
88%
1.95xAverage score across 43 eval scenarios
Passed
No known issues
task.mdevals/scenario-39/
Connect a Koog Agent to an Older MCP Server
Problem/Feature Description
A developer has a Koog 1.0 agent in Kotlin running on the JVM. They want it to talk to an internal MCP server their team set up for querying customer records. The server operator has told them the server is from an older deployment and only supports the event-stream wire protocol over HTTP, not the newer streaming protocol. The server is at https://mcp.internal.example/sse.
Their agent main file already uses runBlocking. They don't have MCP wired up at all yet — nothing in build.gradle.kts, nothing in the agent construction.
Output Specification
Walk through how to connect the agent to this server. Produce the modified source files and the Gradle dependency change in a single response.
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
scenario-17
scenario-18
scenario-19
scenario-20
scenario-21
scenario-22
scenario-23
scenario-24
scenario-25
scenario-26
scenario-27
scenario-28
scenario-29
scenario-30
scenario-31
scenario-32
scenario-33
scenario-34
scenario-35
scenario-36
scenario-37
scenario-38
scenario-39
scenario-40
scenario-41
scenario-42
scenario-43
skills
add-observability
add-persistence
add-rag
add-structured-output
add-token-budgeting
add-tool
cache-llm-calls
define-prompt
domain-model-subtask-pipeline
references
enable-prompt-caching
handle-agent-events
manage-state
migrate-from-0-x
model-planner-subtasks
persist-chat-history
query-sql-from-agent
scaffold-agent
snapshot-and-restore
test-koog-agents
trace-agent-internals
use-attachments
use-functional-agent
use-llm-node-variants
use-planner
wire-a2a
wire-acp-server
wire-ktor-server
wire-mcp-server
wire-spring-boot