Skip to main content
Glama
pbozzay

level-mcp

by pbozzay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LEVEL_API_KEYNoValue sent in the Authorization header. Required for authenticated operations.
LEVEL_API_BASE_URLNoAlternate API origin for a proxy or test server. Default: https://api.level.io
LEVEL_API_TIMEOUT_MSNoPer-request timeout in milliseconds. Default: 30000

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
listAlertsB

List alerts. Returns a list of your alerts. Level API endpoint: GET /v2/alerts

showAlertA

Show alert. Retrieves the details of an existing alert. Level API endpoint: GET /v2/alerts/{id}

resolveAlertA

Resolve alert. Resolves an active alert. If the alert is already resolved, this is a no-op and returns the alert as-is. Level API endpoint: POST /v2/alerts/{id}/resolve

showAutomationRunB

Show automation run. Retrieves the status of an existing automation run. Level API endpoint: GET /v2/automation-runs/{id}

listAutomationWebhooksA

List automation webhooks. Returns webhook trigger URLs and accepted parameters for non-archived automations. Level API endpoint: GET /v2/automations/webhooks

listAutomationsA

List automations. Returns a list of non-archived automations. Level API endpoint: GET /v2/automations

listCustomFieldValuesA

List custom field values. Returns a list of custom field values for the organization, groups, or devices. Level API endpoint: GET /v2/custom-field-values

updateCustomFieldValueA

Update custom field value. Set a custom field value for the organization, group, or device. Level API endpoint: PATCH /v2/custom-field-values

deleteCustomFieldValueB

Delete custom field value. Deletes a custom field value for the organization, group, or device. Level API endpoint: DELETE /v2/custom-field-values

listCustomFieldsB

List custom fields. Returns a list of custom fields. Level API endpoint: GET /v2/custom-fields

createCustomFieldC

Create custom field. Creates a custom field. Level API endpoint: POST /v2/custom-fields

showCustomFieldA

Show custom field. Retrieves the details of an existing custom field. Level API endpoint: GET /v2/custom-fields/{id}

updateCustomFieldC

Update custom field. Updates a custom field. Level API endpoint: PATCH /v2/custom-fields/{id}

deleteCustomFieldB

Delete custom field. Deletes a custom field. Level API endpoint: DELETE /v2/custom-fields/{id}

listDevicesA

List devices. Returns a list of your devices. Level API endpoint: GET /v2/devices

showDeviceA

Show device. Retrieves the details of an existing device. Level API endpoint: GET /v2/devices/{id}

deleteDeviceB

Delete device. Deletes the specified device. Level API endpoint: DELETE /v2/devices/{id}

updateDeviceC

Update device. Updates the specified device. Level API endpoint: PATCH /v2/devices/{id}

assignGroupDevicesB

Assign devices to group. Assigns the specified devices to the given group. Level API endpoint: POST /v2/groups/{id}/devices

removeGroupDevicesA

Remove devices from group. Removes the specified devices from the group. Level API endpoint: DELETE /v2/groups/{id}/devices

listGroupsA

List groups. Returns a list of your groups. Level API endpoint: GET /v2/groups

createGroupC

Create group. Creates a new group. Level API endpoint: POST /v2/groups

showGroupA

Show group. Retrieves the details of an existing group. Level API endpoint: GET /v2/groups/{id}

updateGroupC

Update group. Updates an existing group. Level API endpoint: PATCH /v2/groups/{id}

deleteGroupA

Delete group. Deletes an existing group. Level API endpoint: DELETE /v2/groups/{id}

tagDevicesC

Tag devices. Applies a tag to the provided devices. Level API endpoint: POST /v2/tags/{id}/devices

removeTagFromDevicesB

Remove tag from devices. Removes a tag from the provided devices. Level API endpoint: DELETE /v2/tags/{id}/devices

listTagsC

List tags. Returns a list of tags. Level API endpoint: GET /v2/tags

createTagC

Create tag. Creates a new tag. Level API endpoint: POST /v2/tags

showTagA

Show tag. Retrieves a tag. Level API endpoint: GET /v2/tags/{id}

updateTagB

Update tag. Updates an existing tag. Level API endpoint: PATCH /v2/tags/{id}

deleteTagC

Delete tag. Deletes a tag. Level API endpoint: DELETE /v2/tags/{id}

listUpdatesB

List updates. Returns a list of your updates. Level API endpoint: GET /v2/updates

showUpdateA

Show update. Retrieves the details of an existing update. Level API endpoint: GET /v2/updates/{id}

triggerWebhookA

Trigger webhook. Triggers an automation via a webhook. Webhooks that require an authorization header must include a write-enabled API key. Level API endpoint: POST /v2/automations/webhooks/{token}

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.1/5.0

Scored across 35 tools

Disambiguation5/5

Each tool targets a distinct resource and action (e.g., listDevices vs. showDevice vs. updateDevice). No two tools appear to perform the same operation, and even similar actions like tagDevices and removeTagFromDevices are clearly separated. The tool set is well-organized by resource.

Naming Consistency5/5

Tool names follow a consistent verb-noun pattern in camelCase (list, show, create, update, delete, assign, remove, tag, trigger, resolve). Multi-word actions like assignGroupDevices and removeTagFromDevices remain readable and consistent with the pattern.

Tool Count2/5

With 35 tools, the server is above the 25-tool threshold for 'too many'. While the broad scope covers multiple resource types (devices, groups, tags, custom fields, alerts, updates, automations), the sheer number creates a heavy surface that may overwhelm agents. A more focused set would improve usability.

Completeness2/5

The surface has significant gaps: there is no createDevice, and custom field values lack an explicit create operation. Alerts only support list/show/resolve, updates only support list/show, and automations are missing create/update/delete. These omissions will force agents to work around missing core operations, especially for device lifecycle management.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources