@flowrelay/mcp-server 1.0.22 → 1.0.24

package/README.md

@@ -1,6 +1,6 @@
 # Flow Relay MCP Server
 
-Flow Relay MCP Server adds project-aware, multi-tenant Flow Relay tools to MCP clients such as Claude Desktop and Claude Code.
+Flow Relay MCP Server adds project-aware, multi-tenant Flow Relay tools to MCP clients such as Claude Desktop, Claude Code, Cursor and Windsurf.
 
 It connects to Flow Relay API v1 using an API key and supports:
 
@@ -9,47 +9,71 @@ It connects to Flow Relay API v1 using an API key and supports:
 ## Package
 
 - Name: @flowrelay/mcp-server
-- Version: 1.0.16
+- Version: 1.0.24
+
+## Supported Sources (46 Integrations)
+
+Flow Relay MCP Server supports 46 integration sources across the entire engineering lifecycle:
+
+- **Code & Version Control**: `github`, `gitlab`, `bitbucket`, `azure_devops` (support branch filtering)
+- **CI/CD & Deployment**: `buildkite`, `circleci`, `vercel`, `netlify`, `render`, `railway`, `cloudflare_pages`
+- **Issue Tracking & Project Management**: `linear`, `jira`, `clickup`, `monday_com`, `shortcut`, `asana`
+- **Observability & Incidents**: `sentry`, `datadog`, `pagerduty`, `incident_io`, `grafana`, `new_relic`
+- **Product Analytics**: `posthog`
+- **Security & Code Quality**: `snyk`, `sonarqube`
+- **Feature Flags & Infrastructure**: `launchdarkly`, `hcp_terraform`
+- **Meetings & Collaboration**: `fireflies`, `zoom`, `google_calendar`, `miro`
+- **Customer Support**: `intercom`, `zendesk`, `jira_service_management`
+- **CRM**: `hubspot`, `salesforce`
+- **Communication & Email**: `slack`, `discord`, `microsoft_teams`, `microsoft_outlook`, `gmail`
+- **Documents & Design**: `notion`, `confluence`, `google_drive`, `figma`
 
 ## What Is Included
 
