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

auto mcp = std::make_shared<axllm::AxMCPClient>(transport, axllm::object({{"namespace", "inventory"}}));
  auto catalog = mcp->inspect_catalog();
axllm::AxExecutionContext context({mcp});
context.attach(program);
  mcp->close();

Create the transport
Streamable HTTP connects the client to the remote URL.
Create one client session
AxMCPClient owns negotiation and the protocol lifecycle.
Use a namespace
orders keeps discovered names clear when several servers are attached.

Run itIn your own project

include(FetchContent)
FetchContent_Declare(axllm GIT_REPOSITORY https://github.com/ax-llm/ax GIT_TAG main SOURCE_SUBDIR packages/cpp)
FetchContent_MakeAvailable(axllm)
target_link_libraries(your_app PRIVATE axllm::axllm)

#include <axllm/axllm.hpp>

auto llm = axllm::ai("openai", axllm::object({{"apiKey", std::getenv("OPENAI_API_KEY")}}));
auto classify = axllm::ax("review:string -> sentiment:class \"positive, negative, neutral\"");

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 -- cpp src/examples/cpp/mcp/native_mcp_tools.cpp

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