Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
jira.urlYesYour Jira instance URL.
git.reposNoOptional explicit paths to repos that count as work, in addition to those discovered under git.repo_roots.
jira.emailYesThe email address associated with your Jira account.
git.repo_rootsYesDirectory (or directories) where your work git clones live.
jira.api_tokenYesYour Jira API token (create one at https://id.atlassian.com/manage-profile/security/api-tokens).
git.remote_orgsYesThe GitHub orgs whose origin remotes count as work.
git.author_emailYesThe email address on your commits, used to find your work.
jira.project_keyYesThe Jira project key where tickets are created.
defaults.issue_typeYesThe Jira issue type to use, usually `Task`.
defaults.task_type_fieldNoOptional custom field id for a Jira select field such as "Task type", e.g. `customfield_10100`.
defaults.frontend_servicesYesRepo names that get a `[FE]` prefix instead of `[BE]`.
defaults.task_type_optionsNoOptional mapping of task type option names to Jira option ids for defaults.task_type_field, e.g. `{development: "10200", maintenance: "10201"}`.

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription

No tools

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources