Skip to content

Integrations

Manifest Platform is designed to connect with external systems. This section covers how to bring third-party tools, APIs, and event sources into the platform -- and how to push platform events out to your own infrastructure.

Integration Architecture

The platform supports three primary integration patterns:

graph LR
    subgraph "External Systems"
        MCP["MCP Servers"]
        WH_TARGET["Webhook Targets"]
        EXT_API["External APIs"]
    end

    subgraph "Manifest Platform"
        AGENTS["Agents"]
        WORKFLOWS["Workflows"]
        CONNECTORS["Connectors"]
        HSL["Hosted Services"]
        EVENTS["Event Bus"]
    end

    MCP -->|"Tool Discovery"| AGENTS
    MCP -->|"Tool Discovery"| WORKFLOWS
    CONNECTORS -->|"Data Access"| EXT_API
    EVENTS -->|"Event Delivery"| WH_TARGET
    HSL -->|"Custom Logic"| EXT_API

Inbound Integrations

Bring external capabilities into the platform:

Pattern Description Use Case
MCP Servers Register external Model Context Protocol servers to expose their tools to agents and workflows Adding tools from third-party AI tool providers
Connectors Structured integrations with databases, SaaS APIs, and file systems Reading/writing data from external sources
Hosted Services Custom code blocks that call external APIs using the FlowSDK Domain-specific business logic that composes platform and external services

Outbound Integrations

Push platform events to external systems:

Pattern Description Use Case
Webhooks HTTP callbacks triggered by platform events Notifying Slack, PagerDuty, or CI/CD systems when workflows complete
Connector Write Operations Push data to external systems through connector instances Writing results back to a customer's database

How Integrations Work with Agents

Agents can use tools from multiple sources simultaneously. When an agent runs, it has access to:

  1. Built-in tools -- Platform-native tools (dataset query, code execution, etc.)
  2. MCP tools -- Tools discovered from registered MCP servers
  3. Hosted service tools -- Endpoints from hosted services exposed as agent tools
  4. Connector operations -- Operations from connector instances registered as tools

The agent's tool selection logic chooses the appropriate tool based on the user's request and the tool descriptions provided by each source.

Tool namespacing

Tools from different sources are automatically namespaced to prevent conflicts. An MCP tool from a GitHub server might appear as github/create_issue, while a built-in tool would be platform/query_dataset.

Integration Sections

  • MCP Servers

    Register external MCP servers to expand the tools available to agents and workflows. Supports SSE and stdio transports.

    MCP Servers

  • Webhooks

    Configure HTTP callbacks to receive real-time notifications when platform events occur. Includes retry logic and signature verification.

    Webhooks

Next Steps