ā†back to changelog

Introducing the Skill Server Integration

Expose any ChatBotKit skillset as a text-first HTTP API that agents can read and invoke directly - no MCP client, no JSON-RPC, just a single authenticated endpoint.

We're introducing the Skill Server Integration - a simpler, agent-first way to expose your ChatBotKit skillsets. It's the sibling of the MCP Server integration: same skillset, but instead of speaking the Model Context Protocol, a Skill Server is just a plain HTTP endpoint that any agent, script, or curl can drive.

How it works

A Skill Server exposes a single authenticated URL, dispatched by HTTP method:

  • GET returns a manual - a concise, text-first description of every ability in the linked skillset and how to call it. It's generated from the skillset itself, so it always reflects what is actually callable.
  • POST invokes an ability by name with its input.

That's the whole protocol. An agent reads the manual once, then calls abilities directly. No client library, no JSON-RPC envelope, no handshake.

Why you'll like it

  1. No client required - Works with any agent framework, automation tool, shell script, or cron job. If it can make an HTTP request, it can use a Skill Server.
  2. Self-describing - The manual documents the available abilities and their inputs, so agents discover capabilities on their own.
  3. Text-first - Responses are plain text by default (token-cheap and resilient to context truncation), with structured JSON available on demand via a ?format=json query parameter or an Accept: application/json header.
  4. Flexible input - Pass a structured object or, for freeform abilities, a plain string. The server normalizes and coerces loosely-typed input.
  5. Secure by default - Each integration gets its own static access token. Every request, including the manual, is authenticated.

Getting started

Create a Skill Server integration, attach a skillset, and save to generate your endpoint and access token. Point your agent at the endpoint - GET it for the manual, POST to invoke - and you're done.

The Skill Server integration sits right alongside the MCP Server integration, so you can expose the same skillset both ways and let each consumer pick the transport that suits it.

integrationskillsetskillserveragentapi