---
title: "Developer overview"
url: "/build"
description: "What you can integrate with today — the widget SDK, custom webhook tools, and MCP servers — and what KlicForge does not yet offer."
productArea: build
audience: ["developer"]
tags: ["developers"]
lastReviewed: 2026-07-28
---

# Developer overview (/build)





Most of KlicForge is configured in the dashboard rather than in code. This section covers the
parts you integrate with programmatically.

## What you can build with [#what-you-can-build-with]

| Surface                                         | Use it to                                                                 |
| ----------------------------------------------- | ------------------------------------------------------------------------- |
| [Widget SDK](/build/widget-sdk)                 | Embed the chat widget, control it from JavaScript, react to events        |
| [Custom webhook tools](/skills-and-tools/tools) | Let an agent call your own HTTP API                                       |
| MCP servers                                     | Connect an agent to an external system through the Model Context Protocol |

## What KlicForge does not currently offer [#what-klicforge-does-not-currently-offer]

<Callout type="warn">
  **There is no public REST API with API keys.** KlicForge does not issue API keys or bearer tokens,
  and there is no general-purpose developer API for managing agents, contacts or data from your own
  backend. The dashboard is the management surface.
</Callout>

Also not available today:

* **Outbound webhooks.** KlicForge does not post events to your endpoints when something
  happens. To react to a conversation, have the agent call one of your
  [custom webhook tools](/skills-and-tools/tools) instead.
* **Server-to-server chat.** The endpoints the widget uses are tied to an allowed-origin
  browser context and are not a substitute for a server API.

If your integration depends on either, say so through support — knowing what people need shapes
what gets built.

## Custom webhook tools [#custom-webhook-tools]

The practical way to connect KlicForge to your own systems today. You define the endpoint,
method, parameters and auth headers in the dashboard; the agent calls it during a conversation
and uses the result in its answer.

This inverts the usual integration direction: instead of KlicForge notifying you, your agent
asks you at the moment it needs to know. For most workflows — look up an order, create a
ticket, check availability — that is the more useful shape anyway.

See [tools](/skills-and-tools/tools) for how to define one.

## MCP servers [#mcp-servers]

An agent can connect to an external system through the Model Context Protocol, which exposes
that system's tools to the agent. Connect providers under **Settings → MCP Providers**, then
choose which of their tools each agent may use.

## Agent configuration as files [#agent-configuration-as-files]

An agent's behaviour lives in four Markdown files — IDENTITY, SOUL, AGENTS and USER — which you
can edit in the dashboard. They are worth understanding even if you never touch the platform
programmatically, because they are where an agent's behaviour actually comes from. See
[core prompt files](/agents/core-prompt-files).

## Related pages [#related-pages]

* [Widget SDK](/build/widget-sdk)
* [Tools](/skills-and-tools/tools)
* [Web widget](/channels/web-widget)