Lokalise icon

CONNECT APP

Build with Lokalise

A Localization and Translation Software Tool.

Language Tools

  • OAuth

MCP

Give your agent Lokalise tools

Every Lokalise action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Lokalise account for each tool call — you store no tokens.

// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
  new URL("https://remote.mcp.pipedream.net/v3"),
  {
    requestInit: {
      headers: {
        Authorization: `Bearer ${accessToken}`,
        "x-pd-project-id": "{project_id}",
        "x-pd-environment": "production",
        "x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
        "x-pd-app-slug": "lokalise",
      },
    },
  },
)

const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)

const { tools } = await mcp.listTools()

// e.g. run Create Project:
const result = await mcp.callTool({
  name: "lokalise-create-project",
  arguments: {
    name: "Name",
    description: "Description",
  },
})

API PROXY

Call the Lokalise API directly

For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Lokalise API with the connected user's credentials attached. You store no tokens and write no refresh logic.

const resp = await pd.proxy.get({
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  accountId: "apn_xxxxxxx",
  url: "https://api.lokalise.com/api2/projects",
})

// Any allowed Lokalise endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.

SDK

Run Lokalise actions from your backend

Connect a user's Lokalise account once, then run Create Project on their behalf from your own code — TypeScript, Python, or plain HTTP.

import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const result = await pd.actions.run({
  id: "lokalise-create-project",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    lokalise: { authProvisionId: "apn_xxxxxxx" },
    name: "Name",
    description: "Description",
  },
})

REFERENCE

App details

Reference metadata for the Lokalise connector in the Pipedream registry.

App slug
lokalise
Authentication
OAuth
Categories
Language Tools
Actions
5
Triggers
3
API proxy
Available

OAuth scopes

These are the scopes Pipedream's managed Lokalise OAuth client requests when one of your users connects an account. Supply your own OAuth client to request a different set.

  • read_projects
  • write_projects
  • read_team_users
  • read_files
  • write_files
  • read_languages
  • write_languages
  • read_webhooks
  • write_webhooks