Architecture

Agenetix organizes around three product paths. Each path creates or consumes MCP servers differently, but they share a common runtime, authorization, and agent infrastructure.

Product paths#

flowchart LR
    Create["Create"] --> Choose{"Choose a path"}
    Choose --> Connect["Connect existing MCP"]
    Choose --> Generate["Generate from OpenAPI"]
    Choose --> Agents["Build Agents"]
    Connect --> ConnServer["Connected server"]
    Generate --> GenServer["Generated server"]
    ConnServer --> GW["Optional Gateway"]
    GenServer --> GW
    ConnServer --> ObsTools["Observed tools"]
    GenServer --> ManagedTools["Managed tools + rules"]
    ObsTools --> Attach["Attach to Agent"]
    ManagedTools --> Attach
    Agents --> Attach
    Attach --> Runtime["Agent runtime\n+ embedded SDK"]

Connect existing MCP#

For teams that already run an MCP server. Agenetix connects to the live URL, discovers tools, and provides logging, analytics, optional Gateway auth, and agent attachment.

Tools are observed — Agenetix records what the server exposes but does not modify the upstream server's behavior. Tool editing is not available by default for connected servers.

Generate from OpenAPI#

For teams with a REST API and an OpenAPI spec. Agenetix parses endpoints, creates durable tool records with editable rules, and generates a deployable MCP server.

Tools are managed. You can edit descriptions, instructions, when-to-use/not-to-use guidance, and examples. These rule fields survive OpenAPI refreshes — your customizations are never lost when you update the spec.

Build Agents#

For developers building AI products. An agent combines MCP servers (any mix of connected and generated) with a system prompt and LLM configuration into an embeddable chat experience via the @emcy/agent-sdk.

Agents never modify MCP servers or tools. They only control which servers are attached and which tool subsets are enabled per server.

Gateway as capability#

Gateway is not a product path. It is an attachable capability that adds OAuth authentication, request logging, and rate limiting to either connected or generated servers.

flowchart TB
    subgraph ConnectPath["Connect path"]
        CS["Connected MCP"]
    end
    subgraph GeneratePath["Generate path"]
        GS["Generated MCP"]
    end
    CS --> GW["Gateway\nOAuth + logging + rate limits"]
    GS --> GW
    GW --> Agent["Agent runtime"]

• For Connect: Gateway puts auth and logging in front of your existing MCP server
• For Generate: the generated server runs behind the Agenetix auth edge

How agents use tools at runtime#

When an end user sends a chat message through the agent SDK:

1. The SDK sends the message to Agenetix
2. Agenetix loads the agent config and all attached MCP servers
3. Relevant tools are selected using semantic matching against the user's message
4. The LLM decides which tools to call based on your tool descriptions and rules
5. Agenetix proxies tool calls to the MCP servers (via Gateway or directly)
6. Results stream back to the SDK in real time