The admina-mcp-server exposes a comprehensive set of MCP endpoints designed to integrate with the Admina API. It includes tooling for managing organizations, devices, device custom fields, identities, and service accounts, enabling you to query, create, update, and delete entities as needed. Typical usage involves configuring the MCP client with your organization ID and API key, then using the server’s endpoints to programmatically manage devices, identities, and services within your Admina workspace. The server supports advanced device operations (creation, updates to device data and metadata, and custom fields) as well as identity management (creation, updates, merges) and organization-level information retrieval. You can also fetch service accounts and organization service previews to understand integrations at a glance.

Prerequisites:

• Node.js and npm (or yarn) installed on your machine.
• Access to the Admina API with a valid organization ID and API key.
• Optional: Docker if you prefer containerized runs.

Install and run locally:

1. Clone the repository or set up the MCP server project: git clone <repository-url> cd admina-mcp-server

2. Install dependencies: npm install

   or if you prefer yarn:

   yarn install

3. Build for development (as noted in the README): yarn build:dev

   Ensure the path to the root directory is correct if you run from a subfolder

4. Run the MCP server locally (adjust environment variables as needed): export ADMINA_ORGANIZATION_ID=<your-org-id> export ADMINA_API_KEY=<your-api-key> node path/to/server.js

   If using npx as in the MCP config, you can rely on the configured command instead

5. If you want to run via Docker, build or pull the image and run with the required env vars, mapping ports as needed.

6. Verify installation by making API calls to the available endpoints (organizations, devices, identities, services, etc.).

Environment variables: ADMINA_ORGANIZATION_ID and ADMINA_API_KEY are required for authentication. Ensure these are kept secure and not checked into version control. The server exposes operations for devices (create, update, meta updates, and custom fields), identities (create, update, merge, and stats), and service accounts, among others. If you encounter API rate limits or authorization errors, verify that your API key corresponds to the correct organization and that the key has the necessary scopes. For local development, yarn build:dev prepares the development build and helps with debugging. When upgrading to a new version, bump the package version and follow the release steps described in the README to trigger CI/CD workflows.