Skip to main content

The #1 agentic semantic tool search: 91.6% first-try accuracy on S1 Search Bench Explore Tool Discovery

Live 60 Actions

Talend MCP Server
for AI Agents

StackOne's Talend MCP server gives AI agents 60 ready-to-use actions for Talend — with built-in authentication, security, governance, token efficiency, and high tool-calling accuracy.

Talend logo
Talend MCP Server
Built by StackOne StackOne
DrataGPLocalyzeFlipMindtoolsScreenloop

Coverage

60 Agent Actions

Create, read, update, and delete across Talend — and extend your agent's capabilities with custom actions.

Authentication

Agent Tool Authentication

Per-user OAuth in one call. Your Talend MCP server gets session-scoped tokens with zero credentials stored on your infra.

Agent Auth →

Security

Agent Protection

Every Talend tool response scanned for prompt injection in milliseconds — 88.7% accuracy, all running on CPU.

Prompt Injection Defense →

Performance

Max Agent Context. Min Cost.

Free up to 96% of your agent's context window to enhance reasoning and reduce cost, on every Talend call.

Tools Discovery →

What is the Talend MCP Server?

A Talend MCP server lets AI agents read and write Talend data through the Model Context Protocol — Anthropic's open standard for connecting LLMs to external tools. StackOne's Talend MCP server ships with 60 pre-built actions, fully extensible via the Connector Builder — plus managed authentication, prompt injection defense, and optimized agent context. Connect it from MCP clients like Claude Desktop, Claude Code, Cursor, Goose, and VS Code, or from agent frameworks like OpenAI Agents SDK, LangChain, and Vercel AI SDK.

All Talend MCP Tools and Actions

Every action from Talend's API, ready for your agent. Create, read, update, and delete — scoped to exactly what you need.

Environments

  • Create Environment

    Create a new environment with an initial workspace via POST /orchestration/environments.

  • List Environments

    Retrieve all environments configured in Talend Cloud with optional FIQL filtering via GET /orchestration/environments.

  • Update Environment

    Update the name, description, or cloud container limit of an environment via PUT /orchestration/environments/{environmentId}.

  • Delete Environment

    Permanently remove an environment and all its contents via DELETE /orchestration/environments/{environmentId}.

Connections

  • Create Connection

    Create a new reusable connection with credentials and configuration via POST /orchestration/connections.

  • List Connections

    Retrieve all connections with optional filtering by environment, workspace, or name via GET /orchestration/connections.

  • Get Connection

    Retrieve full details of a specific connection via GET /orchestration/connections/{connectionId}.

  • Update Connection

    Modify the name or configuration parameters of an existing connection via PUT /orchestration/connections/{connectionId}.

  • Move Connection

    Move a connection to a different workspace within the same environment via PUT /orchestration/connections/{connectionId}/move/{targetWorkspaceId}.

  • Delete Connection

    Permanently remove a connection and its stored credentials via DELETE /orchestration/connections/{connectionId}.

Groups

  • Create Group

    Create a new user group for organizing users and managing permissions collectively via POST /account/groups.

  • List Groups

    Retrieve all user groups with optional name filtering and pagination via GET /account/groups.

  • Get Group

    Retrieve detailed information about a specific user group via GET /account/groups/{id}.

  • Update Group

    Rename an existing user group via a partial PATCH /account/groups/{id} update.

  • Delete Group

    Permanently remove a user group from the account via DELETE /account/groups/{id}.

Remote Engines

  • Create Remote Engine

    Register a new remote engine in an environment for on-premises job execution via POST /processing/runtimes/remote-engines.

  • List Remote Engines

    Retrieve all remote engines registered in the account with optional FIQL filtering via GET /processing/runtimes/remote-engines.

  • Get Remote Engine

    Retrieve detailed information about a specific remote engine via GET /processing/runtimes/remote-engines/{id}.

Remote Engine Clusters

  • List Remote Engine Clusters

    Retrieve all remote engine clusters for high-availability and load balancing via GET /processing/runtimes/remote-engine-clusters.

  • Get Remote Engine Cluster

    Retrieve detailed information about a specific remote engine cluster via GET /processing/runtimes/remote-engine-clusters/{clusterId}.

Schedules

  • Create Schedule

    Create a new orphan schedule with an initial trigger in a specified environment via POST /orchestration/schedules.

  • Clone Schedule

    Duplicate a schedule with all its triggers into a new orphan schedule via POST /orchestration/schedules/{scheduleId}.

  • List Schedules

    Retrieve all schedules with filtering by environment, description, and binding status via GET /orchestration/schedules.

  • Get Schedule

    Retrieve complete details of a schedule including all triggers and binding status via GET /orchestration/schedules/{scheduleId}.

  • Delete Schedule

    Delete an orphan schedule via DELETE /orchestration/schedules/{scheduleId} (only unbound schedules can be deleted).

Schedule Triggers

  • Add Schedule Trigger

    Add a new trigger to an existing schedule via POST /orchestration/schedules/{scheduleId}/triggers (max 15 per schedule).

  • Update Schedule Trigger

    Update an existing trigger's configuration within a schedule via PUT /orchestration/schedules/{scheduleId}/triggers.

  • Remove Schedule Trigger

    Remove a specific trigger from a schedule via DELETE /orchestration/schedules/{scheduleId}/triggers by trigger name.

Tasks

  • Create Task

    Create a new executable task in a workspace with artifact binding via POST /orchestration/executables/tasks.

  • List Tasks

    Retrieve all available tasks with filtering by environment, runtime, workspace, and artifact via GET /orchestration/executables/tasks.

Plans

  • Create Plan

    Create a new multi-step plan to orchestrate task workflows via POST /orchestration/executables/plans.

  • List Plans

    Retrieve all available plans with filtering by environment, workspace, task, and plan ID via GET /orchestration/executables/plans.

Users

  • Create User

    Create a new user account with profile details and optional invitation email via POST /account/users.

  • List Users

    Retrieve a paginated list of all users with profile details and role assignments via GET /account/users.

  • Get User

    Retrieve the full profile, access details, and role assignments for a specific user via GET /account/users/{id}.

  • Update User

    Update an existing user's profile via a full replacement PUT /account/users/{id} request.

  • Delete User

    Permanently delete a user account and revoke all access immediately via DELETE /account/users/{id}.

Roles

  • Create Role

    Create a new custom role with a name and optional permission assignments via POST /account/roles.

  • List Roles

    Retrieve all available roles with optional name filtering and pagination via GET /account/roles.

  • Get Role

    Retrieve the full definition of a specific role including all permission identifiers via GET /account/roles/{id}.

  • Update Role

    Update an existing custom role's name or permissions via full replacement PUT /account/roles/{id}.

  • Delete Role

    Permanently delete a custom role and unassign it from all users via DELETE /account/roles/{id}.

Workspaces

  • Create Workspace

    Create a new Custom workspace within an environment via POST /orchestration/workspaces.

  • List Workspaces

    Retrieve all workspaces with optional FIQL query filtering via GET /orchestration/workspaces.

  • Update Workspace

    Modify configuration of an existing workspace via PUT /orchestration/workspaces/{id} including name, owner, and artifact protection.

  • Delete Workspace

    Permanently remove a Custom workspace and cascade delete all contents via DELETE /orchestration/workspaces/{id}.

Other (14)

  • Add Users To Group

    Add one or more users to a group via POST /account/groups/{id}/users, granting group-level permissions immediately.

  • List Group Users

    Retrieve all users belonging to a specific group via GET /account/groups/{id}/users with pagination.

  • Get Current User

    Retrieve profile information about the currently authenticated user or service account via GET /account/me.

  • List Plan Executions

    Retrieve plan execution history with filtering by time range, status, environment, and workspace via GET /processing/executables/plans/executions.

  • List Artifacts

    Retrieve all available artifacts with filtering by environment, workspace, name, and type via GET /orchestration/artifacts.

  • List User Roles

    Retrieve all roles directly assigned to a specific user via GET /account/users/{id}/roles with pagination.

  • List Role Users

    Retrieve all users assigned a specific role via GET /account/roles/{id}/users with pagination.

  • Update Schedule Description

    Update the functional description of a schedule via PATCH /orchestration/schedules/{scheduleId} without modifying triggers.

  • Remove User From Group

    Remove a specific user from a group via DELETE /account/groups/{id}/users/{userId}, revoking group-level permissions.

  • Remove User From Role

    Remove a specific user from a role via DELETE /account/roles/{id}/users/{userId}, revoking the role's permissions.

  • Simulate Schedule Events

    Preview upcoming triggered events for a schedule within a time range via GET /orchestration/schedules/{scheduleId}/events.

  • Assign Roles To User

    Assign one or more roles to a user via POST /account/users/{id}/roles, granting all associated permissions immediately.

  • Revoke Role From User

    Remove a specific role from a user via DELETE /account/users/{id}/roles/{roleId}, revoking associated permissions.

  • Assign Role To Users

    Bulk assign a role to multiple users in a single POST /account/roles/{id}/users operation.

Set Up Your Talend MCP Server in Minutes

One endpoint. Any framework. Your agent is talking to Talend in under 10 lines of code.

MCP Clients

Agent Frameworks

Claude Desktop
{
  "mcpServers": {
    "stackone": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://api.stackone.com/mcp?x-account-id=<account_id>",
        "--header",
        "Authorization: Basic <YOUR_BASE64_TOKEN>"
      ]
    }
  }
}

More Workflow Automation MCP Servers

Talend MCP Server FAQ

Talend MCP server vs direct API integration — what's the difference?
A Talend MCP server and direct API integration serve different use cases. Direct API integration is for software-to-software — backend code calling Talend. A Talend MCP server is for AI agents — MCP clients like Claude and Cursor, plus framework agents built with OpenAI, LangChain, or Vercel AI — discovering and calling Talend at runtime. StackOne provides both.
How does Talend authentication work for AI agents?
Talend authentication for AI agents works through a StackOne Connect Session. Create one via the dashboard or the SDK — you get an auth link and ready-to-paste config for Claude Desktop, Cursor, and other MCP clients. Your user authenticates their own Talend account; StackOne handles token exchange, storage, and refresh. Credentials never reach the LLM, and each user is isolated via origin_owner_id.
Are Talend MCP tools vulnerable to prompt injection?
Yes — Talend MCP tools can be vulnerable to indirect prompt injection. Any tool that reads user-written content — documents, messages, tickets, records, or free-text fields — is a potential vector. StackOne Defender scans every tool response before it enters the agent's context — regex patterns in ~1ms, then a MiniLM classifier in ~4ms. 88.7% accuracy, CPU-only.
What is the context bloat of a Talend agent and how do I avoid it?
Context bloat happens when Talend tool schemas and API responses eat your Talend agent's memory, preventing it from reasoning effectively. A single Talend query can return a massive JSON response, and connecting multiple tools compounds the problem. Tools Discovery and Code Mode reduce context bloat — loading only relevant tools per query and keeping raw responses out of the agent's context.
Can I limit which actions my Talend agent can access?
Yes — you can limit which actions your Talend agent can access directly from the StackOne dashboard. Toggle actions on or off, or restrict them to specific accounts, with no code changes to your agent. Session tokens can be scoped to exact actions so if one leaks, exposure stays contained.
Can I create custom agent actions for my Talend MCP server?
Yes — you can create custom agent actions for your Talend MCP server using Connector Builder. It's an integration agent your coding assistant (Claude Code, Cursor, or Copilot) can invoke to research Talend's API, generate production-ready connector YAML, test against the live API, and validate before you ship.
When should I NOT use a Talend MCP server?
Skip a Talend MCP server if your integration is purely software-to-software — direct Talend API integration is simpler when no AI agent is involved. For deterministic, compliance-critical operations (financial transactions, regulatory reporting), direct API gives you predictable behavior without agent-driven decision-making. MCP shines when AI agents need to dynamically discover and call Talend actions at runtime.
What AI frameworks and AI clients does the StackOne Talend MCP server support?
The StackOne Talend MCP server supports both. MCP clients (paste-and-go apps): Claude Desktop, Claude Code, Cursor, VS Code, Goose. Agent frameworks (code SDKs you build with): OpenAI Agents SDK, Anthropic, Vercel AI, Google ADK, CrewAI, Pydantic AI, LangChain, LangGraph, Azure AI Foundry.

Put your AI agents to work

All the tools you need to build and scale AI agent integrations, with best-in-class connectivity, execution, and security.