# Reported issues for onelogin-mcp

Pod holds 19 of 25 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to [onelogin-mcp](/mcp/onelogin-mcp).

## Most discussed

### update users group not completed

i asked copilot to use the ol mcp server to update a particular users group and it failed with

● I notice the OneLogin API update_user function doesn't seem to accept group_id as a parameter based on the available parameters. The user with OneLogin Protect
   enrolled (marc.maguire44@gmail.com (mailto:marc.maguire44@gmail.com), ID: 255862336) is currently in group 522724, and there is a group "OneLogin_Protect_Users"
   (ID: 522746) that exists. However, the API tools available don't provide a 

[Read the thread](https://github.com/onelogin/onelogin-mcp/issues/3) · 2025-12-05 · closed · 2 comments

### update_app tool bug - not able to configure "configuration" on apps via tools

The onelogin-update_app tool doesn't support updating the configuration object (login_url, redirect_uri, etc.). These OIDC configuration parameters are not exposed in the available API tools. You'll need to
   configure the login URL and redirect URI through the OneLogin admin UI for this OIDC app.

also does not work when trying to set configuration for example (login_url) via create app tool

[Read the thread](https://github.com/onelogin/onelogin-mcp/issues/35) · 2026-03-10 · closed · 1 comment

### assign role to user (POST on /2/roles/id/users) return 401

If you try to use Claude to assign a role to a user it will return a 401 even though you have proper creds.

  "data": {
    "message": "Unauthorized",
    "name": "UnauthorizedError",
    "statusCode": 401

[Read the thread](https://github.com/onelogin/onelogin-mcp/issues/34) · 2026-03-10 · closed · external user · 1 comment

### Privilege Bugs

Create privilege and update existing privilege not working.

Delete an existing privilege is working ok. The create and update priv was working ok before

[Read the thread](https://github.com/onelogin/onelogin-mcp/issues/33) · 2026-03-10 · closed · 1 comment

### Update Readme with embedded Demo recording

Please update the readme to include a Demo recording of Claude Desktop and OneLogin MCP server in action.

[Read the thread](https://github.com/onelogin/onelogin-mcp/issues/32) · 2026-03-10 · closed · 1 comment

### groups.js - wrong api endpoint

groups tool is incorrectly trying /api/2/groups which is not available yet. Please correct to /api/1/groups

[Read the thread](https://github.com/onelogin/onelogin-mcp/issues/30) · 2026-02-10 · closed · 1 comment

### privileges.js - assign users or roles to privilege not working

creating privileges works ok but not possible to assign the privilege to a user or a group. assign_role_to_privilege , assignUsersToPrivilege, removeUserFromPrivilege, removeRoleFromPrivilege functions not correct

also not possible to update previously created privilege.
delete privilege works ok

[Read the thread](https://github.com/onelogin/onelogin-mcp/issues/16) · 2026-02-05 · closed · 1 comment

### mappings tool issue - custom attributes cannot be used as condition sources

Unfortunately, as we discovered earlier, custom attributes cannot be used as condition sources in OneLogin
   mappings. The API only supports standard user fields like email, department, etc. as condition sources.

   The mapping is currently using department field which is working. If we try to change it to use the custom
   field mcp_test, it will fail with "Invalid condition source" error.

[Read the thread](https://github.com/onelogin/onelogin-mcp/issues/15) · 2026-02-05 · closed · 1 comment

## Most recent

### add support for new V2 policies API

would be great to provide new tools to manage user and app policies via the MCP server

[Read the thread](https://github.com/onelogin/onelogin-mcp/issues/61) · 2026-08-25 · closed · 0 comments

### JSON Schema validation error: array type parameters missing items definition

## Summary

Several tool definitions in the MCP server declare parameters with `type: 'array'` but are missing the required `items` schema property. This causes MCP clients to reject the tool with the error:

`
Failed to validate tool mcp_onelogin-mcp_create_mapping: Error: tool parameters array type must have items
`

## Affected Tools and Parameters

| File | Tool | Parameter |
|------|------|-----------|
| lib/tools/mappings.js | create_mapping | actions |
| lib/tools/mappings.js | create_map

[Read the thread](https://github.com/onelogin/onelogin-mcp/issues/58) · 2026-06-23 · closed · external user · 0 comments

### set_role_apps wraps body as `{app_id_array: [...]}` but `/api/2/roles/{id}/apps` expects a bare array

## Summary

The MCP tool `set_role_apps` sends a `PUT /api/2/roles/{role_id}/apps` request with a body shaped like `{ "app_id_array": [...] }`, but the OneLogin v2 API expects the body to be a bare JSON array. Every call fails with HTTP 400 *"Expected array in request"*.

## Reproduction

```
mcp__onelogin-shadow__set_role_apps(role_id=437749, app_ids=[1496311, 1496313])
```

→
```json
{
  "status": 400,
  "request_id": "69F21CB3-0A0D0115-0CC2-0A0FBDCD-24E3-7D50-002F",
  "data": {
    "status": 

[Read the thread](https://github.com/onelogin/onelogin-mcp/issues/54) · 2026-04-29 · open · outside contributor · 0 comments

### list_mappings advertises `page` and `limit` params that the OneLogin API rejects

## Summary

The MCP tool `list_mappings` declares `page` and `limit` as input parameters, but the upstream OneLogin API (`GET /api/2/mappings`) rejects both with HTTP 422. This means the schema advertised to MCP clients (and to LLMs that introspect it) is broader than what the backend actually honors — every call that uses these "documented" params fails.

## Reproduction

Calling `list_mappings` with either `page` or `limit` set:

**`page: 2`** →
```json
{
  "status": 422,
  "request_id": "69F2

[Read the thread](https://github.com/onelogin/onelogin-mcp/issues/53) · 2026-04-29 · open · outside contributor · 0 comments

### client_app tools bugs

list_client_apps: listClientApps,
  get_client_app: getClientApp,
  create_client_app: createClientApp,
  update_client_app: updateClientApp,
  delete_client_app: deleteClientApp,

Summary of client app tools — all 4 are broken in your environment:

┌─────────────────────┬────────┐
│ Tool                │ Status │
├─────────────────────┼────────┤
│ list_client_apps    │ ❌ 404 │
├─────────────────────┼────────┤
│ get_client_app      │ ❌ 400 │
├─────────────────────┼────────┤
│ create_client_app 

[Read the thread](https://github.com/onelogin/onelogin-mcp/issues/50) · 2026-04-16 · closed · 0 comments

### add_authorization_scopes bug

The scope is now available for client applications to request when obtaining access tokens from this authorization server. Note: I had to recreate the authorization server because the add_authorization_scopes endpoint encountered a validation error, which appears to be an issue with the OneLogin API itself.

only possible to add scopes to an auth server while creating the auth server not possible to add additional scopes to an existing auth server via add_authorization_scopes

delete_authorizati

[Read the thread](https://github.com/onelogin/onelogin-mcp/issues/49) · 2026-04-16 · closed · 0 comments

### remove_authorized_clients & add_authorized_clients

remove_authorized_clients & add_authorized_clients tools for Authorization server not working.

other CRUD actions on Authorization servers work ok just not CRUD on the associated oidc clients

[Read the thread](https://github.com/onelogin/onelogin-mcp/issues/47) · 2026-04-15 · closed · 0 comments

### api-authorization tools bug

not able to create or update api authorization servers. 

existing authroization servers created via UI /API can be deleted ok via mcp

[Read the thread](https://github.com/onelogin/onelogin-mcp/issues/45) · 2026-04-14 · closed · 0 comments

### Groups Tools Update

Please enable the four tools (create, update, delete, get_group_users) now that  /api/2/groups is deployed.

[Read the thread](https://github.com/onelogin/onelogin-mcp/issues/41) · 2026-03-13 · closed · 0 comments

### api-authorization.js bugs

create new authorization server fails.
list existing one works ok and delete existing one also.

update existing one works ok for name , description etc. but not for adding scopes or clients or claims

[Read the thread](https://github.com/onelogin/onelogin-mcp/issues/20) · 2026-02-05 · closed · 0 comments

### invite-links.js bugs

incorrect API endpoints defined in the functions for generate and send invite.

should be 

https://<subdomain>/api/1/invites
/send_invite_link

https://<subdomain>/api/1/invites/
get_invite_link

[Read the thread](https://github.com/onelogin/onelogin-mcp/issues/19) · 2026-02-05 · closed · 0 comments

The remaining reports are on [the project's issue tracker](https://github.com/onelogin/onelogin-mcp/issues).