-The server currently exposes these tools:
-
-- get_workspace_context
-- list_projects
-- set_active_project
-- list_filter_options (lists the selectable resources, branches, event types and priorities per source for a project – call this before generating so handoff/insight filters use real values instead of guesses; also reports whether Figma is selectable, since Figma requires the project's processing region to be Global)
-- list_handoffs (returns project-specific handoffs, or an aggregated view of all accessible project handoffs if no project is active; filter by status: active, archived, or all)
-- ask_project (ask a question about a project and get an answer grounded in codebase, baselines and 14 days of activity; 2 credits per question)
-- generate_handoff (processed asynchronously, and the server automatically polls until the job finishes. Requires active project or project_id. Accepts per-source filters: projects, eventTypes, branches, priorities.)
-- generate_correlation_insight (accepts per-source filters)
-- generate_onboarding_brief (accepts per-source filters)
-- generate_architecture_insight (accepts per-source filters)
-- generate_release_notes (generates release notes or PR descriptions from code activity; accepts per-source filters)
-- list_digests (lists past scheduled activity digests for a project)
-- list_insights
-- list_integrations
-- list_events
-- list_untracked_resources (lists event-producing resources not scoped to any project – useful for discovering untracked activity)
-- discord_list_channels
-- discord_send_message (plain text, or a handoff/insight by id or `last_*` – `last_handoff`, `last_correlation`, `last_onboarding`, `last_architecture`, `last_release_notes` – rendered to Markdown and attached as a `.md` file)
+The server currently exposes 18 tools:
+
+- `get_workspace_context`: Show current Flow Relay context (account mode, organizations count, accessible projects count, active project scope and caller role).
+- `list_projects`: List every accessible project (personal and organization) with id, scope and role.
+- `set_active_project`: Set or clear the active project for subsequent tool calls so `project_id` can be omitted.
+- `list_filter_options`: List selectable resources (projects/repos/channels/boards), branches, event types and priorities per source for a project. Call this before generating so handoff and insight filters use real values instead of guesses. Also reports whether Figma visual context is selectable (requires Global processing region).
+- `list_handoffs`: List handoffs for the active project or across accessible projects. Filter by status (`active`, `archived` or `all`). Outputs server-rendered Markdown.
+- `generate_handoff`: Generate an async handoff with automated polling until completion. Requires active project or explicit `project_id`. Accepts per-source `filters` (`projects`, `eventTypes`, `branches`, `priorities`).
+- `generate_correlation_insight`: Generate a cross-source correlation insight. Accepts per-source `filters`.
+- `generate_onboarding_brief`: Generate an onboarding brief insight. Accepts per-source `filters`.
+- `generate_architecture_insight`: Generate an architecture insight. Accepts per-source `filters`.
+- `generate_release_notes`: Turn a project's merged work into release notes or a PR description (`style: 'release_notes' | 'pr_description'`). Accepts code source, repo and per-source `filters`. Costs 3 credits per run.
+- `ask_project`: Ask one question about a project and get an answer grounded in its indexed codebase, baselines and last 14 days of activity. Answers synchronously and cites used events (`ev:...`). Costs 2 credits per question.
+- `list_digests`: Browse scheduled activity digests of a project, newest first. Reading is free.
+- `list_insights`: List project AI insights by kind and status.
+- `list_integrations`: List connected integrations in personal or project scope.
+- `list_events`: Browse recent events in personal or project scope.
+- `list_untracked_resources`: List event-producing resources not scoped to any project (useful for discovering unassigned activity).
+- `discord_list_channels`: List text channels in connected Discord servers.
+- `discord_send_message`: Send a Discord message – plain text, or attach a rendered Markdown artifact (`last_handoff`, `last_correlation`, `last_onboarding`, `last_architecture` or `last_release_notes`) as a `.md` file.
+
+### Filter Dimensions
+
+When calling `generate_handoff`, insight tools or `generate_release_notes`, per-source `filters` accept:
+
+- `projects`: Resource ids from `list_filter_options[source].projects` (repos, channels, boards, spaces, services, sites, projects).
+- `eventTypes`: Event-type values from `list_filter_options` (e.g. `push`, `issue_created`, `workflow_job`).
+- `branches`: Git branch names (`main`, `develop`) – git sources only (`github`, `gitlab`, `bitbucket`, `azure_devops`).
+- `priorities`: Priority values – supported on `jira`, `linear`, `sentry`, `pagerduty`, `incident_io`, `clickup`, `zendesk`, `snyk` and `grafana`.
 
 ## Environment Variables
 
 Required:
 
-- FLOWRELAY_API_KEY
+- `FLOWRELAY_API_KEY`: Your Flow Relay API key (`fr_...`).
 
 Optional:
 
-- FLOWRELAY_PROJECT_ID
-- FLOWRELAY_BASE_URL
-
-If FLOWRELAY_PROJECT_ID is set, it becomes the default project context for project-aware tools unless you override it per call.
+- `FLOWRELAY_PROJECT_ID`: Initial active project context for project-aware tools.
+- `FLOWRELAY_BASE_URL`: Base URL of the Flow Relay API (defaults to `https://www.flowrelay.it`).
 
 ## Quick Start (Claude Desktop)
 
-Add this to your claude_desktop_config.json:
+Add this to your `claude_desktop_config.json`:
 
 ```json
 {
@@ -69,15 +93,16 @@ Add this to your claude_desktop_config.json:
 ## Multi-Tenant Behavior
 
 - Every handoff and insight is tied to a project; you need an active project (`set_active_project`) or `project_id`. Events and integrations remain user-level.
-- You can select a project during the MCP session with set_active_project.
-- You can override scope per call by passing project_id where supported.
+- You can select a project during the MCP session with `set_active_project`.
+- You can override scope per call by passing `project_id` where supported.
 
 Recommended flow:
 
-1. Call get_workspace_context
-2. Call list_projects
-3. Call set_active_project
-4. Run handoff and query tools in the selected scope
+1. Call `get_workspace_context`
+2. Call `list_projects`
+3. Call `set_active_project`
+4. Call `list_filter_options` to inspect selectable resources
+5. Run handoff, insight, Q&A and query tools in the selected scope
 
 ## Local Development
 
@@ -96,16 +121,17 @@ npm pack
 
 ## Troubleshooting
 
-- Error: Missing FLOWRELAY_API_KEY
-  - Set FLOWRELAY_API_KEY in your MCP client configuration.
+- Error: Missing `FLOWRELAY_API_KEY`
+  - Set `FLOWRELAY_API_KEY` in your MCP client configuration.
 - Project not found or inaccessible
-  - Run list_projects and use one of the returned IDs.
+  - Run `list_projects` and use one of the returned IDs.
 - No events or handoffs returned
   - Verify active scope and data availability in that scope.
 
 ## Related Docs
 
 - Documentation & Platform: https://www.flowrelay.it
+- MCP Documentation: https://www.flowrelay.it/docs/mcp
 
 ## License
 

package/dist/index.js

@@ -50,13 +50,22 @@ const SOURCES = [
     'grafana',
     'google_calendar',
     'google_drive',
+    'launchdarkly',
+    'hcp_terraform',
+    'sonarqube',
+    'miro',
+    'new_relic',
+    'jira_service_management',
+    'posthog',
+    'hubspot',
+    'salesforce',
 ];
 const SourceEnum = z.enum(SOURCES);
 const SourceFilterSchema = z.object({
     projects: z.array(z.string()).optional().describe('Resource ids from list_filter_options[source].projects (repos, channels, boards). Use the exact id, not the display label.'),
     eventTypes: z.array(z.string()).optional().describe('Event-type values from list_filter_options (e.g. "push", "issue_created"). Case-sensitive; provider-driven. A value that does not exist matches no events (it is not rejected).'),
     branches: z.array(z.string()).optional().describe('Git branch names (e.g. "main", "develop") – git sources only (github, gitlab, bitbucket, azure_devops). Using this on a non-git source is a 400.'),
-    priorities: z.array(z.string()).optional().describe('Priority values from list_filter_options (e.g. "high", "urgent") – jira, linear, sentry, pagerduty, incident_io, clickup, zendesk, snyk, grafana only. Using this on another source is a 400; unrecognized values simply match no events.'),
+    priorities: z.array(z.string()).optional().describe('Priority values from list_filter_options (e.g. "high", "urgent") – jira, jira_service_management, linear, sentry, pagerduty, incident_io, clickup, zendesk, snyk, grafana, new_relic, hubspot, salesforce only. Using this on another source is a 400; unrecognized values simply match no events.'),
 });
 const FiltersSchema = z.record(z.string(), SourceFilterSchema)
     .optional()

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@flowrelay/mcp-server",
-  "version": "1.0.22",
+  "version": "1.0.24",
   "description": "Flow Relay MCP Server for Claude Desktop and Claude Code – handoffs, integrations and context events via natural conversation.",
   "type": "module",
   "license": "AGPL-3.0-or-later",