Skip to main content
Connectors provide ready-to-use integrations with popular external services. Each connector can be used in two ways depending on your use case.

​
Integration Modes

App Mode

Import the connector as an app into your workspace and call automations directly from DSUL.Best for: Workflow automations, data pipelines, scheduled jobs

MCP Mode

Connect the MCP endpoint to AI Knowledge projects. AI agents discover and use tools automatically.Best for: AI agents, conversational interfaces, dynamic tool selection

​
Available Connectors

Jira

Search, create, and manage Jira issues. Supports both Jira Cloud and Data Center deployments.

Outlook

Read, send, and manage emails via Microsoft Graph API. Full mailbox access with folder management.

Excel

Read and write Excel workbooks stored in OneDrive or SharePoint. 50+ operations for worksheets, ranges, tables, and charts.

SharePoint

Browse and download files from SharePoint document libraries. Supports per-user access validation.

​
Choosing the Right Mode

CriteriaApp ModeMCP Mode
CallerDSUL automationsAI agents (LLM)
Tool discoveryManual (you specify which automation)Automatic (agent selects tools)
AuthenticationWorkspace configHeaders, user session, or workspace config
Use caseDeterministic workflowsConversational AI, agentic tasks

​
When to Use App Mode

  • You’re building a workflow automation (e.g., sync data on a schedule)
  • You know exactly which operations to call
  • You want to chain multiple operations in a single automation
  • You don’t need AI to decide which operations to use
# Example: App mode in DSUL
- Jira.searchJira:
    jql: "project = DEV AND status = 'In Progress'"
    maxResults: 10
    output: results

​
When to Use MCP Mode

  • You’re building an AI agent that needs access to external services
  • The agent should dynamically choose which operations to call
  • Users interact via natural language (chat interface)
  • You want tool discovery and schema introspection
// Example: MCP tool call from AI agent
{
  "name": "searchJira",
  "arguments": {
    "jql": "project = DEV AND status = 'In Progress'",
    "maxResults": 10
  }
}

​
Architecture

Each connector follows a two-workspace pattern:
The App workspace contains:
  • Business logic and API client code
  • Authentication handling
  • Data transformation
The MCP workspace contains:
  • JSON-RPC 2.0 endpoint
  • Tool definitions with schemas
  • Output formatting for LLM consumption

​
Next Steps

Jira Connector

Get started with Jira integration

Building Custom Connectors

Create your own connector for any API