loading
Loading content
loading
MCP
Hosted Streamable HTTP at api.trickest.io/mcp. Same Token header as the platform API. Cursor, Claude Code, or Codex builds and runs workflows from its own loop.
No package and no local server. Point any MCP client at the hosted endpoint and pass a Settings API token with the Token scheme.
{ "mcpServers": { "trickest": { "url": "https://api.trickest.io/mcp", "headers": { "Authorization": "Token <YOUR_TOKEN>" } } }}Same shape in Cursor, Claude Code, Codex, or any Streamable HTTP client. Token from Settings › Developer › API Token. Full setup.
The client discovers Trickest tools and runs them from its own loop. Same MCP mark every compatible host shows.
Thought briefly
Thought for 1s
Fleet is warm. Running the chain serially via MCP, starting with gau-history.
Thought for 2s
Build, distribute, and read results. Same engine as the CLI, called as tools.
Inspect a workflow before changing it: the graph and how data moves.
› Show me the discovery workflow
Put Python or Bash beside library tools as first-class steps.
› Drop a Python step after httpx
Link ports by schema, or embed a whole workflow as one node.
› Connect outputs into the next module
Execute on managed or self-hosted machines. Parallel where the graph allows.
› Fan this scan across the fleet
Read Live Tables and declared outputs after the run lands.
› Which hosts are still open on 443?
Start a run from the agent loop and wait for status before the next step.
› Execute and tell me when it finishes
Full client configs in the docs. Write code yourself with the SDK.
MCP is one of four ways in. Pick the next cut of the stack.
Get a personalized demo
A 30-minute walkthrough. We map the platform to your stack and answer pricing and deployment questions for your environment.