OneLogin

Provides comprehensive access to OneLogin endpoints for identity, apps, authentication, and security via MCP clients.

javascript

GitHub Stars

javascript

Language

4 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "onelogin-onelogin-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@onelogin/onelogin-mcp"
      ],
      "env": {
        "ONELOGIN_URL": "https://mycompany.onelogin.com",
        "ONELOGIN_SERVER": "default",
        "ONELOGIN_CLIENT_ID": "your_client_id",
        "ONELOGIN_LEGACY_KEY": "<ONELOGIN_LEGACY_KEY>",
        "ONELOGIN_USE_PREPROD": "true",
        "ONELOGIN_CLIENT_SECRET": "your_client_secret"
      }
    }
  }
}

You can run a Model Context Protocol server for OneLogin to access every endpoint you need for identity, applications, authentication, security, and configuration. This MCP server lets Claude Desktop, OpenCode, and other MCP clients manage users, apps, roles, MFA, and more through a consistent, scriptable interface.

How to use

You interact with the OneLogin MCP server from your MCP client by issuing natural language requests. Ask to list users, assign roles, generate MFA tokens, manage SAML apps, or adjust security settings. The MCP client translates your request into the appropriate tool call, communicates with OneLogin via the MCP server, and returns structured results for you to review.

How to install

Prerequisites ensure your environment can authenticate with OneLogin and run MCP clients.

Step 1: Install or prepare your MCP client environment. You will run MCP commands through npx in most provided configurations.

Step 2: Configure the MCP server in your client config. You can use environment variables for credentialed access or store credentials in a setup file depending on your workflow.

Step 3: Start the MCP server integration in your client configuration. The following setup examples show the exact commands and environments to use.

Configuration and usage notes

Credential configuration supports two methods: using environment variables directly in your MCP client config or using a setup flow that stores credentials in a configuration file. Environment variables take precedence over stored configuration.

Environment variables you may set include the OneLogin URL, OAuth2 client ID, and client secret. You can also opt into preproduction environments, use a legacy key if needed, and assign a named server for logging.

If you work with multiple environments, you can define separate MCP server configurations for production and test, ensuring each environment points to the correct OneLogin subdomain and credentials.

Troubleshooting

If the MCP server does not appear in your MCP client, verify the JSON configuration syntax, ensure you reference the correct index path, and restart your client completely.

If you encounter a spawn bun ENOENT error, ensure Bun is installed and accessible, or provide the full Bun path in the startup config.

Authentication errors are usually due to incorrect credentials or misconfigured environment variables. Confirm the OneLogin URL, client ID, and client secret, and verify that the OAuth2 client has the necessary API permissions.

Project structure and development notes

The MCP server sources present a modular structure with a registry that discovers tools and a suite of modules for users, roles, apps, MFA, mappings, and analytics. Each module exports a tools array and a handlers object, enabling straightforward extension and customization.

Release and support

To publish new releases, follow semantic versioning and use your standard release workflow. Support channels include issue tracking and official API documentation.

Built by

VeilStrat

AI signals for GTM teams