Actions that create themselves. The customer points Chatbase at the API they already have, reviews the generated actions, and enables them.
The problem
Today, every action is typed by hand: name, when to use, data inputs, method, URL, parameters, headers, body, test, data access. One full wizard per endpoint. Three endpoints means the whole thing three times.
Meanwhile, the customer's API is usually already described somewhere: an OpenAPI spec, a Postman collection, or their docs. None of that information is used.
The proposal
Point. Paste a spec URL, upload a file, or paste docs. Given a base URL, well known paths like /openapi.json are probed automatically.
Review. Every generated action appears with its inputs, descriptions, and when to use, all editable.
Test. One click fires a real test call per action and validates the response.
Enable. Approved actions go live. The outcome is identical to the manual flow, minus the typing.
Discovery is not enablement. Nothing is callable until a human approves it. Read only endpoints import by default, write actions require explicit opt in.
What it improves
Setup effort goes from per endpoint to per API.
Auth moves from keys pasted into header fields to stored credentials, injected at call time.
When the API changes, a re sync re reads the spec and flags breaking changes instead of failing silently.
Plug any MCP server into a Chatbase agent. Paste a URL, authenticate, and the agent sees every tool that server exposes.
The problem
More and more tools ship an MCP server (Stripe, Shopify, Linear, and a fast growing long tail). Each one already exposes ready made, well described tools that any MCP aware agent can use. A Chatbase agent currently has no way to consume them, so those integrations get rebuilt by hand as individual actions, or skipped.
The Actions page today (July 2026): custom API calls and first party integrations, with no way to connect an MCP server.
The proposal
Once actions are tool definitions instead of hand typed forms, the same layer can consume tools from an MCP server:
Connect. The customer pastes the MCP server URL and authenticates with a token or OAuth.
Review. Every tool the server exposes appears in the same review screen as discovered actions, toggle on what the agent should have.
Enable. The agent can now use those tools, with the same guardrails and data access controls as any other action.
One engine, two inputs. Auto discovery covers the APIs that have no MCP server. Custom MCP covers everyone who already has one. Together they connect any customer system in minutes.
What it improves
An entire ecosystem of ready made integrations becomes available in seconds.
Tool descriptions and schemas come from the server itself, always up to date, nothing to maintain.
Customers who already invested in MCP connect with zero extra work.
