Alphakey Mcp Server

io.github.seyoung230Published by GitHub account seyoung230v2.1.2Updated Oct 24, 2026

AlphaKey IDaaS MCP Server — Manage SSO, MFA, users, apps, and security policies through AI IDE

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

A local MCP server that connects an AI IDE to an AlphaKey IDaaS tenant so an assistant can manage SSO, MFA, users, apps and security policies.

What you can do
Connect an AI IDE to an AlphaKey identity-as-a-service tenant through its OpenAPI endpoint, using a tenant URL and an authentication token supplied as environment variables. Work with identity and access management objects such as single sign-on configuration, multi-factor authentication, user accounts, applications and security policies. The manifest lists no individual tools, so the exact operations available are not documented in the supplied material.
When to use it
Useful when an administrator wants to inspect or change AlphaKey SSO, MFA, user, application or security-policy settings from an AI IDE instead of the AlphaKey console.
Requirements
Runs locally as a stdio process, launched with uvx from the alphakey-mcp-server PyPI package, so a Python/uv runtime is needed. Requires the ALPHAKEY_BASE_URL environment variable with the tenant URL and the ALPHAKEY_TOKEN secret environment variable with an AlphaKey OpenAPI authentication token. Network access to the tenant is implied. Desktop only.
Before you install
The server holds an AlphaKey OpenAPI authentication token in ALPHAKEY_TOKEN, which grants access to the tenant's identity and access management data; keep it out of logs and shared configuration. Because it manages SSO, MFA, users, apps and security policies, assistant actions may create, change or remove accounts and access settings, so review changes before applying them. The manifest declares no authentication of its own.

Installation

In SourceWeft

  1. Open Alphakey Mcp Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v2.1.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.