Skip to main content
Glama
moneyforward-i

Admina MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ADMINA_API_KEYYesYour Admina API key. For more details on obtaining your API key, please refer to the Getting Started Guide at https://docs.itmc.i.moneyforward.com/reference/getting-started-1#step-1-obtain-your-api-key
ADMINA_ORGANIZATION_IDYesYour Admina organization ID

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_organization_info

Get information about the organization including name, unique name, status, system language, etc.

get_devices

Get a list of devices for an organization using advanced search and filtering.

Key Features

  • Combine query parameters (pagination, sorting) with body parameters (filtering)

  • Support for text search, field-specific filters, and complex queries

  • Pagination with cursor-based navigation

Example Usage

Find first 5 devices for user with email "someone@gmail.com":

  • Query: limit=5

  • Body: {"searchTerm": "someone@gmail.com", "searchFields": ["people.primaryEmail"]}

Pro Tips

  • 1: Always make sure understand the definition of the fields (preset and custom fields) before using them.

  • 2: If user search devices by category: pc, phone or other, please use body.type to filter devices by category.

  • 3: Always to understand what are current sub types of the devices. If the user search information relate to sub types, Please use body.filters.["preset.subtype"] to filter devices by sub types.

  • 4: We don't really need to use searchFields parameter to the search results in all fields, only use it when the user search information relate to specific fields.

  • 5: If user want to filter devices by status, please use body.filters.["preset.status"].eq to filter devices by status.

  • 5.1: Unassigned devices status should be "in_stock" or "decommissioned".

  • 6: If user want to filter devices by preset fields or custom fields, please check the field.kind first, we only support date, number, dropdown kind of fields.

  • 6.1: If the field.kind is date, please use body.filters.["preset.field_name"].minDate or body.filters.["custom.attributeCode"].minDate and body.filters.["preset.field_name"].maxDate or body.filters.["custom.attributeCode"].maxDate to filter devices by date range.

  • 6.2: If the field.kind is number, please use body.filters.["preset.field_name"].minNumber or body.filters.["custom.attributeCode"].minNumber and body.filters.["preset.field_name"].maxNumber or body.filters.["custom.attributeCode"].maxNumber to filter devices by number range.

  • 6.3: If the preset field field.kind is dropdown, please use body.filters.["preset.field_name"].eq or body.filters.["custom.attributeCode"].eq to filter devices by dropdown value.

  • 7: Combine multiple filters examples: {"preset.status":{"eq":"active"},"preset.subtype":{"eq":"desktop_pc"},"custom.custom_xxx":{"eq":"1"},"custom.dt_13":{"minDate":"2025-12-23","maxDate":"2025-12-25"},"custom.drp_4":{"eq":"1"}}

create_device

Create a new device for an organization. Requires device type (subtype), asset number, and model name. Can include optional preset fields and custom fields.

update_device

Update an existing device's information. Can update preset fields, custom fields, and device properties. Note: fields.preset.asset_number, fields.preset.subtype, fields.preset.model_name are always required.

update_device_meta

Update device's meta information including assignment info (peopleId, status, dates) and location. Use this to assign/unassign devices to people. When unassigned, status should be 'in_stock' or 'decommissioned'. When assigned without status, defaults to 'active'.

get_device_custom_fields

Get all custom fields configured for an organization's devices. Returns field definitions, types (text, date, number, dropdown), and configurations.

create_device_custom_field

Create a new custom field for organization devices. Defines a new field that can be used across all devices in the organization.

update_device_custom_field

Update an existing device custom field configuration. Can modify field name, code, visibility for device types, and dropdown configuration.

delete_device_custom_field

Delete a device custom field configuration. Removes a custom field definition from the organization.

get_identities

Return a list of identities. Can be filtered by the status, department and type. Can also search by the email or name by keyword

get_services

Return a list of services, along with the preview of the accounts. Can be searched by the service name by keyword

get_service_accounts

Return a list of accounts for a specific service. The serviceId can be obtained from the get_services tool. Can be searched by email/name of the account by keyword

get_people_accounts

Return a list of SaaS accounts belonging to a person. The peopleId can be obtained from the get_identities tool. Can be filtered by role, two-factor authentication, and searched by service name or workspace name

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/moneyforward-i/admina-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server