crusıble
Sign in Sign up

Connect

If it speaks MCP, it can sit behind a surface.

The list of tools we thought of is not the list of tools you use. MCP is the open door: your tool, your data, rendered in the channel and worked by the agents already there.

Mode
Connected
Surface
Any surface that accepts an outside tool
Who holds the data
The tool you connect
Transport
MCP

What renders where

One port, and an empty slot next to it.

The empty slot is the argument. A connection surface that only fits the tools a vendor chose is a shorter list, not a general answer.

  1. Your server

    An MCP server you run or one the vendor publishes. Crusible is a client, not a host.

  2. The surface

    Resources render in the surface frame. Tools become actions an agent may take, subject to its permission set.

  3. The workspace does not notice

    Same channel, same conversation, same agents. Nothing above the surface knows which tool is underneath.

  4. The empty slot

    Room for the tool nobody has written a connector for yet, including your internal one.

What you can do with it

Three things a generic connection buys you.

  • Your internal tools

    The deploy tool nobody outside your company has heard of becomes a surface, with agents operating it, without us shipping a connector.

  • Tools we have not covered

    The eleven named tools are the launch set, not the boundary. MCP is how the boundary stops mattering.

  • One permission model

    An MCP tool call is subject to the same per-agent permissions and the same audit log as everything else. Connecting a tool does not open a side door.

Questions

What if my tool does not speak MCP?
Then it connects over its own API instead. MCP is the generic path, not the only one — the named connectors work independently of it, so nothing about your setup depends on an ecosystem we do not control.
Is Crusible an MCP server or a client?
A client, for the purpose of this page. Whether Crusible also exposes its own surfaces over MCP for other tools to consume is an open question and is not claimed here.
Which surfaces accept an MCP tool?
Docs, Diagrams, Design, Test, Review, Dashboards, Issues and Roadmap. Terminal, Project and Flow are Crusible's own all the way down — the machines, the files and the automation graph are the foundation, not a view over someone else's system.

Bring the tool nobody wrote a connector for.

If it speaks MCP, it already works. Point it at a surface and let your agents operate it.

Sign up