ELMA365 MCP server

elma365-mcp

An MCP server for the ELMA365 low-code platform: BPM tasks, business processes and app items through an AI agent

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/elma365-mcp

Detects the agents on your machine, checks the risk and pins the version.

Other ways to install

Run in a terminal

claude mcp add --transport stdio --env 'ELMA365_DOMAIN=<ELMA365_DOMAIN value>' --env 'ELMA365_TOKEN=<your ELMA365_TOKEN>' elma365 -- npx -y @theyahia/elma365-mcp

Or add to the file .mcp.json, in the project

{
  "mcpServers": {
    "elma365": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/elma365-mcp"
      ],
      "env": {
        "ELMA365_DOMAIN": "<ELMA365_DOMAIN value>",
        "ELMA365_TOKEN": "<your ELMA365_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

ELMA365_DOMAINrequired
ELMA365_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Install in Cursor

The button opens the agent and offers to add the server. If nothing happens, copy the config below.

Add to the file ~/.cursor/mcp.json, for all projects

{
  "mcpServers": {
    "elma365": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/elma365-mcp"
      ],
      "env": {
        "ELMA365_DOMAIN": "<ELMA365_DOMAIN value>",
        "ELMA365_TOKEN": "<your ELMA365_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.

Keys and settings

ELMA365_DOMAINrequired
ELMA365_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Install in VS Code

The button opens the agent and offers to add the server. If nothing happens, copy the config below.

Run in a terminal

code --add-mcp '{"name":"elma365","type":"stdio","command":"npx","args":["-y","@theyahia/elma365-mcp"],"env":{"ELMA365_DOMAIN":"<ELMA365_DOMAIN value>","ELMA365_TOKEN":"<your ELMA365_TOKEN>"}}'

Or add to the file .vscode/mcp.json, in the project

{
  "servers": {
    "elma365": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/elma365-mcp"
      ],
      "env": {
        "ELMA365_DOMAIN": "<ELMA365_DOMAIN value>",
        "ELMA365_TOKEN": "<your ELMA365_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the servers key.

Keys and settings

ELMA365_DOMAINrequired
ELMA365_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

codex mcp add elma365 --env 'ELMA365_DOMAIN=<ELMA365_DOMAIN value>' --env 'ELMA365_TOKEN=<your ELMA365_TOKEN>' -- npx -y @theyahia/elma365-mcp

Or add to the file ~/.codex/config.toml, for all projects

[mcp_servers.elma365]
command = "npx"
args = ["-y", "@theyahia/elma365-mcp"]
env = { ELMA365_DOMAIN = "<ELMA365_DOMAIN value>", ELMA365_TOKEN = "<your ELMA365_TOKEN>" }

If the file already exists, append the block to the end.

Keys and settings

ELMA365_DOMAINrequired
ELMA365_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.gemini/settings.json, for all projects

{
  "mcpServers": {
    "elma365": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/elma365-mcp"
      ],
      "env": {
        "ELMA365_DOMAIN": "<ELMA365_DOMAIN value>",
        "ELMA365_TOKEN": "<your ELMA365_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

ELMA365_DOMAINrequired
ELMA365_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/devin/mcp_config.json, for all projects

{
  "mcpServers": {
    "elma365": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/elma365-mcp"
      ],
      "env": {
        "ELMA365_DOMAIN": "<ELMA365_DOMAIN value>",
        "ELMA365_TOKEN": "<your ELMA365_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.

Keys and settings

ELMA365_DOMAINrequired
ELMA365_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Formerly Windsurf.

Add to the file cline_mcp_settings.json, for all projects

{
  "mcpServers": {
    "elma365": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/elma365-mcp"
      ],
      "env": {
        "ELMA365_DOMAIN": "<ELMA365_DOMAIN value>",
        "ELMA365_TOKEN": "<your ELMA365_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.

Keys and settings

ELMA365_DOMAINrequired
ELMA365_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .roo/mcp.json, in the project

{
  "mcpServers": {
    "elma365": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/elma365-mcp"
      ],
      "env": {
        "ELMA365_DOMAIN": "<ELMA365_DOMAIN value>",
        "ELMA365_TOKEN": "<your ELMA365_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

ELMA365_DOMAINrequired
ELMA365_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

A fork of Roo Code, same .roo folders.

Add to the file opencode.json, in the project

{
  "mcp": {
    "elma365": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@theyahia/elma365-mcp"
      ],
      "environment": {
        "ELMA365_DOMAIN": "<ELMA365_DOMAIN value>",
        "ELMA365_TOKEN": "<your ELMA365_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcp key.

Keys and settings

ELMA365_DOMAINrequired
ELMA365_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/zed/settings.json, for all projects

{
  "context_servers": {
    "elma365": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/elma365-mcp"
      ],
      "env": {
        "ELMA365_DOMAIN": "<ELMA365_DOMAIN value>",
        "ELMA365_TOKEN": "<your ELMA365_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the context_servers key.

Keys and settings

ELMA365_DOMAINrequired
ELMA365_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .codeassistant/mcp.json, in the project

{
  "mcpServers": {
    "elma365": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/elma365-mcp"
      ],
      "env": {
        "ELMA365_DOMAIN": "<ELMA365_DOMAIN value>",
        "ELMA365_TOKEN": "<your ELMA365_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

ELMA365_DOMAINrequired
ELMA365_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

You will need: Node.js

Checked against the repository on Sep 25, 2026, commit 1fff44f.

Text for your agent

Set the ELMA365_DOMAIN (company subdomain) and ELMA365_TOKEN (Bearer token) variables, then connect the server with claude mcp add elma365 -e ELMA365_DOMAIN=mycompany -e ELMA365_TOKEN=your-token -- npx -y @theyahia/elma365-mcp.

Other ways from the author

claude mcp add elma365 -e ELMA365_DOMAIN=mycompany -e ELMA365_TOKEN=your-token -- npx -y @theyahia/elma365-mcp

Command from the README for Claude Code.

This is third-party code. Review the repository files before installing.

What it does

The server talks to the public ELMA365 API using the company domain and a Bearer token, giving an agent nine tools: listing and creating app items by namespace and code, listing tasks and business processes, starting a process with parameters, listing users and looking one up by ID, and reading or adding comments on an item. Claude Code gets two ready skills: show my tasks and start a process by code. The server runs over stdio via npx or as Streamable HTTP on its own port, with a Smithery deployment template included.

Who it is for. For employees and admins at companies running ELMA365 who want to close tasks and start processes through an agent.

Good fit when

You want to see your BPM tasks and close them from a chat with an agent
You want to start a business process by code with ready parameters
You want to create an ELMA365 app item or add a comment without opening the web interface

Not a fit when

Your company does not use ELMA365
You need low-code app development or platform configuration rather than working with data through the API

Example request

Show my ELMA365 tasks for today and start the approval_flow process

Limitations

The project has a single author and is part of the author's larger WWmcp series; the README does not call out separate versioned npm releases for this package specifically. It needs the company's ELMA365 domain and an API Bearer token. The README does not describe ELMA365 API limits such as rate limits or token permissions.

How to disable. Remove the elma365 server from your MCP client config, for example with claude mcp remove elma365 in Claude Code.

MCP

Transport: stdio, http
Authentication: API key

Environment variables
Environment variables
ELMA365_DOMAIN required	The company's ELMA365 subdomain or full domain.
ELMA365_TOKEN required, secret	ELMA365 API Bearer token.

Security check

Can create app items, start business processes and add comments
The API token grants access to everything its permissions allow

README in short

The Russian README explains the server's purpose and gives configs for Claude Desktop, Claude Code, VS Code, Cursor, Streamable HTTP and Smithery. A table of nine tools and two Claude Code skills comes with Russian example phrases. It separately covers domain and Bearer token auth and the API base URL. Part of the same author's WWmcp series.

FAQ

Where do I get ELMA365_TOKEN?

The README does not spell out the steps; the token comes from the company's API settings on the ELMA365 platform.

Can processes be started with parameters?

Yes, the start_process tool accepts a process code and a JSON object of parameters.

n8n-MCP

Editors’ pick

An MCP server with n8n node and template knowledge: the agent picks nodes, validates configs and, with API access, creates workflows in your n8n

MCP serverHigh risk23K

Zapier MCP

Official

Zapier's official MCP plugin: the agent gets actions across thousands of apps through your Zapier account

PluginHigh risk421

Awesome Claude Skills by Composio

Awesome Claude Skills

A curated list of Claude skills and plugins, plus Composio's own automation skills for 78 SaaS apps

SkillHigh risk75.8K

CLI-Anything

A plugin and CLI catalog for agents: generates command-line interfaces for GUI apps like GIMP and Blender and installs ready ones via CLI-Hub

PluginHigh risk50.9K

Install

What it does

Good fit when

Not a fit when

Example request

Limitations

MCP

Security check

README in short

FAQ

Related

n8n-MCP

Zapier MCP

Awesome Claude Skills by Composio

CLI-Anything