Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FRESHRELEASE_DOMAIN | Yes | Your Freshrelease domain (e.g., yourcompany.freshrelease.com) | |
| FRESHRELEASE_API_KEY | Yes | Your Freshrelease API key |
Schema
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fr_create_project | Create a project in Freshrelease. |
| fr_get_project | Get a project from Freshrelease by ID or key. - project_identifier: numeric ID (e.g., 123) or key (e.g., "ENG") |
| fr_create_task | Create a task under a Freshrelease project. - due_date: ISO 8601 date string (e.g., 2025-12-31) if supported by your account
- issue_type_name: case-insensitive issue type key (e.g., "epic", "task").
Resolved to an `issue_type_id` via `/project_issue_types` and added to payload.
- user: optional name or email. If provided and `assignee_id` is not,
resolves to a user id via `/{project_identifier}/users?q=...` and sets `assignee_id`.
- additional_fields: arbitrary key/value pairs to include in the request body
(unknown keys will be passed through to the API). Core fields
(title, description, assignee_id, status, due_date, issue_type_id) cannot be overridden. |
| fr_get_task | Get a task from Freshrelease by ID. |
| fr_get_all_tasks | Get a task from Freshrelease by ID. |
| fr_get_issue_type_by_name | Fetch the issue type object for a given human name within a project. This function lists issue types under the specified project and returns the first match by case-insensitive name comparison. |
| fr_search_users | Search users in a project by name or email. Calls `/{project_identifier}/users?q=search_text` and returns the JSON response. |
| fr_link_testcase_issues | Bulk update multiple test cases with issue links by keys. - Resolves `testcase_keys[]` via `GET /{project_identifier}/test_cases/{key}` to ids
- Resolves `issue_keys[]` via `GET /{project_identifier}/issues/{key}` to ids
- Performs: PUT `/{project_identifier}/test_cases/update_many` with body
{ "ids": [...], "test_case": { "issue_ids": [...] } } |