LABSCO SUMMARY
No fixed tool list: you build the tools, and Boltic hosts them.
There is nothing to evaluate until you build something, so what is worth judging is the platform's defaults, and the one that matters is authentication being on by default rather than a checkbox — a self-built MCP endpoint left open is the classic way to publish an internal workflow to the internet by accident.
What it is
Not one server but a factory. You compose actions from Boltic primitives — workflows and other building blocks — and the platform hosts the result. Every server you create gets its own URL, shown in the Connect MCP dialog.
What you get
The tools are whatever you built. Boltic calls them actions, and the documented types include exposing a Boltic workflow as a callable tool.
Requirements
A Boltic workspace. Authentication is built into the generated endpoints — OAuth 2.0 or a bearer token — so a server you create is not open by default.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Exposing an internal workflow to an agent
Wrap an existing Boltic workflow as an action and let a client call it, without writing a server.
02
Giving each team its own surface
Every created server has its own endpoint and its own authentication, so scopes are separated by construction.
BEFORE YOU INSTALL
What to know first
Requires
- an MCP client that can reach a remote endpoint
- OAuth 2.0 or a bearer token; authentication is built into every generated endpoint
INSTALLATION
Connect your client
Per-workspace: each user-created MCP server gets its own hosted endpoint URL, shown in the dashboard Connect MCP dialog; no public shared endpoint
Server setup
Go to the Overview tab of your MCP server in the Boltic dashboard and click Connect MCP.
Choose the client you want to connect — Cursor, Claude, Windsurf or Kaily.
Copy the setup command or configuration snippet for that client and run the command in your terminal to configure your client.
Requirements
- OAuth 2.0 or a bearer token; authentication is built into every generated endpoint
