Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
MCP server for OneLogin API - manage users, apps, roles, and authentication
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
ONELOGIN_URL, ONELOGIN_CLIENT_ID, ONELOGIN_CLIENT_SECRETValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"onelogin": {
"command": "npx",
"args": [
"-y",
"@onelogin/onelogin-mcp"
],
"env": {
"ONELOGIN_URL": "your-value",
"ONELOGIN_CLIENT_ID": "your-value",
"ONELOGIN_CLIENT_SECRET": "your-value"
}
}
}
}Run this in your terminal
claude mcp add onelogin --env ONELOGIN_URL=your-value --env ONELOGIN_CLIENT_ID=your-value --env ONELOGIN_CLIENT_SECRET=your-value -- npx -y @onelogin/onelogin-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"onelogin": {
"command": "npx",
"args": [
"-y",
"@onelogin/onelogin-mcp"
],
"env": {
"ONELOGIN_URL": "your-value",
"ONELOGIN_CLIENT_ID": "your-value",
"ONELOGIN_CLIENT_SECRET": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"onelogin": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@onelogin/onelogin-mcp"
],
"env": {
"ONELOGIN_URL": "your-value",
"ONELOGIN_CLIENT_ID": "your-value",
"ONELOGIN_CLIENT_SECRET": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account onelogin, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: ONELOGIN_URL, ONELOGIN_CLIENT_ID, ONELOGIN_CLIENT_SECRET
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.2.1) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, AvaHR
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Read hiring data and create inactive assessment and questionnaire drafts for human review.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A Model Context Protocol server providing comprehensive access to the OneLogin API. Enables Claude Desktop, OpenCode, and other MCP clients to manage users, apps, roles, authentication, and security settings.
This server provides tools covering a comprehensive set of supported OneLogin API endpoints:
All tools include comprehensive descriptions with warnings, best practices, and return data specifications.
https://github.com/user-attachments/assets/512abc44-6bb4-42e4-bb47-c0bc16f29beb
Configure credentials directly in Claude Desktop config - no separate setup required.
Edit the config file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonSingle environment:
{
"mcpServers": { "onelogin": { "command": "npx", "args": ["-y", "@onelogin/onelogin-mcp"], "env": { "ONELOGIN_URL": "https://mycompany.onelogin.com", "ONELOGIN_CLIENT_ID": "your_client_id", "ONELOGIN_CLIENT_SECRET": "your_client_secret" } } } }
Multiple environments (production/test separation):
{
"mcpServers": { "onelogin-prod": { "command": "npx", "args": ["-y", "@onelogin/onelogin-mcp"], "env": { "ONELOGIN_URL": "https://company.onelogin.com", "ONELOGIN_CLIENT_ID": "prod_client_id", "ONELOGIN_CLIENT_SECRET": "prod_secret" } }, "onelogin-test": { "command": "npx", "args": ["-y", "@onelogin/onelogin-mcp"], "env": { "ONELOGIN_URL": "https://company-test.onelogin.com", "ONELOGIN_CLIENT_ID": "test_client_id", "ONELOGIN_CLIENT_SECRET": "test_secret" } } } }
Optional environment variables:
ONELOGIN_USE_PREPROD: Set to "true" for preprod environmentsONELOGIN_LEGACY_KEY: Legacy API key (rarely needed)ONELOGIN_SERVER: Server name for logging (defaults to "default")Restart Claude Desktop completely after configuration.
For OpenCode users, add to ~/.config/opencode/mcp.json:
Single environment:
{
"mcpServers": { "onelogin": { "command": "npx", "args": ["-y", "@onelogin/onelogin-mcp"], "env": { "ONELOGIN_URL": "https://mycompany.onelogin.com", "ONELOGIN_CLIENT_ID": "your_client_id", "ONELOGIN_CLIENT_SECRET": "your_client_secret" } } } }
Multiple environments:
{
"mcpServers": { "onelogin-prod": { "command": "npx", "args": ["-y", "@onelogin/onelogin-mcp"], "env": { "ONELOGIN_URL": "https://company.onelogin.com", "ONELOGIN_CLIENT_ID": "prod_client_id", "ONELOGIN_CLIENT_SECRET": "prod_secret" } }, "onelogin-test": { "command": "npx", "args": ["-y", "@onelogin/onelogin-mcp"], "env": { "ONELOGIN_URL": "https://company-test.onelogin.com", "ONELOGIN_CLIENT_ID": "test_client_id", "ONELOGIN_CLIENT_SECRET": "test_secret" } } } }
Restart OpenCode after configuration.
Alternative method using a configuration file:
npm install -g @onelogin/onelogin-mcp
npx onelogin-mcp-setup
Enter your OneLogin server details when prompted:
https://mycompany.onelogin.com)Configuration is stored in ~/.config/onelogin-mcp/servers.json.
Edit the config file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonSingle environment:
{
"mcpServers": { "onelogin": { "command": "npx", "args": ["-y", "@onelogin/onelogin-mcp"] } } }
Multiple environments (reference servers by name):
{
"mcpServers": { "onelogin-prod": { "command": "npx", "args": ["-y", "@onelogin/onelogin-mcp"], "env": { "ONELOGIN_SERVER": "Production" } }, "onelogin-test": { "command": "npx", "args": ["-y", "@onelogin/onelogin-mcp"], "env": { "ONELOGIN_SERVER": "Test" } } } }
Use natural language to interact with OneLogin:
List all users with email ending in @example.com
Get details for user ID 12345 Create a user john.doe@example.com with firstname John, lastname Doe Assign roles [123, 456] to user 789 Generate MFA token for user 101112 List all SAML apps
Claude will select the appropriate tool, call the OneLogin API, and present results.
This server provides 156 tools organized into 7 major categories:
Identity & Access (59 tools)
Applications (17 tools)
Authentication (21 tools)
Security (40 tools)
Customization (6 tools)
Monitoring (9 tools)
Account Management (4 tools)
The server supports two configuration methods:
ONELOGIN_URL, ONELOGIN_CLIENT_ID, and ONELOGIN_CLIENT_SECRET in your MCP client config (see Installation above)npx onelogin-mcp-setup to store credentials in ~/.config/onelogin-mcp/servers.jsonEnvironment variables take precedence over the configuration file. See the Installation section above for complete configuration examples.
ONELOGIN_USE_PREPROD: Set to "true" for preprod environmentsONELOGIN_LEGACY_KEY: Legacy API key (rarely needed)ONELOGIN_SERVER: Server name for logging (defaults to "default") or to select a named server from servers.jsonAll tools return structured responses:
{
"success": true, "request_id": "68F194DE-0A0D05A2-55F8-0A0F6C42-01BB-62EAE-0008", "status": 200, "data": { // Tool-specific data } }
The request_id matches the x-request-id HTTP header for tracing in Datadog and OneLogin logs.
index.jsClaude cannot find the Bun runtime. Solutions:
# Verify Bun is installed
which bun
curl -fsSL https://bun.sh/install | bash
{ "command": "/Users/yourname/.bun/bin/bun", "args": ["run", "/path/to/index.js"] }
ONELOGIN_URL, ONELOGIN_CLIENT_ID, and ONELOGIN_CLIENT_SECRET in Claude Desktop config~/.config/onelogin-mcp/servers.jsonUsing environment variables: Each MCP server entry has its own credentials - verify you're talking to the correct server instance in Claude.
Using servers.json: Check the ONELOGIN_SERVER environment variable in Claude Desktop config matches a server name in servers.json.
onelogin-mcp/
├── index.js # MCP server entry point ├── setup.js # Interactive credential setup ├── lib/ │ ├── config.js # Credential management │ ├── onelogin-api.js # OAuth2 client with token caching │ └── tools/ │ ├── registry.js # Tool registry and dispatcher │ ├── users.js # User management (14 tools) │ ├── roles.js # Role management (13 tools) │ ├── privileges.js # Privilege management (11 tools) │ ├── apps.js # App management (15 tools) │ ├── mfa.js # MFA management (10 tools) │ ├── mappings.js # User mappings (15 tools) │ ├── smart-hooks.js # Smart Hooks (11 tools) │ ├── policies.js # Security policies (7 tools) │ ├── risk-rules.js # Risk rules (6 tools) │ ├── api-authorization.js # OAuth scopes (16 tools) │ ├── sessions.js # Session tokens (5 tools) │ ├── brands.js # Branding (6 tools) │ ├── connectors.js # App catalog (2 tools) │ ├── reports.js # Analytics (5 tools) │ ├── rate-limits.js # API throttling (2 tools) │ ├── saml.js # SAML assertions (2 tools) │ ├── invite-links.js # Password resets (2 tools) │ ├── oauth-tokens.js # OAuth tokens (2 tools) │ ├── events.js # Audit logs (2 tools) │ ├── groups.js # User groups (6 tools) │ └── accounts.js # Child accounts (4 tools) ├── package.json ├── CONTRIBUTING.md ├── PROGRESS.md └── README.md
See CONTRIBUTING.md for guidelines on adding new tools.
Key conventions:
tools array and handlers objectTo publish a new version to npm:
main branchv1.1.0)v prefix)package.json with the new version@onelogin/onelogin-mcpVersion Format: Use semantic versioning (MAJOR.MINOR.PATCH)
MAJOR: Breaking API changesMINOR: New features, backward compatiblePATCH: Bug fixes, backward compatibleManual Publishing (if needed):
MIT