Connect to an MCP server You initialize one negotiated MCP session over the transport that fits your deployment. Streamable HTTP is the normal current choice for a remote server. go academy academy/topics/mcp-lifecycle-transports website/content-src/academy/course.mjs academy Connect to an MCP server
Unit 9 · Connect to external tools and data

Connect to an MCP server

You initialize one negotiated MCP session over the transport that fits your deployment. Streamable HTTP is the normal current choice for a remote server.

AxMCPClient8 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})
  1. Create the transport

    Streamable HTTP connects the client to the remote URL.

  2. Create one client session

    AxMCPClient owns negotiation and the protocol lifecycle.

  3. Use a namespace

    orders keeps discovered names clear when several servers are attached.

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

Source-backed follow-up