Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
RUST_LOGNoTracing log filter (e.g. omni_dev=debug) for diagnosing issues
AWS_REGIONNoAWS region for the Bedrock backend (e.g. us-west-2)
USE_OLLAMANoSet to "true" to route AI calls through a local Ollama or LM Studio server
USE_OPENAINoSet to "true" to route AI calls through the OpenAI Chat Completions API
DATADOG_SITENoOverride stored Datadog site; defaults to datadoghq.com
OLLAMA_MODELNoModel identifier to request from the Ollama-compatible server
CLAUDE_API_KEYNoAlternative to ANTHROPIC_API_KEY; accepted by the default AI backend
OPENAI_API_KEYNoOpenAI API key, required when USE_OPENAI=true
ANTHROPIC_MODELNoOverride the default Anthropic model identifier (e.g. claude-opus-4-7)
ATLASSIAN_EMAILNoAtlassian account email associated with the API token
DATADOG_API_KEYNoOverride stored Datadog API key
DATADOG_API_URLNoOverride site-derived URL for on-prem or proxied Datadog installs
DATADOG_APP_KEYNoOverride stored Datadog application key
OLLAMA_BASE_URLNoBase URL of the local Ollama or LM Studio server (e.g. http://localhost:11434)
OMNI_DEV_EDITORNoEditor command used for interactive prompts (falls back to EDITOR, then a platform default)
ANTHROPIC_API_KEYNoAnthropic API key for the default AI backend
AWS_ACCESS_KEY_IDNoAWS access key ID for the Bedrock backend (used by the AWS SDK)
AWS_SESSION_TOKENNoAWS session token for the Bedrock backend when using temporary credentials
OPENAI_AUTH_TOKENNoAlternative to OPENAI_API_KEY; accepted by the OpenAI backend
ATLASSIAN_API_TOKENNoAtlassian API token for Jira and Confluence tools
OMNI_DEV_AI_BACKENDNoSelect the AI backend explicitly. Options: claude-cli, ollama, openai, bedrock, or unset for the default Anthropic API
OMNI_DEV_CONFIG_DIRNoOverride the directory used for omni-dev configuration (default: ~/.omni-dev)
AWS_SECRET_ACCESS_KEYNoAWS secret access key for the Bedrock backend (used by the AWS SDK)
ATLASSIAN_INSTANCE_URLNoAtlassian instance base URL (e.g. https://your-org.atlassian.net)
CLAUDE_CODE_USE_BEDROCKNoSet to "true" to route AI calls through AWS Bedrock instead of the Anthropic API
ANTHROPIC_DEFAULT_OPUS_MODELNoOverride the model identifier used when an Opus-tier model is requested
ANTHROPIC_DEFAULT_HAIKU_MODELNoOverride the model identifier used when a Haiku-tier model is requested
ANTHROPIC_DEFAULT_SONNET_MODELNoOverride the model identifier used when a Sonnet-tier model is requested

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
ai_chatA

Send a single message to the configured AI (Claude/OpenAI/Ollama/Bedrock) and return its response. Non-streaming, single-turn. On missing credentials, returns a tool error containing the same diagnostic the CLI would print. Mirrors omni-dev ai chat in one-shot form.

atlassian_auth_statusA

Report which Atlassian credential scopes have credentials configured. Returns boolean presence flags only — NEVER includes the email, API token, or any other secret. The instance URL (non-secret) is returned verbatim. Read-only. Output is YAML.

atlassian_convertA

Convert between JFM markdown and ADF JSON. Mirrors omni-dev atlassian convert to-adf / from-adf. direction must be either "to-adf" or "from-adf".

claude_skills_cleanA

Remove skill symlinks and the managed exclude block created by a prior claude_skills_sync. MUTATES THE FILESYSTEM. Operates relative to the server process's cwd. Mirrors omni-dev ai claude skills clean.

claude_skills_statusA

Report symlinks and managed exclude-block entries left by prior claude_skills_sync runs. Read-only. Operates relative to the server process's cwd. Mirrors omni-dev ai claude skills status.

claude_skills_syncA

Sync Claude Code skills from the current repository (the MCP server's current working directory) into target worktrees. MUTATES THE FILESYSTEM: creates symlinks inside .claude/skills/ and upserts a managed block in .git/info/exclude. Operates relative to the server process's cwd — not cross-project. Mirrors omni-dev ai claude skills sync.

config_models_showA

Return the embedded models.yaml listing every AI model the CLI knows about (identifiers, token budgets, provider). Output is YAML. Mirrors omni-dev config models show.

confluence_attachment_deleteB

Delete a Confluence attachment by ID. Set purge: true to permanently purge instead of moving to trash (requires space admin). Mirrors omni-dev atlassian confluence attachment delete --force.

confluence_attachment_listA

List attachments on a Confluence page (one page per call). Pass the returned next_cursor back as cursor to fetch the next page. limit defaults to 25. Mirrors omni-dev atlassian confluence attachment list.

confluence_attachment_uploadA

Upload a local file as an attachment to a Confluence page. file_path is a path on the MCP server's filesystem (the file is streamed from disk, never fully buffered). Optional filename overrides the stored name; comment is recorded as a version note; minor_edit (default false) marks the upload as minor. Returns YAML describing the new attachment. Mirrors omni-dev atlassian confluence attachment upload.

confluence_childrenB

List children of a Confluence page, or top-level pages in a space. Supports optional recursion with a max depth. Mirrors omni-dev atlassian confluence children.

confluence_comment_addA

Post a markdown comment to a Confluence page. The content is converted to ADF before posting. Mirrors omni-dev atlassian confluence comment add.

confluence_comment_listA

List footer comments on a Confluence page (auto-paginated). limit of 0 returns every comment. Mirrors omni-dev atlassian confluence comment list.

confluence_compareB

Compare two versions of a Confluence page. Returns a structurally-aware diff: walks the ADF tree, splits the document into heading-delimited sections, and reports per-block changes rather than character-level deltas over a serialization.

Version refs accept "latest", "previous", "v-N" (e.g. "v-2"), a numeric version, or an ISO 8601 date. previous is relative to to.

Detail levels: summary (counts only), outline (default — per-section change kind + drill-in cursors), full (embeds per-section deltas, budget-truncated).

Mirrors omni-dev atlassian confluence compare run.

confluence_compare_sectionA

Drill into a section diff using a cursor returned by confluence_compare (outline mode). Stateless: the cursor encodes the page ID and version pair. Output formats: "unified" (default), "side_by_side", "markdown_inline". Mirrors omni-dev atlassian confluence compare section.

confluence_createB

Create a new Confluence page from JFM markdown (default) or raw ADF JSON. JFM is GitHub-style markdown, NOT Confluence wiki markup — see resource omni-dev://specs/jfm for syntax. Returns the new page's ID. Mirrors omni-dev atlassian confluence create.

confluence_deleteA

Delete a Confluence page. IRREVERSIBLE. Requires the caller to pass confirm: true to prevent accidental deletions. Set purge: true to permanently purge instead of moving to trash (requires space admin). Mirrors omni-dev atlassian confluence delete --force.

confluence_downloadA

Recursively download a Confluence page or an entire space into a directory. Either id (root page) or space (space key) must be provided. Returns a YAML manifest summary of downloaded pages. Mirrors omni-dev atlassian confluence download.

confluence_historyA

List version history (metadata only) for a Confluence page. Returns version number, timestamp, author account ID, edit message, and minor-edit flag for each version, newest-first. Does NOT fetch version bodies — use confluence_read for content. since filters to versions at or after a numeric version ("5") or ISO 8601 date ("2026-01-01T00:00:00Z"). limit defaults to 20; 0 means unlimited. Mirrors omni-dev atlassian confluence history.

confluence_label_addB

Add one or more labels to a Confluence page. Mirrors omni-dev atlassian confluence label add.

confluence_label_listA

List labels on a Confluence page (auto-paginated). limit of 0 returns every label. Mirrors omni-dev atlassian confluence label list.

confluence_label_removeA

Remove one or more labels from a Confluence page. Destructive operation: callers must explicitly pass confirm: true for the removal to proceed; otherwise the tool refuses with an error. Mirrors omni-dev atlassian confluence label remove.

confluence_moveA

Move or reparent a Confluence page within its current space. position is "append" (default — target becomes new parent), "before", or "after" (sibling reorder relative to target). Same-space only — cross-space moves are not supported. Returns the moved page's metadata as YAML (id, title, parent_id, ancestors). Mirrors omni-dev atlassian confluence move.

confluence_readA

Fetch a Confluence page by ID. Returns JFM markdown by default, or raw ADF JSON when format="adf". When output_file is set, the content is written to that path and the tool returns a short YAML summary (path/bytes/format) — useful for large pages. Mirrors omni-dev atlassian confluence read.

confluence_searchA

Search Confluence pages using CQL. Returns YAML with matching page IDs, titles, and space keys. Mirrors omni-dev atlassian confluence search --cql.

confluence_user_searchA

Search Confluence users by display name or email. limit of 0 returns every match; defaults to 25. Mirrors omni-dev atlassian confluence user search.

confluence_writeA

Overwrite a Confluence page's body from JFM markdown (default) or raw ADF JSON. JFM is GitHub-style markdown, NOT Confluence wiki markup — see resource omni-dev://specs/jfm for syntax. Mirrors omni-dev atlassian confluence write --force.

datadog_auth_statusA

Report which Datadog credential scopes have credentials configured. Returns boolean presence flags only — NEVER includes the API key, application key, or any other secret. The site (non-secret) is returned verbatim. Read-only. Output is YAML.

datadog_dashboard_getA

Fetch a single Datadog dashboard by id (string). Returns the full definition including widgets. Mirrors omni-dev datadog dashboard get. Output is YAML.

datadog_dashboard_listA

List Datadog dashboards. filter_shared (boolean, optional) restricts to shared / non-shared dashboards. Mirrors omni-dev datadog dashboard list. Output is YAML.

datadog_downtime_listC

List Datadog scheduled downtimes. active_only (boolean, optional) restricts to currently-active downtimes. Mirrors omni-dev datadog downtime list. Output is YAML.

datadog_events_listA

List Datadog events. limit of 0 (or omitted) auto-paginates across cursor pages up to 10000; any non-zero value caps the total at that count. from / to accept relative shorthand (15m, 1h), now, RFC 3339, or Unix epoch seconds. Mirrors omni-dev datadog events list. Output is YAML.

datadog_hosts_listA

List Datadog reporting hosts. limit of 0 (or omitted) auto-paginates up to 10000. Mirrors omni-dev datadog hosts list. Output is YAML.

datadog_logs_searchA

Search Datadog log events. limit of 0 (or omitted) auto-paginates across cursor pages up to 10000; any non-zero value caps the total at that count. sort is timestamp-asc or timestamp-desc (default). Mirrors omni-dev datadog logs search. Output is YAML.

datadog_metrics_catalog_listA

List metrics in the Datadog catalog (/api/v1/metrics). Distinct from datadog_metrics_query: returns metric names ingested since from, optionally filtered by host. Mirrors omni-dev datadog metrics catalog list. Output is YAML.

datadog_metrics_queryA

Execute a point-in-time Datadog metrics timeseries query. Mirrors omni-dev datadog metrics query. Returns YAML matching the CLI -o yaml output (status, from_date, to_date, series).

datadog_monitor_getA

Fetch a single Datadog monitor by numeric id. Mirrors omni-dev datadog monitor get. Output is YAML.

datadog_monitor_listA

List Datadog monitors with optional name / tags filters. limit of 0 (or omitted) auto-paginates up to 10000. Mirrors omni-dev datadog monitor list. Output is YAML.

datadog_monitor_searchA

Free-text / faceted search across Datadog monitors. limit of 0 (or omitted) auto-paginates up to 10000. Mirrors omni-dev datadog monitor search. Output is YAML.

datadog_slo_getA

Fetch a single Datadog SLO by id (string). Mirrors omni-dev datadog slo get. Output is YAML.

datadog_slo_listA

List Datadog Service Level Objectives. limit of 0 (or omitted) auto-paginates up to 10000. Mirrors omni-dev datadog slo list. Output is YAML.

git_branch_infoA

Analyze branch commits against a base and return repository information as YAML. Mirrors omni-dev git branch info.

git_check_commitsA

Validate commit messages in a range against commit guidelines. Mirrors omni-dev git commit message check. Returns a YAML payload with the full CheckReport, a pass/fail summary, and the exit code the CLI would use (honouring strict).

git_create_prA

Generate an AI-drafted pull request title and description for the current branch. Mirrors omni-dev git branch create pr in its content-generation phase — this tool returns the proposed PR content as YAML and does NOT push the branch or invoke gh pr create.

git_twiddle_commitsA

Generate improved commit messages for a range and (by default) apply them. Mirrors omni-dev git commit message twiddle --auto-apply. Set dry_run = true to return the proposed amendments as YAML without applying them. The editor is never started from this tool.

git_view_commitsC

Analyze commits in a range and return repository information as YAML. Mirrors omni-dev git commit message view.

jira_attachment_downloadB

Download attachments on a JIRA issue to disk. Returns YAML metadata (id, filename, mime_type, size, on-disk path) for each downloaded file. If output_dir is omitted, files are written to a fresh temp directory whose path is in the result; the assistant can then read them via the filesystem tool. Mirrors omni-dev atlassian jira attachment download.

jira_attachment_imagesA

Download image attachments (PNG, JPEG, GIF, SVG, WebP) on a JIRA issue to disk. Returns YAML metadata for each downloaded image. If output_dir is omitted, files are written to a fresh temp directory. Mirrors omni-dev atlassian jira attachment images.

jira_board_issuesA

List issues on a JIRA agile board. Accepts an optional JQL filter. Returns YAML. Mirrors omni-dev atlassian jira board issues.

jira_board_listA

List JIRA agile boards, optionally filtered by project key and/or board type (scrum/kanban). Returns YAML. Mirrors omni-dev atlassian jira board list.

jira_changelogA

Get the change history for a JIRA issue. Returns YAML with one entry per change (author, timestamp, items). Mirrors omni-dev atlassian jira changelog.

jira_commentA

Manage JIRA issue comments. action = "list" returns comments as YAML; action = "add" posts the given body (JFM markdown).

jira_comment_editA

Edit an existing JIRA comment. body is JFM markdown (see resource omni-dev://specs/jfm) and replaces the current comment text. Optional visibility = {type: "group"|"role", value: <name>} updates the restriction. JIRA enforces stricter permissions on edit than on add (often only the original author can edit) — when JIRA refuses, its error message is surfaced verbatim. Returns the updated comment metadata as YAML.

jira_createA

Create a new JIRA issue. Returns the new issue key and self URL as YAML.

jira_deleteA

Delete a JIRA issue. DESTRUCTIVE AND IRREVERSIBLE. You must explicitly pass confirm: true for the deletion to proceed; otherwise the tool returns an error without contacting the API. Returns YAML {status: ok} on success. Mirrors omni-dev atlassian jira delete.

jira_devA

Fetch development status for a JIRA issue: linked pull requests, branches, and repositories as YAML.

jira_field_listA

List JIRA field definitions, optionally filtered by name substring. Returns YAML. Mirrors omni-dev atlassian jira field list.

jira_field_optionsA

List allowed option values for a JIRA custom field. If context_id is omitted, the first context for the field is auto-discovered. Returns YAML. Mirrors omni-dev atlassian jira field options.

jira_linkA

Manage JIRA issue links and hierarchy. Actions: "list" (needs key), "types", "create" (needs key, target, link_type), "remove" (needs link_id), "parent" (needs key = child, target = parent — sets the system parent field for Epic → Story / Story → Sub-task hierarchy, distinct from relationship links).

jira_link_listA

List inward and outward links on a JIRA issue. Returns YAML with one entry per link (id, link_type, direction, linked_issue_key, linked_issue_summary). Mirrors omni-dev atlassian jira link list.

jira_link_removeA

Remove a JIRA issue link by its link ID (use jira_link_list or jira_read to discover IDs). Destructive operation: callers must explicitly pass confirm: true for the removal to proceed; otherwise the tool refuses with an error. Returns YAML {status: ok}. Mirrors omni-dev atlassian jira link remove.

jira_link_typesA

List the configured JIRA issue link-type catalogue (id, name, inward, outward). Global per JIRA instance — returns the configured types, not the ones used in any particular issue. Returns YAML. Mirrors omni-dev atlassian jira link types.

jira_project_listA

List JIRA projects. Returns YAML. Mirrors omni-dev atlassian jira project list.

jira_readA

Fetch a JIRA issue. Returns JFM markdown (default, AI-friendly) or raw ADF JSON when format = "adf". When output_file is set, the content is written to that path and the tool returns a short YAML summary (path/bytes/format) — useful for large issues.

jira_searchA

Search JIRA issues using a JQL query. Returns matching issues as YAML.

jira_sprint_addB

Add one or more issues to a JIRA sprint by issue key. Returns YAML {status: ok} on success. Mirrors omni-dev atlassian jira sprint add.

jira_sprint_createB

Create a new sprint on a JIRA agile board. Returns YAML for the created sprint. Mirrors omni-dev atlassian jira sprint create.

jira_sprint_issuesB

List issues in a JIRA sprint. Accepts an optional JQL filter. Returns YAML. Mirrors omni-dev atlassian jira sprint issues.

jira_sprint_listA

List sprints on an agile board, optionally filtered by state (active/future/closed). Returns YAML. Mirrors omni-dev atlassian jira sprint list.

jira_sprint_updateA

Update sprint name, state (future/active/closed), dates, or goal. Returns YAML {status: ok}. Mirrors omni-dev atlassian jira sprint update.

jira_transitionA

Transition a JIRA issue to a new workflow status. Most common usage: pass the transition name in transition, e.g. transition: "In Progress". The numeric id also works, e.g. transition: "31". Names are matched case-insensitively. If unsure which transitions are valid from the issue's current status, call this tool first with list = true (or omit transition) to get the available {id, name} pairs as YAML, then call again with one of those names. Optionally posts comment (JFM markdown) after the transition succeeds.

jira_transition_listA

List the workflow transitions available from a JIRA issue's current status. Returns YAML with {id, name, to_status, has_screen} for each transition. Faster and lighter than jira_read when you only need the transition ids and names to feed into jira_transition. Equivalent to jira_transition with list = true, but exposed as a single-purpose tool for discoverability.

jira_user_searchA

Search JIRA users by display-name or email substring. Returns matches as YAML — each entry includes account_id, display_name, email_address (often redacted by GDPR), active, and account_type. Use the returned account_id as input to jira_write's assignee or reporter parameter. limit defaults to 25; pass 0 for unlimited. Atlassian matches substrings on display name and email — try a shorter or alternate spelling if the first attempt returns nothing.

jira_version_createA

Create a new version in a JIRA project. Dates must be YYYY-MM-DD and are validated client-side. Returns YAML for the created version. Mirrors omni-dev atlassian jira version create.

jira_version_listA

List versions for a JIRA project, optionally filtered by released and archived flags. Returns YAML. Mirrors omni-dev atlassian jira version list.

jira_watcher_addA

Add a user (by Atlassian account ID) as a watcher on a JIRA issue. Returns YAML {status: ok}. Mirrors omni-dev atlassian jira watcher add.

jira_watcher_listA

List watchers on a JIRA issue. Returns YAML with watch_count and an array of watcher accounts. Mirrors omni-dev atlassian jira watcher list.

jira_watcher_removeA

Remove a user (by Atlassian account ID) from the watchers of a JIRA issue. Destructive operation: callers must explicitly pass confirm: true for the removal to proceed; otherwise the tool refuses with an error. Returns YAML {status: ok}. Mirrors omni-dev atlassian jira watcher remove.

jira_worklog_addA

Log time on a JIRA issue. time_spent accepts JIRA's duration format (e.g., 1h 30m, 2d). Returns YAML {status: ok}. Mirrors omni-dev atlassian jira worklog add.

jira_worklog_listA

List worklog entries on a JIRA issue. Returns YAML. Mirrors omni-dev atlassian jira worklog list.

jira_writeA

Update a JIRA issue. content updates the description (JFM markdown by default, or raw ADF JSON when format = "adf"); omit it to leave the description unchanged. JFM is GitHub-style markdown — see resource omni-dev://specs/jfm for syntax. parent sets the system parent field for hierarchy (Epic → Story, Story → Sub-task) — distinct from jira_link actions, which create relationship links (Blocks, Composition, etc.) rather than the parent field. assignee/reporter accept an accountId (use the empty string "" to clear, "-1" for JIRA automatic assignment); call jira_user_search first if you only have a name or email. fields is an escape hatch — a map of canonical JIRA field id to its API JSON value (e.g. {"priority": {"name": "High"}}) — for fields without a typed parameter. At least one of content, parent, assignee, reporter, or fields must be supplied.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
git_commitsYAML commit analysis for a git range (e.g. `HEAD`, `HEAD~3..HEAD`). Backed by the same core as `omni-dev git commit message view`.
jira_issue_jfmJIRA issue rendered as JFM (JIRA-flavoured markdown).
jira_issue_adfJIRA issue body as raw Atlassian Document Format (ADF) JSON.
confluence_page_jfmConfluence page rendered as JFM markdown.
confluence_page_adfConfluence page body as raw ADF JSON.
omni_dev_specReference specs maintained by omni-dev. Currently supports `jfm` (JIRA-Flavoured Markdown) — fetch before writing JIRA or Confluence content via `jira_write`, `jira_create`, or `confluence_write`.

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/rust-works/omni-dev'

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