Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OMNARA_API_KEYNoOmnara personal access token or org API key
OMNARA_API_URLNoAPI URL for self-hosted instances (default https://api.omnara.com/v1)

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
{
  "listChanged": true
}
logging
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
agents_archiveA

Archives the agent: requests cancellation of its active runtime, cancels queued inputs and affected processes, removes its pending wakeup, releases explicit machine bindings, deletes pooled machines created for the agent, and deletes cron triggers targeting the agent. The agent and its full event history stay readable by id; archived agents leave listings. The agent's profile and configuration are retained, as are explicitly attached BYO machines. Archiving an already-archived agent is a no-op that returns the agent unchanged.

agents_cancelD

Cancel agent

agents_events_listA

Returns one page of agent events, chronological within the page. Forward pagination (after_sequence) walks from a known boundary toward the present using next_after_sequence. Backward pagination (before_sequence) starts at the latest events and walks toward the beginning using next_before_sequence; passing before_sequence takes precedence over after_sequence.

agents_getD

Get agent

agents_inputD

Create agent input

agents_interactions_listC

Items are ordered by created_at ascending, then id ascending.

agents_interactions_resolveD

Resolve agent interaction

agents_launchA

Launch from a pinned config, optionally adding agent-local integration tools, subscriptions and interaction handlers and admitting an attributed initial text input in the same transaction. Adding integration capabilities requires project management permission; launching an existing config requires agent operate permission. Reusing an idempotency key returns the current agent even if the retry body differs. The retry body is not applied and integration references are not resolved again.

agents_listC

Items are ordered by created_at descending, then id descending.

agents_updateD

Update agent config

configs_createD

Create agent config

configs_getC

Get agent config

crons_createA

Creates a cron trigger that fires on a schedule. A trigger targeting an agent profile launches a new agent from the profile's current config on each firing; a trigger targeting an agent sends an input to that agent. Missed firings are coalesced, matching standard cron behavior: if one or more scheduled times pass while firing is delayed, the trigger fires once for the oldest missed time and then resumes its schedule from the current time, without retroactively firing for the other missed times.

crons_deleteD

Delete cron trigger

crons_getD

Get cron trigger

crons_listC

Items are ordered by created_at descending, then id descending.

crons_updateA

Updates the schedule, message template, or enabled state. The target is immutable; delete the trigger and create a new one to retarget.

grant_machines_addC

Create project machine grant

grant_machines_deleteA

Removes the project's access to the machine. Processes that depended on the grant are stopped. The machine itself is retained, and there are no dependency blockers.

grant_machines_listA

Lists explicit machine grants that can be deleted directly. Pool-derived machine access is managed through project machine pool grants.

grant_models_addD

Create project model grant

grant_models_deleteA

Removes the project's access to the configured model. The grant is live policy: new launches can no longer select the model, and agents already using it lose access on their next model call. The model itself is retained, and there are no dependency blockers.

grant_models_editA

Updates the project's overrides for the configured model. Omitted fields keep their current values; null clears an override so the project inherits from the configured model. The grant is live policy: agents already using the model re-apply the updated overrides on their next model call, against the configured-model revision each agent pinned at launch. Updates are validated against the configured model's current revision only, so an update can make an agent pinned to an older, incompatible revision fail its next model call.

grant_models_listC

Items are ordered by created_at descending, then id descending.

grant_pools_addC

Create project machine pool grant

grant_pools_deleteA

Removes the project's access to the machine pool, revokes machine grants generated through it, and stops processes that depended on those grants. The pool itself is retained, and there are no dependency blockers.

grant_pools_editA

Updates the grant's overrides and limits. Omitted fields keep their current values; null clears an override so the grant follows the machine pool again. Overlay objects and metadata are replaced whole when present. Existing machines keep their configuration; the updated defaults and limits apply to new launches.

grant_pools_getC

Get project machine pool grant

grant_pools_listD

Items are ordered by created_at descending, then id descending.

grant_secrets_addC

Create secret grant

grant_secrets_deleteA

Deletes only this project grant. The secret, its versions, the target project, and other grants are retained, and there are no dependency blockers.

grant_secrets_listC

Items are ordered by created_at descending, then id descending.

grant_skills_addD

Create skill grant

grant_skills_deleteA

Deletes only this project grant. The skill, its revisions, the target project, and other grants are retained, and there are no dependency blockers.

grant_skills_listC

Items are ordered by created_at descending, then id descending.

machines_createD

Connect a BYO machine

machines_deleteA

Deletes a BYO machine, ends its active daemon runtimes and work, revokes its daemon tokens and project grants, and releases agent bindings. Pooled machines are managed through their machine pool and cannot be deleted through this route. There are no dependency blockers for a BYO machine.

machines_getC

Get machine

machines_listC

Items are ordered by machine created_at descending, then machine id descending.

machines_updateC

Update machine execution defaults

model_providers_catalogA

Fetches the provider's live model catalog by validating the configured credential and probing the provider's /models endpoint. The call waits on the upstream provider, so it is slower than the other model provider config routes and can report failure as data.

model_providers_createA

Create a model provider config, validate the configured credential where the provider exposes a validation endpoint, then probe the provider's /models endpoint. The result is returned as model_catalog; a failed probe does not fail creation.

model_providers_deleteA

Deletes only the model provider config. Deletion is blocked while it has configured models. Cluster-managed provider configs cannot be deleted through this route.

model_providers_getC

Get model provider config

model_providers_listA

List model provider configs with server-side filtering, sorting, and cursor pagination.

model_providers_updateD

Update model provider config

models_createC

Create configured model

models_deleteA

Deletes only the configured model. Deletion is blocked while it has active project grants. Cluster-managed configured models cannot be deleted through this route.

models_listC

Items are ordered by created_at descending, then id descending.

models_updateC

Update configured model

orgs_createA

Creates the organization and its local default resources atomically. An idempotency key determines the proposed organization ID; replaying it returns the existing organization. Without a key, each request is a fresh attempt. Optional default-provider provisioning begins after commit and retries asynchronously without failing organization creation.

orgs_listA

Users get every organization they belong to; org API keys get the organization that issued them. Items are ordered by organization name ascending.

pools_createA

Creates a machine pool in the organization. The body carries the pool name, the provider (arker, blaxel, boxd, createos, daytona, freestyle, modal, tenki, or unikraft), the provider auth secret, default machine settings, and the per-machine and total CPU, memory, and machine-count limits the provider supports; the required fields depend on the provider. See the createMachinePool operation in the Omnara API reference at https://docs.omnara.com/api-reference for the full request schema.

pools_deleteA

Deletes the machine pool and its pooled machines, revokes generated machine grants and project machine-pool grants, and stops processes that depended on those grants. Deleting a cluster-managed machine pool is rejected with 409 Conflict; there are no other dependency blockers.

pools_getD

Get machine pool

pools_listA

List machine pools with server-side filtering, sorting, and cursor pagination.

pools_updateB

Tenant-managed pools support every request field. Cluster-managed pools only allow changes to default CPU and memory, environment and secret environment variables, provider-supported per-machine CPU and memory limits, and the idle deletion policy. Other cluster-managed changes are rejected with 409 Conflict.

profiles_createD

Create agent profile

profiles_deleteA

Deletes the profile, all of its profile versions, and any cron triggers targeting the profile. Agents launched from the profile are retained and keep running: each agent holds an immutable snapshot of the configuration it was launched with, so its reference to the profile becomes historical provenance only. Integration settings may retain the public profile ID; future launches fail as unavailable until those settings reference an available profile.

profiles_getD

Get agent profile

profiles_listC

Items are ordered by created_at descending, then id descending.

profiles_renameD

Rename agent profile

profiles_updateD

Update agent profile

projects_createC

Create project

projects_listC

Items are ordered by created_at descending, then id descending.

secrets_createD

Create secret

secrets_deleteA

Deletes the secret and permanently destroys all of its versions and project grants; the ciphertext cannot be recovered. Deletion is blocked while the secret is the credential of a model provider config, machine pool, or integration.

secrets_getC

Get secret through ownership authority

secrets_listA

Items are ordered by created_at descending, then id descending. Without an owner filter, returns the deduplicated union of organization secrets the caller may list, project secrets the caller may list, and the caller's own user secrets.

secrets_updateC

Update secret metadata

skills_deleteA

Deletes the skill together with all of its revisions and project grants; uploaded archive content is destroyed. No other resources are deleted. Deletion is blocked while an active agent's configuration references the skill.

skills_getC

Get skill through ownership authority

skills_listA

Items are ordered by created_at descending, then id descending. Without an owner filter, returns the deduplicated union of organization skills the caller may list, project skills the caller may list, and the caller's own user skills. Grants are managed separately and do not change ownership.

tools_catalogC

Get tool catalog

whoamiA

Get the authenticated user and their organizations

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.4/5.0

Scored across 75 tools

Disambiguation3/5

The set contains many parallel tool pairs such as models_delete vs grant_models_delete, pools_delete vs grant_pools_delete, and secrets_create vs grant_secrets_add, which could cause misselection without careful reading. Descriptions clarify boundaries, but the sheer number of tools with grant/non-grant and resource/action variations creates moderate ambiguity.

Naming Consistency4/5

Nearly all tool names use snake_case with a resource-first pattern (e.g., agents_get, models_create, grant_pools_add), which is predictable and readable. Minor deviations exist: grants use add/edit while base resources use create/update, and a few tools like whoami or profiles_rename break the verb pattern.

Tool Count1/5

75 tools is an extreme mismatch for a single MCP server. While the domain is broad, this count far exceeds typical well-scoped ranges (3–15) and is likely to overwhelm an agent's selection process.

Completeness3/5

Core resources like secrets, machines, pools, crons, and grants have near-complete CRUD coverage. However, notable gaps exist: no configs_list/update/delete, no projects_get/update/delete, no skills_create, and no models_get, which will limit several agent workflows.