Handle long-running MCP work
Modern servers may return a task from an ordinary tool call, which Ax can auto-await or expose for input, cancellation, and observation. Legacy task-draft APIs remain compatibility-only.
Worked example
See the idea in context
auto result = client->call_tool(
"start_reindex", axllm::object({{"scope", "all"}}));
auto task_id = axllm::display(axllm::Core::get(
axllm::Core::get(result, "task", axllm::Value::object()),
"taskId", ""));
target.waitFor = axllm::array({axllm::object({
{"kind", "mcp.task"}, {"value", "taskKey"},
{"metadata", axllm::object({{"taskId", task_id}})},
})});
runtime.register_target(std::move(target)).start();
runtime.publish(start_event, "tenant:demo", "authenticated");
source->start_scoped([&](axllm::AxEventEnvelope event,
std::string scope, std::string trust) {
runtime.publish(event, scope, trust);
});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.
From a clone of the ax repo:
npm run example -- cpp src/examples/cpp/mcp/native_mcp_tools.cppActive practice
Answer 2 in a row to learn this · attempt 1