Unit 9 · Connect to external tools and data

Handle long-running MCP work

You can monitor progress, provide requested input, cancel, or resume work that finishes later. Recording and deterministic replay make the protocol lifecycle testable.

11 focused minutesNot started

Worked example

See the idea in context

runtime.RegisterTarget(target)
runtime.AddSource(started)
runtime.AddSource(mcp)
taskResult, err := client.CallTool("start_reindex", map[string]ax.Value{"scope": "all"})

Run itIn your own project

go get github.com/ax-llm/ax/packages/go

import axllm "github.com/ax-llm/ax/packages/go"

client := axllm.NewAI("openai", map[string]axllm.Value{"apiKey": os.Getenv("OPENAI_API_KEY")})
classify := axllm.NewAx("review:string -> sentiment:class \"positive, negative, neutral\"", nil)

Set OPENAI_APIKEY in your environment before running provider-backed code.

In the ax repo

From a clone of the ax repo:

npm run example -- go src/examples/go/mcp/native_mcp_tools.go

Active practice

Show that you can use it

Answer 2 in a row to learn this · attempt 1

Keep exploring

See the idea in context

Show that you can use it

Source-backed follow-up