Named MCP endpoints that expose a curated subset of operations to an LLM
+Keys authenticate external clients and CI pipelines to the Crank API.
+| Name | +Key prefix | +Scopes | +Created | +Last used | +Status | ++ |
|---|
Real-time invocation log for all operations in this workspace.
+Manage your personal profile, security, and notification preferences.
+Invocation metrics for all operations in your workspace.
+| Operation | +Protocol | +Calls | +Errors | +Error rate | +Latency (p50 / p95 / p99) | +Quota | +
|---|
Select the transport protocol your upstream service uses. This determines how Crank will communicate with your API and which configuration options are available in subsequent steps.
+Choose an existing upstream — a shared host with its auth config — or register a new one. Then define the specific endpoint path this operation will call.
+{param} for path variables.Define the GraphQL operation this tool will execute. All requests are sent as HTTP POST to the endpoint configured in the previous step. Variables are populated from MCP tool arguments at runtime.
+$variable: Type syntax. In step 5 you will map MCP input fields to these variables. Crank serialises the final {"query","variables"} payload automatically.
+ Choose how to describe the gRPC service contract. Upload a .proto file, discover methods from a live server via reflection, or enter the route manually. Only unary RPCs are supported — streaming connections cannot be held open during MCP tool invocations.
.proto file hereChoose the HTTP verb this operation sends and configure content negotiation headers. Crank will serialize MCP tool arguments into the appropriate request body format.
+Name your tool, write the LLM-facing description, and define the input/output schemas. The description is the primary signal the model uses when deciding whether to call this tool.
+Define how MCP tool arguments map to upstream request fields, and how the upstream response maps back to MCP output. Then set execution parameters — auth is configured per-upstream in step 3.
+
- - The legacy React/Vite UI has been removed. A new operator console is being integrated on top of the same - deployment path. -
-- Backend services, MCP endpoints and deployment contracts remain intact. Replace this static entrypoint with - the new Alpine.js UI when it is ready. -
-Tool contracts that expose your upstream APIs as MCP tools
+Loading operations…
+Try adjusting your search or filters.
+| + NAME + + + + | +PROTOCOL | +STATUS | ++ CREATED + + + + | +TARGET URL | ++ |
|---|---|---|---|---|---|
|
+
+
+
+
+
+
+
+ |
+ + + | ++ + + + + | ++ |
+
+
+
+
+
+
+ |
+
+
+
+
+
+ |
+