Skip to main content

MCP overview

An Intellectible workflow can act as an MCP server. An AI client discovers the tools you define, supplies arguments, and receives the results of the corresponding workflow logic. Use this to expose focused operations such as looking up a customer or preparing a report.

This differs from the ordinary Run workflow API: MCP clients exchange protocol messages to discover and call named tools, rather than sending a workflow run request.

Prepare the workflow​

A workflow needs both a server-definition path and handlers for its tools:

  1. Use MCP Server to define the server details, tool names, descriptions, and input schemas.
  2. Connect MCP Server Start to Set MCP Output, passing the MCP Server node’s configuration as its value.
  3. For each tool, add MCP Server Tool Call Event with the exact tool name.
  4. Use named Input nodes for the tool arguments and Set MCP Output to return the result.

The Workflows as MCP tools guide explains the editor setup. An ordinary workflow is not automatically an MCP server just because it has an endpoint URL.

Keep server-definition logic free of business side effects. Intellectible loads the definition for each HTTP request; discovering a tool should not also send a notification or change a record.

Connect a client​

Use an MCP client that supports Streamable HTTP and custom request headers.

SettingValue
URLhttps://app.intellectible.com/api/publicv1/projects/PROJECT_ID/workflows/WORKFLOW_ID/mcp
TransportStreamable HTTP
Authentication headerAuthorization: YOUR_PROJECT_API_KEY
Required permissionworkflows.run on the target workflow

Send the complete project key without a Bearer prefix. For the test environment, use its base URL and matching credentials. A client that only supports browser sign-in, or cannot supply this header, cannot use this authentication method directly.

Use the client’s normal MCP initialization and tool-discovery flow, then make a safe test call. See the endpoint reference for HTTP headers, JSON-RPC examples, and responses.

What this endpoint exposes​

The workflow defines the available tools and their argument schemas. This endpoint does not register MCP resources or prompts. Those are separate MCP concepts, not additional names for workflow tools.

The transport is stateless: it does not issue a persistent MCP session ID. Do not rely on server-side conversation memory or resumable event history between requests. Store application state explicitly in your project services.

Tool results are returned as MCP text content. Object results are JSON-encoded within that text, rather than returned as a separate structured-content field.

Permissions and safe tool design​

The API key authorizes execution of the target workflow. It does not select which of that workflow’s tools the caller may use. Separate workflows and keys when different callers need access to different operations.

Give tools precise descriptions and input schemas, validate arguments in the workflow, and avoid returning secrets. Tools may write data or contact external services; configure appropriate confirmation in the calling client and make repeatable actions idempotent.

Check Logs → API in the workflow when troubleshooting. The editor’s normal Run action does not simulate MCP initialization or a tool call. See Logs and troubleshooting.

Endpoint​