Connect an outside service
For a beta user: connect an MCP server in the console, check that it answers, re-read its tools, learn what testing a tool costs, and take it away again.
For a beta user who wants an App to use a service outside Kortecx, such as a ticket tracker or a chat tool. After this page you can connect a server, see its tools and whether it answers, and remove it. Not here: the bundled connectors and every option (Connect outside services) or storing the credential (Store secrets).
MCP is family 08, which reads four bars evidenced in the census at revision 3ec0e4f4, 2026-10-20. Three of those bars read under the older census rule, not the newer one: reachable, measured and natural-language. The console bar reads under the newer rule.
As of 2026-10-21, this page gives the console path only. The cloud SDK and command line name methods for the connector catalog and for the connectors you wrote, and none for registering, testing or removing a server. The cloud SDK is also built from source until its first publish.
Connect a server
Open Connectors in the left rail of the console. Choose Register, give the connection a name, and say how to reach it: a program to start, or an https address. Or choose Browse the catalog, which lists the connectors the platform ships and says whether each can be registered here, and choose Fork on one to make your own copy.
A registration that names a secret your workspace has not stored is refused, and a registration of an address that names a secret is refused with the reason. How a connector gets its key depends on its catalog row and on what your deployment has switched on; see Store secrets.
A server reached by address must be on the host allow-list an operator keeps, and a program must be on an operator's list of programs; none is on it by default. Anything not listed is refused. Only a by-hand registration of an address refused for its host can use Ask an operator to allow it, and only where the deployment takes host requests.
Registering dials the server at once and lists the tools it exposes. Where your org has admins, registering, removing and re-discovering a shared connection are for an owner or an admin.
See it and check it
The Connectors page lists your connections. Each shows how many tools it brought in and one plain line, such as that its tools can be granted to runs or that they cannot fire here. Open a connection to see its health as last recorded: connected, unreachable or unknown. A server that could not be dialed is kept and reads unreachable, never as a success.
In the same drawer, Test asks whether the server answers now and reads Reachable now or Not reachable. Discover tools dials it again and reads how many tools it found, which is how you pick up a tool the service gained or lost; if the dial fails it reports that the server could not be reached to look, not a count.
About testing one tool
MCP in the left rail opens a page with a Tools tab. A tool that comes from one of your connections and can fire shows a Test section in its drawer. That test is not a free check. It is a real model run on a model provider connected to your workspace, which may call the tool once, and that provider bills the model turn whether or not it does. A workspace with no connected provider is refused. The result reads that the tool ran, or that it did not and why. This page gives no steps for it; nothing else fires a tool by hand.
Take it away
Open the connection and choose Remove, which asks you to type the name back before anything is written. Removing unregisters the connection from your workspace and forgets its catalog link and any label or switched-off tools you set on it. To use it again, register it again.
What it does not do yet
Dated gaps, as of 2026-10-21.
- Firing a tool directly. A standalone tool call is not built on this deployment yet, and answers that it is not supported. A tool fires inside a run, and a server's own line on the Connectors page says whether its tools can fire here.
- Driven live. Everything on this page is read from the console source and the cloud code at the cited revisions. None of it was driven against a deployed console for this page.
What it refuses
You see only your own workspace's connections. The census tenancy check for this family reads PARTIAL: a static scope audit, with no cross-tenant probe receipt.
Find a recipe you can reuse
For a beta user: search your catalog of recipes by what you want done, and read the task signatures the catalog publishes.
See the tools a run can use
For a beta user: see the tools your runtime has registered, read which can fire, and know why a listed tool is not a granted one.