Security & governancePublic source

Identity MCP Server

Policy-enforced identity control plane for ADK-Rust Enterprise agents. Look up users, verify identity, check MFA, review entitlements, request access changes, and manage lifecycle events — all audit-logged with actor…

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Actor context on every call — who is asking, from which agent, for which ticket, for what purpose.

Audit-logged — every identity lookup is recorded (PII access tracking).

Minimized PII — returns only what's needed, never secrets or recovery codes.

Approval-gated writes — access changes go through approval workflow.

Break-glass revoke — emergency revocation with mandatory post-review.

Pluggable — in-memory store now, Okta/Azure AD/Google Workspace via feature flags.

Architecture

How Identity MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

Identity MCP Server

Validates the request and owns 8 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

Identity MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask Identity MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

8 named tools

lookup_user

Look up a user by email, username, full name, or employee ID

read only

list_user_groups

List groups/roles a user belongs to

read only

check_mfa

Check MFA enrollment status, methods, and last verification

read only

verify_user

Verify user exists and is active

read only

list_entitlements

List all entitlements for a user with source, grant type, risk level

read only

request_access

Request access grant or revoke — goes through approval workflow

internal write

emergency_revoke

Emergency access revocation — immediate effect, triggers post-action review

destructive

lifecycle_task

Create onboarding/offboarding/transfer/role-change lifecycle task

internal write

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

5 read only2 internal write1 destructive

Audit-logged — every identity lookup is recorded (PII access tracking).
Minimized PII — returns only what's needed, never secrets or recovery codes.
Approval-gated writes — access changes go through approval workflow.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

Resources

Long-running tasks

ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-identity

ADK-Rust connection shape

let toolset = McpToolset::from_stdio(
    "mcp-identity",
    ["mcp-identity"],
).await?;

let agent = LlmAgentBuilder::new("agent")
    .tools(toolset.tools().await?)
    .build()?;

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md CHANGELOG ↗CHANGELOG.md Architecture ↗docs/architecture.svg Issues and support ↗github.com issues

Keep exploring