Practical overview
When it fits
Use it when a team needs to build AI assistants or workflow automations and wants both a visual builder and a TypeScript-based development path. Its two-way synchronization is especially relevant when technical and non-technical contributors share responsibility for agent definitions.
Who it is for
- Engineering teams defining agents and custom tools in TypeScript.
- Non-technical teams creating or managing agent definitions in the visual builder.
- Organizations building customer-facing assistants or internal copilots.
- Teams automating tasks such as CRM updates or helpdesk ticket triage.
Documented uses
- Create and manage agent definitions in the visual builder or TypeScript SDK, synchronizing between them.
- Build assistants for help centers, technical documentation, in-app experiences or internal teams.
- Coordinate specialized agents in a multi-agent application.
- Configure MCP tools and credentials for agents.
- Embed chat interfaces in web applications and track activity with traces.
Requirements & limits
- The visual builder and TypeScript SDK are described as interoperable, with two-way synchronization.
- The framework includes a REST API for agent configuration and execution, plus evaluation capabilities.
- It uses the Vercel AI SDK to interface with language-model providers.
- The repository specifies Elastic License 2.0 subject to Inkeep’s Supplemental Terms; review those terms for intended use.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Define a basic agent and sub-agent with the TypeScript SDK
Create a declarative agent configuration that assigns a sub-agent and makes an MCP tool available to it.
Before you start
- The
@inkeep/agents-sdkpackage and a locally definedconsoleMcpimport, as shown in the repository example.
Steps
Import
agentandsubAgentfrom@inkeep/agents-sdk, and import the MCP tool definition.Define a sub-agent with an ID, name, description,
canUsereturning the MCP tool, and a prompt.Define and export an agent with its own ID, name, and description, using the sub-agent as its default and listing it in
subAgents.
Expected outcome
A TypeScript agent definition with a default sub-agent and an MCP tool available to that sub-agent.
Guide limitations
- The example defines the agent configuration; it does not document installing dependencies, running the agent, or deploying it.
- The repository states that SDK definitions and the Visual Builder are interoperable, but does not give synchronization steps in this example.
Compare options for Agent orchestration
These projects document a common task and share a project role. This is a source-based comparison, not an execution benchmark or a guarantee of interchangeability.
| Project | Documented purpose | Platform | Access and requirements |
|---|---|---|---|
| Agents — inkeep | Create and manage agent definitions in the visual builder or TypeScript SDK, synchronizing between them. | Cloud, Docker, Self-hosted, Server | |
| Agenite | Define typed tools with JSON Schema validation and error handling. | CLI | |
| Veldra | Create an agent with a policy, tools, skills, knowledge base and reasoning method. | Self-hosted | The documented deployment is self-hosted and uses a sign-in gate after a first-run administrator account is created. |
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 16 October 2026
- Original website title
- inkeep/agents · Official homepage title · retained in its source language

