Agenetix

Concepts

Platform lifecycle

How the Agenetix packages and services work together across development, deployment, and runtime.

5 sections

Agenetix has several components that run in different places. Understanding where each piece fits helps you plan your integration.

Components#

ComponentWhere it runsWhat it does
Agenetix Dashboardagenetix.comWeb UI for managing servers, tools, agents, and Gateway
Agenetix APIagenetix.comREST API backing the dashboard and SDKs
@emcy/openapi-to-mcpYour machine / CInpm package that parses OpenAPI specs and generates MCP server code
@emcy/agent-sdkYour app (browser)Embeddable chat widget, SSE streaming client, MCP auth flows
@emcy/sdkYour generated MCP serverLightweight telemetry SDK that reports tool calls back to Agenetix

End-to-end flow#

MERMAID
flowchart LR
    Dev["Your machine"] -->|"@emcy/openapi-to-mcp"| Spec["OpenAPI spec"]
    Dev -->|"@emcy/agent-sdk"| App["Your app"]
    Dev -->|"Dashboard or CLI"| Backend["Agenetix"]
    Spec --> Backend
    Backend --> Generated["Generated MCP server"]
    Backend --> Connected["Connected MCP server"]
    Backend --> GW["Optional Gateway"]
    Generated --> AgentRT["Agent runtime"]
    Connected --> AgentRT
    AgentRT --> App
    App -->|"@emcy/sdk telemetry"| Backend

Generate path#

  1. Import an OpenAPI spec via the dashboard
  2. Agenetix parses the spec and creates a tool for each operation
  3. Edit tool rules — descriptions, instructions, when-to-use guidance
  4. Download or publish the generated MCP server
  5. The generated server includes @emcy/sdk for telemetry
  6. Create an Agent and attach the generated server
  7. Embed @emcy/agent-sdk in your app
  8. End users chat and Agenetix orchestrates tool calls

Connect path#

  1. Provide a live MCP server URL
  2. Agenetix discovers its tools automatically
  3. Optionally front the server with a Gateway for auth
  4. Create an Agent and attach the connected server
  5. Same embedding and chat flow as Generate

Updates never destroy your work#

  • OpenAPI refresh merges changes — new tools are added, changed tools are updated, removed tools are disabled (not deleted), and your custom rules are always preserved
  • Rediscovery for connected servers follows the same safe merge approach
  • Tool rule edits and server configuration are separate operations that cannot accidentally overwrite each other