Unit 9 · Connect to external tools and data

Discover what an MCP server offers

You inspect the negotiated catalog for tools, prompts, resources, templates, and capabilities. Your app uses server-owned identifiers instead of guessing them.

inspectCatalog()7 focused minutesNot started

Unit example (nearest native match)

See the idea in context

mcp := ax.NewAxMCPClient(transport, map[string]ax.Value{"namespace": "inventory"})
catalog, err := mcp.InspectCatalog(false)
defer func() { _ = mcp.Close() }()
program := ax.NewAx("request:string -> answer:string", map[string]ax.Value{"mcp": mcp})

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