- Home
- MCP servers
- Admina
Admina
- javascript
4
GitHub Stars
javascript
Language
4 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"moneyforward-i-admina-mcp-server": {
"command": "npx",
"args": [
"-y",
"@moneyforward_i/admina-mcp-server"
],
"env": {
"ADMINA_API_KEY": "<API Key>",
"ADMINA_ORGANIZATION_ID": "<Organization Id>"
}
}
}
}You run the Admina MCP Server to expose Admina APIs as MCP endpoints that your MCP clients can consume. It centralizes access to devices, identities, services, and accounts, enabling you to integrate Admina data into your MCP workflow securely with your organization’s API key.
How to use
Use an MCP client to connect to the Admina MCP Server. The server provides endpoints that let you list devices, identities, organization services with account previews, service accounts, and all SaaS accounts for a person. You don’t need to manage the underlying API calls yourself; the MCP server abstracts those calls and returns structured results you can use in your integration.
How to install
Prerequisites you need on your machine before starting are Node.js installed on your system. You also need access to an Admina organization and an API key to authorize requests.
Install and run the MCP server locally using the provided command in your environment configuration. The server is intended to be run via a package runner, which will start the MCP server process and expose the MCP endpoints for your client to consume.
Configuration details
Configure the MCP client to connect to the Admina MCP Server using the following settings. You will supply your organization identifier and API key as environment variables when starting the server.
Tools and APIs exposed
The Admina MCP Server provides a set of endpoints to fetch data from Admina services. The key data operations include:
Additional notes
Environment variables shown below are required to run the server. Include these in your runtime environment where you start the MCP server.
Security and access
Protect your API key and organization ID. Treat them as sensitive credentials and supply them only to trusted environments. Rotate keys periodically and restrict access to MCP clients that require these endpoints.
Available tools
get_devices
Return a list of devices available in the organization.
get_identities
Return a list of identities within the organization.
get_services
Return a list of services integrations that belong to the organization along with a preview of accounts.
get_service_accounts
Return a list of accounts for a specific service.
get_people_accounts
Return a list of all SaaS accounts belonging to a person.