LLMQore

Qt/C++ library for working with cloud and local LLM providers, create MCP servers and clients, download and using library MCP Bridge.

LLM clients — unified streaming API across all providers:

auto *client = new LLMQore::ClaudeClient(url, apiKey, model, this);
client->ask("What is Qt?", cb);

MCP server — expose tools, resources and prompts over stdio or HTTP:

// stdio (stdin/stdout, e.g. for Claude Desktop)
auto *transport = new LLMQore::McpStdioServerTransport(&app);

// or Streamable HTTP
auto *transport = new LLMQore::McpHttpServerTransport({.port = 8080, .path = "/mcp"}, &app);

auto *server = new LLMQore::McpServer(transport, cfg, &app);
server->addTool(new MyTool(server));
server->start();

MCP client — connect to MCP servers and bind their tools into LLM clients:

// Add servers one by one
client->tools()->addMcpServer({.name = "filesystem", .command = "npx",
    .arguments = {"-y", "@modelcontextprotocol/server-filesystem", "/home/user"}});

// Or load from a JSON config
client->tools()->loadMcpServers(QJsonDocument::fromJson(configData).object());

loadMcpServers accepts:

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/home/user"]
    }
  }
}

<img width="912" height="740" alt="Screenshot 2026-04-13 at 18 48 18" src="https://github.com/user-attachments/assets/2fb1ea83-1d2d-4016-9c87-56180dbf3301" />

See Quick Start for complete examples.

MCP Bridge

A standalone CLI tool built on llmqore that aggregates multiple MCP servers (stdio or SSE) and re-exposes them either behind a single HTTP/SSE endpoint or as one stdio server — useful when the upstreams and the client disagree on transport.

mcp-bridge bridge.json              # HTTP endpoint
mcp-bridge --stdio bridge.json      # stdio (for Claude Desktop and friends)

Config uses the familiar mcpServers schema:

{
  "port": 8808,
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/home/user"]
    }
  }
}

Prebuilt binaries for Linux/macOS/Windows (with Qt runtime bundled) are published to GitHub Releases. See MCP Bridge docs for full usage, config reference, and build instructions.

Supported Providers

Provider	Client class	Streaming	Tools	Thinking
Anthropic Claude	ClaudeClient	✓	✓	✓
OpenAI (Chat Completions)	OpenAIClient	✓	✓	✓
OpenAI (Responses API)	OpenAIResponsesClient	✓	✓	✓
Ollama	OllamaClient	✓	✓	✓
Google AI	GoogleAIClient	✓	✓	✓
Mistral	MistralClient	✓	✓	✓
llama.cpp	LlamaCppClient	✓	✓	✓
DeepSeek	OpenAIClient	✓	✓	✓

MCP (Model Context Protocol)

Client and server implementation of the MCP 2025-11-25 spec:

• Transports: stdio, Streamable HTTP
• Server: tools, resources, resource templates, prompts, completions, sampling, elicitation
• Client: tools, resources, prompts, completions, sampling, elicitation, roots

See MCP Protocol Coverage for the full spec-conformance matrix.

ACP (Agent Client Protocol)

Host/client implementation of Zed's Agent Client Protocol — drive an external coding agent (Claude Code, Gemini CLI, Codex, …) over stdio. LLMQore launches the agent, runs the session, streams its output as Qt signals, and services the agent's callbacks (permission, file system, terminal).

using namespace LLMQore::Acp;

// Agents are data, not code: load a catalogue