What can you do with this server?

The Admina MCP Server provides comprehensive IT asset and identity management through the Admina API, enabling management of devices, identities, and SaaS accounts. Organization Management: Retrieve organization details including name, status, and system language. Device Management: List devices with advanced filtering (type, subtype, status, custom fields, date ranges, assigned people) and text search; create devices with asset number, model, and subtype; update device information and specifications; manage device assignments to people, status, and location; track device lifecycle from procurement to decommission. Custom Field Management: Retrieve, create, update, and delete custom field definitions for devices supporting text, number, date, and dropdown types. Identity Management: List organizational identities with filtering by status (active, retired, on leave), department, and type; search by email or name. Service & Account Management: List integrated SaaS services with account previews; retrieve accounts for specific services with filtering by roles, 2FA status, licenses, activity, and alerts; get all SaaS accounts belonging to a specific person. Key Features: Cursor-based pagination for large datasets, advanced filtering and sorting, multi-service account visibility. Configuration: Requires organization ID and API key for authentication.

How do I use Admina MCP Server?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Admina MCP Server show me all devices in our organization" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

admina-mcp-server

MCP server for the Admina API.

Tools and API Documentation

Organization

get_organization_info: Get information about the organization including name, unique name, status, and system language.

Devices

get_devices: Return a list of devices with advanced search and filtering. Get Devices API
create_device: Create a new device for an organization. Requires device type (subtype), asset number, and model name.
update_device: Update an existing device's information including preset fields and custom fields.
update_device_meta: Update device's meta information including assignment info (peopleId, status, dates) and location.

Device Custom Fields

get_device_custom_fields: Get all custom fields configured for an organization's devices.
create_device_custom_field: Create a new custom field for organization devices.
update_device_custom_field: Update an existing device custom field configuration.
delete_device_custom_field: Delete a device custom field configuration.

Identities

get_identities: Return a list of identities. Get Identities API
create_identity: Create a new identity. Requires employeeStatus, employeeType, firstName, lastName.
get_identity: Get a single identity by ID. Optionally expand with customFieldsMetadata.
update_identity: Update an existing identity by ID.
delete_identity: Delete an identity by ID.
get_identity_field_configuration: Get identity field configuration of an organization including preset field settings, field order, and source of truth metadata.
get_identity_config: Get configuration for identity fields of a specific identity.
check_identity_management_type: Determine the management type for an identity based on email or identityId.
get_identities_stats: Get identities statistics including management type counts, HR master integration info, and domain lists.
merge_identities: Merge identities in batch (supports up to 50 merge operations per request).
unmerge_identities: Unmerge previously merged people or identity entities (supports up to 50 unmerge operations per request).
bulk_update_identities: Bulk update multiple identities in a single request. Provide a list of identity IDs (1-50) and a set of field updates to apply to all of them.
get_identity_history: Get the change history of a specific identity. Returns a paginated list of field-level changes, action types, sources, and actors.
archive_identity: Toggle the archive flag for an identity by ID. Returns the updated identity.
unregister_identity: Toggle the unregistered management type for an identity by ID. Returns the updated identity.

Services & Accounts

get_services: Return a list of services integrations that belongs to organization along with a preview of accounts. Organization Services API
get_service_accounts: Return a list of accounts for a specific service. Get Service Accounts API
get_people_accounts: Return a list of all SaaS accounts belonging to a person. Get People Accounts API

Configuration

To configure the admina-mcp-server, you will need the organizationId and an API key. For more details on obtaining your API key, please refer to the Getting Started Guide.

MCP Client Configuration

To configure this MCP server, add the following configuration to your mcp settings.

{
  "mcpServers": {
    "admina-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@moneyforward_i/admina-mcp-server"
      ],
      "env": {
        "ADMINA_ORGANIZATION_ID": <Organization Id>,
        "ADMINA_API_KEY": <API Key>
      }
    }
  }
}

For local set up, run yarn build:dev and set the path to the root dir.

Releasing

Preparing a release

Bump up a package version of package.json. A Git commit will be created automatically.

yarn version --new-version <new version>

Push the change to the main branch as usual.

Creating a release

Create a new release in GitHub by clicking on "Releases" and then "Draft a new release"
Set the Tag version to a new tag
Set the Target as main.
Set the Release title to the tag you created, vX.Y.Z
Click "Publish release" to save and publish your release.
GitHub Actions workflow will be triggered by publishing a new release and the package will be released.