@flowrelay/mcp-server 1.7.0 → 1.8.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +14 -3
- package/dist/api.d.ts +22 -0
- package/dist/api.js +21 -0
- package/dist/server.js +125 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -11,7 +11,7 @@ It connects to Flow Relay API v1 using an API key and supports:
|
|
|
11
11
|
## Package
|
|
12
12
|
|
|
13
13
|
- Name: @flowrelay/mcp-server
|
|
14
|
-
- Version: 1.
|
|
14
|
+
- Version: 1.8.0
|
|
15
15
|
|
|
16
16
|
## Supported Sources (52 Integrations)
|
|
17
17
|
|
|
@@ -32,7 +32,7 @@ Flow Relay MCP Server supports 52 integration sources across the entire engineer
|
|
|
32
32
|
|
|
33
33
|
## What Is Included
|
|
34
34
|
|
|
35
|
-
The server currently exposes
|
|
35
|
+
The server currently exposes 40 tools, 3 prompts and 1 resource template. Every tool carries the four MCP annotations (`readOnlyHint`, `destructiveHint`, `idempotentHint`, `openWorldHint`): the `list_*` and `get_*` tools are read-only and idempotent, the `generate_*` tools (including `generate_plan_review`), `ask_project`, `create_work_item`, `create_raid_entry`, `resolve_suggestion`, `decide_approval`, `request_change` and `discord_send_message` are non-idempotent (each call spends credits, creates an item or an entry, files a request, decides one or posts a message), `update_work_item` and `link_evidence` write but are idempotent (the same values twice leave the item unchanged) and `delete_work_item` is the one destructive tool (`destructiveHint: true`, so clients can ask before it runs; the deletion can be restored from the change history).
|
|
36
36
|
|
|
37
37
|
- `get_workspace_context`: Show current Flow Relay context (account mode, organizations count, accessible projects count, active project scope and caller role).
|
|
38
38
|
- `list_projects`: List every accessible project (personal and organization) with id, scope, role and the prefix of its work item keys.
|
|
@@ -69,9 +69,20 @@ The server currently exposes 36 tools. Every tool carries the four MCP annotatio
|
|
|
69
69
|
- `apply_template`: Add a saved template to a plan, at the top level or under an item key. Project managers only.
|
|
70
70
|
- `list_approvals`: List the change requests of a plan: what was asked in plain language, who asked, who decided and what they said. Business plan and above, organization projects.
|
|
71
71
|
- `request_change`: Ask for a change to an item (status, progress, priority, blocked flag, duration or deadline) that a second person must approve. It only files the request; approving applies it. Business plan and above, organization projects.
|
|
72
|
+
- `resolve_suggestion`: Accept or dismiss one pending suggestion from `list_suggestions`. Accepting applies it to the plan as the key owner.
|
|
73
|
+
- `create_raid_entry`: Add a risk, assumption, issue, decision or dependency to the register of a plan, with optional probability and impact from 1 to 5, response and due date.
|
|
74
|
+
- `delete_work_item`: Delete a work item and everything under it. One batch in the change history, so a project manager can restore it. Contributors can delete only items they created.
|
|
75
|
+
- `decide_approval`: Approve, reject or withdraw a change request from `list_approvals`. A request needs a second person; only its author can withdraw it.
|
|
72
76
|
- `generate_plan_review`: Write a status report for a project plan (progress, concerns, milestone outlook, suggested register entries, next steps) from numbers the scheduler computed and the last 14 days of linked activity. Returns Markdown. Costs 5 credits per run.
|
|
73
77
|
|
|
74
|
-
Work item tools, `list_raid`, `get_earned_value`, `get_portfolio`, `get_forecast`, `list_automations`, `list_templates`, `apply_template`, `list_approvals` and `request_change` cost no credits. Dates are wall-clock times in the plan time zone (`YYYY-MM-DDTHH:mm`), which every reply names. Contributors can create items when the project allows it, assign only themselves and update the items assigned to them or created by them; schedule changes may need a project manager. A commit message, branch name or pull request title that mentions an item key (`FR-12`) is linked to that item as evidence. Items mirrored from Jira, Linear or GitHub Issues also answer to the key the tracker gave them (`PAY-123`, `acme/web#42`).
|
|
78
|
+
Work item tools, `resolve_suggestion`, `create_raid_entry`, `delete_work_item`, `decide_approval`, `list_raid`, `get_earned_value`, `get_portfolio`, `get_forecast`, `list_automations`, `list_templates`, `apply_template`, `list_approvals` and `request_change` cost no credits. Dates are wall-clock times in the plan time zone (`YYYY-MM-DDTHH:mm`), which every reply names. Contributors can create items when the project allows it, assign only themselves and update the items assigned to them or created by them; schedule changes may need a project manager. A commit message, branch name or pull request title that mentions an item key (`FR-12`) is linked to that item as evidence. Items mirrored from Jira, Linear or GitHub Issues also answer to the key the tracker gave them (`PAY-123`, `acme/web#42`).
|
|
79
|
+
|
|
80
|
+
### Prompts and resources
|
|
81
|
+
|
|
82
|
+
- `handoff_for_branch` (argument `branch`): finds the git sources that carry the branch and generates a handoff limited to it.
|
|
83
|
+
- `onboard_me` (arguments `role`, optional `focus`): reads the existing insights first and generates an onboarding brief only when none fits.
|
|
84
|
+
- `weekly_status`: writes a short status update from the plan, the register and the last days of activity.
|
|
85
|
+
- Resource template `flowrelay://projects/{project_id}/handoffs/latest`: the latest active handoff of a project as Markdown.
|
|
75
86
|
|
|
76
87
|
### Filter Dimensions
|
|
77
88
|
|
package/dist/api.d.ts
CHANGED
|
@@ -277,6 +277,16 @@ export interface RaidQuery {
|
|
|
277
277
|
status?: string;
|
|
278
278
|
limit?: number;
|
|
279
279
|
}
|
|
280
|
+
export interface RaidInput {
|
|
281
|
+
kind: 'risk' | 'assumption' | 'issue' | 'decision' | 'dependency';
|
|
282
|
+
title: string;
|
|
283
|
+
description?: string;
|
|
284
|
+
status?: 'open' | 'monitoring' | 'closed';
|
|
285
|
+
probability?: number;
|
|
286
|
+
impact?: number;
|
|
287
|
+
response?: string;
|
|
288
|
+
dueOn?: string;
|
|
289
|
+
}
|
|
280
290
|
export interface ScheduleForecast {
|
|
281
291
|
mode: 'schedule';
|
|
282
292
|
uncertainty: string;
|
|
@@ -569,4 +579,16 @@ export declare class FlowRelayAPI {
|
|
|
569
579
|
id: string;
|
|
570
580
|
status: string;
|
|
571
581
|
}>;
|
|
582
|
+
resolveSuggestion(projectId: string, suggestionId: string, action: 'accept' | 'dismiss'): Promise<{
|
|
583
|
+
status?: string;
|
|
584
|
+
}>;
|
|
585
|
+
createRaidEntry(projectId: string, input: RaidInput): Promise<{
|
|
586
|
+
id: string;
|
|
587
|
+
number: number;
|
|
588
|
+
}>;
|
|
589
|
+
deleteWorkItem(projectId: string, ref: string): Promise<void>;
|
|
590
|
+
decideApproval(projectId: string, approvalId: string, decision: 'approve' | 'reject' | 'withdraw', note?: string): Promise<{
|
|
591
|
+
status: string;
|
|
592
|
+
batchId?: string;
|
|
593
|
+
}>;
|
|
572
594
|
}
|
package/dist/api.js
CHANGED
|
@@ -231,4 +231,25 @@ export class FlowRelayAPI {
|
|
|
231
231
|
body: JSON.stringify(input),
|
|
232
232
|
});
|
|
233
233
|
}
|
|
234
|
+
async resolveSuggestion(projectId, suggestionId, action) {
|
|
235
|
+
return this.request(`/projects/${projectId}/suggestions/${encodeURIComponent(suggestionId)}`, {
|
|
236
|
+
method: 'POST',
|
|
237
|
+
body: JSON.stringify({ action }),
|
|
238
|
+
});
|
|
239
|
+
}
|
|
240
|
+
async createRaidEntry(projectId, input) {
|
|
241
|
+
return this.request(`/projects/${projectId}/raid`, {
|
|
242
|
+
method: 'POST',
|
|
243
|
+
body: JSON.stringify(input),
|
|
244
|
+
});
|
|
245
|
+
}
|
|
246
|
+
async deleteWorkItem(projectId, ref) {
|
|
247
|
+
await this.request(`/projects/${projectId}/work-items/${encodeURIComponent(ref)}`, { method: 'DELETE' });
|
|
248
|
+
}
|
|
249
|
+
async decideApproval(projectId, approvalId, decision, note) {
|
|
250
|
+
return this.request(`/projects/${projectId}/approvals/${encodeURIComponent(approvalId)}`, {
|
|
251
|
+
method: 'PATCH',
|
|
252
|
+
body: JSON.stringify(note ? { decision, note } : { decision }),
|
|
253
|
+
});
|
|
254
|
+
}
|
|
234
255
|
}
|
package/dist/server.js
CHANGED
|
@@ -4,7 +4,7 @@
|
|
|
4
4
|
* Copyright (c) 2026 Adriano Sorbello (atrisorb) <https://github.com/atrisorb>
|
|
5
5
|
* Licensed under GNU Affero General Public License v3.0 or later (AGPL-3.0-or-later)
|
|
6
6
|
*/
|
|
7
|
-
import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
|
|
7
|
+
import { McpServer, ResourceTemplate } from '@modelcontextprotocol/sdk/server/mcp.js';
|
|
8
8
|
import { z } from 'zod';
|
|
9
9
|
import { createRequire } from 'node:module';
|
|
10
10
|
export const PKG_VERSION = createRequire(import.meta.url)('../package.json').version;
|
|
@@ -77,6 +77,7 @@ const READ_ONLY = { readOnlyHint: true, destructiveHint: false, idempotentHint:
|
|
|
77
77
|
const MUTATING = { readOnlyHint: false, destructiveHint: false, idempotentHint: false, openWorldHint: true };
|
|
78
78
|
const SESSION_STATE = { readOnlyHint: false, destructiveHint: false, idempotentHint: true, openWorldHint: false };
|
|
79
79
|
const WRITE_IDEMPOTENT = { readOnlyHint: false, destructiveHint: false, idempotentHint: true, openWorldHint: true };
|
|
80
|
+
const DESTRUCTIVE = { readOnlyHint: false, destructiveHint: true, idempotentHint: true, openWorldHint: true };
|
|
80
81
|
export function normalizeProjectId(value) {
|
|
81
82
|
if (typeof value !== 'string')
|
|
82
83
|
return null;
|
|
@@ -261,7 +262,9 @@ export function createFlowRelayServer(api, initialProjectId) {
|
|
|
261
262
|
'',
|
|
262
263
|
'Cost: every generate_* call consumes credits from the user\'s plan and is charged once on success (architecture is the deepest and most expensive, handoff the cheapest). Do not regenerate an artifact you can retrieve with list_handoffs / list_insights, and confirm intent before generating repeatedly.',
|
|
263
264
|
'',
|
|
264
|
-
'Work items: a project plan holds tasks and milestones addressed by keys such as FR-12. list_my_work shows what is assigned to the caller, list_work_items and get_work_item read a plan, create_work_item and update_work_item change it, list_suggestions shows the changes Flow Relay proposes from linked activity and link_evidence attaches a link to an item, list_raid reads the risk register, get_earned_value reads costs and earned value against a baseline and get_portfolio reads the progress, forecast, risks and health of every project of an organization, get_forecast simulates a plan to say how likely each finish date is and plan_whatif tries a what-if question on a copy of the plan (5 credits). list_automations reads the rules that act on a plan by themselves, list_templates and apply_template add saved structure to a plan, list_approvals reads the change requests of a plan and request_change asks for a change that a second person must approve. Work item tools cost no credits; generate_plan_review writes a status report from the numbers of the plan (5 credits). A commit message, branch name or pull request title that mentions an item key links that work to the item.',
|
|
265
|
+
'Work items: a project plan holds tasks and milestones addressed by keys such as FR-12. list_my_work shows what is assigned to the caller, list_work_items and get_work_item read a plan, create_work_item and update_work_item change it, list_suggestions shows the changes Flow Relay proposes from linked activity and link_evidence attaches a link to an item, list_raid reads the risk register, get_earned_value reads costs and earned value against a baseline and get_portfolio reads the progress, forecast, risks and health of every project of an organization, get_forecast simulates a plan to say how likely each finish date is and plan_whatif tries a what-if question on a copy of the plan (5 credits). list_automations reads the rules that act on a plan by themselves, list_templates and apply_template add saved structure to a plan, list_approvals reads the change requests of a plan and request_change asks for a change that a second person must approve. resolve_suggestion accepts or dismisses one of those suggestions, create_raid_entry adds an entry to the register, delete_work_item removes an item and everything under it (a project manager can restore it from the change history) and decide_approval approves, rejects or withdraws a change request. Work item tools cost no credits; generate_plan_review writes a status report from the numbers of the plan (5 credits). A commit message, branch name or pull request title that mentions an item key links that work to the item.',
|
|
266
|
+
'',
|
|
267
|
+
'Prompts: handoff_for_branch, onboard_me and weekly_status start the usual flows. The resource flowrelay://projects/{project_id}/handoffs/latest holds the latest handoff of a project as Markdown.',
|
|
265
268
|
'',
|
|
266
269
|
'Scope and access follow the API key\'s tenant role; a tool only ever sees projects the key can access.',
|
|
267
270
|
].join('\n'),
|
|
@@ -1085,5 +1088,125 @@ export function createFlowRelayServer(api, initialProjectId) {
|
|
|
1085
1088
|
return { content: [{ type: 'text', text: `Could not send the change request: ${err.message}` }] };
|
|
1086
1089
|
}
|
|
1087
1090
|
});
|
|
1091
|
+
server.tool('resolve_suggestion', 'Accept or dismiss one pending suggestion from list_suggestions. Accepting applies it to the plan as the key owner: a status change, a new item, a dependency or an evidence link. Dismissing hides it. Accepting changes the plan, so confirm with the user first. Free: no credits.', {
|
|
1092
|
+
suggestion_id: z.string().min(1).describe('Suggestion id from list_suggestions.'),
|
|
1093
|
+
action: z.enum(['accept', 'dismiss']).describe('accept applies the suggestion to the plan, dismiss hides it.'),
|
|
1094
|
+
project_id: z.string().optional().describe('Project id from list_projects. Omit to use the active project.'),
|
|
1095
|
+
}, MUTATING, async ({ suggestion_id, action, project_id }) => {
|
|
1096
|
+
try {
|
|
1097
|
+
const resolved = await requireProject(project_id);
|
|
1098
|
+
const { status } = await api.resolveSuggestion(resolved.projectId, suggestion_id, action);
|
|
1099
|
+
return { content: [{ type: 'text', text: `Suggestion ${suggestion_id} ${status ?? (action === 'accept' ? 'accepted' : 'dismissed')} in ${resolved.project.name}.` }] };
|
|
1100
|
+
}
|
|
1101
|
+
catch (err) {
|
|
1102
|
+
return { content: [{ type: 'text', text: `Could not resolve the suggestion: ${err.message}` }] };
|
|
1103
|
+
}
|
|
1104
|
+
});
|
|
1105
|
+
server.tool('create_raid_entry', 'Add an entry to the RAID register of a project plan: a risk, assumption, issue, decision or dependency. Probability and impact are scores from 1 to 5 and their product is the score list_raid shows. Viewers cannot add. Free: no credits.', {
|
|
1106
|
+
kind: z.enum(['risk', 'assumption', 'issue', 'decision', 'dependency']).describe('What the entry is.'),
|
|
1107
|
+
title: z.string().min(1).max(300).describe('Short title of the entry.'),
|
|
1108
|
+
description: z.string().max(10000).optional().describe('Details of the entry.'),
|
|
1109
|
+
status: z.enum(['open', 'monitoring', 'closed']).optional().describe('Status (default open).'),
|
|
1110
|
+
probability: z.number().int().min(1).max(5).optional().describe('How likely it is, 1 rare to 5 almost certain.'),
|
|
1111
|
+
impact: z.number().int().min(1).max(5).optional().describe('How much it matters, 1 minor to 5 severe.'),
|
|
1112
|
+
response: z.string().max(5000).optional().describe('The planned response or mitigation.'),
|
|
1113
|
+
due_on: z.string().optional().describe('Due date as YYYY-MM-DD.'),
|
|
1114
|
+
project_id: z.string().optional().describe('Project id from list_projects. Omit to use the active project.'),
|
|
1115
|
+
}, MUTATING, async ({ kind, title, description, status, probability, impact, response, due_on, project_id }) => {
|
|
1116
|
+
try {
|
|
1117
|
+
const resolved = await requireProject(project_id);
|
|
1118
|
+
const created = await api.createRaidEntry(resolved.projectId, { kind, title, description, status, probability, impact, response, dueOn: due_on });
|
|
1119
|
+
return { content: [{ type: 'text', text: `Added ${kind} #${created.number} to the register of ${resolved.project.name}: ${title}` }] };
|
|
1120
|
+
}
|
|
1121
|
+
catch (err) {
|
|
1122
|
+
return { content: [{ type: 'text', text: `Could not add the register entry: ${err.message}` }] };
|
|
1123
|
+
}
|
|
1124
|
+
});
|
|
1125
|
+
server.tool('delete_work_item', 'Delete a work item and everything under it from a project plan: its sub-items, dependencies and assignments leave the plan and the plan is rescheduled. The deletion is recorded as one batch in the change history, so a project manager can restore it in Flow Relay. Contributors can delete only items they created. Confirm with the user before calling it. Free: no credits.', {
|
|
1126
|
+
ref: z.string().min(1).max(100).describe('Item key such as FR-12, or the item id.'),
|
|
1127
|
+
project_id: z.string().optional().describe('Project id from list_projects. Omit to use the active project.'),
|
|
1128
|
+
}, DESTRUCTIVE, async ({ ref, project_id }) => {
|
|
1129
|
+
try {
|
|
1130
|
+
const resolved = await requireProject(project_id);
|
|
1131
|
+
await api.deleteWorkItem(resolved.projectId, ref);
|
|
1132
|
+
return { content: [{ type: 'text', text: `Deleted ${ref} from ${resolved.project.name}. A project manager can restore it from the change history.` }] };
|
|
1133
|
+
}
|
|
1134
|
+
catch (err) {
|
|
1135
|
+
return { content: [{ type: 'text', text: `Could not delete the work item: ${err.message}` }] };
|
|
1136
|
+
}
|
|
1137
|
+
});
|
|
1138
|
+
server.tool('decide_approval', 'Approve, reject or withdraw a change request listed by list_approvals. Approving applies the requested change to the plan as the approver. A request needs a second person: you cannot approve or reject a request you made, and only its author can withdraw it. Confirm with the user before approving. Free: no credits.', {
|
|
1139
|
+
approval_id: z.string().min(1).describe('Change request id from list_approvals.'),
|
|
1140
|
+
decision: z.enum(['approve', 'reject', 'withdraw']).describe('approve applies the change, reject refuses it, withdraw cancels your own request.'),
|
|
1141
|
+
note: z.string().max(1000).optional().describe('Why, shown to the other person.'),
|
|
1142
|
+
project_id: z.string().optional().describe('Project id from list_projects. Omit to use the active project.'),
|
|
1143
|
+
}, MUTATING, async ({ approval_id, decision, note, project_id }) => {
|
|
1144
|
+
try {
|
|
1145
|
+
const resolved = await requireProject(project_id);
|
|
1146
|
+
const { status } = await api.decideApproval(resolved.projectId, approval_id, decision, note);
|
|
1147
|
+
return { content: [{ type: 'text', text: `Change request ${approval_id} in ${resolved.project.name} is now ${status}.` }] };
|
|
1148
|
+
}
|
|
1149
|
+
catch (err) {
|
|
1150
|
+
return { content: [{ type: 'text', text: `Could not decide the change request: ${err.message}` }] };
|
|
1151
|
+
}
|
|
1152
|
+
});
|
|
1153
|
+
server.registerPrompt('handoff_for_branch', {
|
|
1154
|
+
title: 'Handoff for a branch',
|
|
1155
|
+
description: 'Generate a handoff limited to one git branch and present it.',
|
|
1156
|
+
argsSchema: { branch: z.string().describe('Branch name such as main or feature/login.') },
|
|
1157
|
+
}, ({ branch }) => ({
|
|
1158
|
+
messages: [
|
|
1159
|
+
{
|
|
1160
|
+
role: 'user',
|
|
1161
|
+
content: {
|
|
1162
|
+
type: 'text',
|
|
1163
|
+
text: `Write a handoff for the branch "${branch}" of the active Flow Relay project. Use set_active_project first if no project is active (list_projects shows the choices). Call list_filter_options and find every git source (github, gitlab, bitbucket, azure_devops) whose branches include "${branch}". Then call generate_handoff with filters that limit each of those sources to that branch. Present the finished handoff as Markdown and name the sources it covered. If no source carries the branch, say so and do not generate.`,
|
|
1164
|
+
},
|
|
1165
|
+
},
|
|
1166
|
+
],
|
|
1167
|
+
}));
|
|
1168
|
+
server.registerPrompt('onboard_me', {
|
|
1169
|
+
title: 'Onboard me to a project',
|
|
1170
|
+
description: 'Generate an onboarding brief tailored to a role and a focus area.',
|
|
1171
|
+
argsSchema: {
|
|
1172
|
+
role: z.string().describe('The role of the person being onboarded, for example backend engineer.'),
|
|
1173
|
+
focus: z.string().optional().describe('The repository or feature area they will work on.'),
|
|
1174
|
+
},
|
|
1175
|
+
}, ({ role, focus }) => ({
|
|
1176
|
+
messages: [
|
|
1177
|
+
{
|
|
1178
|
+
role: 'user',
|
|
1179
|
+
content: {
|
|
1180
|
+
type: 'text',
|
|
1181
|
+
text: `Onboard me to the active Flow Relay project as a ${role}${focus ? ` focused on ${focus}` : ''}. Use set_active_project first if no project is active (list_projects shows the choices). Check list_insights for a recent onboarding brief before spending credits. If none fits, call generate_onboarding_brief with new_member_role "${role}"${focus ? ` and focus_area "${focus}"` : ''}. Present the brief as Markdown and end with the three things I should read first.`,
|
|
1182
|
+
},
|
|
1183
|
+
},
|
|
1184
|
+
],
|
|
1185
|
+
}));
|
|
1186
|
+
server.registerPrompt('weekly_status', {
|
|
1187
|
+
title: 'Weekly status',
|
|
1188
|
+
description: 'Summarize the week of the active project from its plan and its activity.',
|
|
1189
|
+
}, () => ({
|
|
1190
|
+
messages: [
|
|
1191
|
+
{
|
|
1192
|
+
role: 'user',
|
|
1193
|
+
content: {
|
|
1194
|
+
type: 'text',
|
|
1195
|
+
text: 'Write a status update for the week of the active Flow Relay project. Use set_active_project first if no project is active (list_projects shows the choices). Read list_work_items for the plan, list_raid for open risks and list_events for the last days of activity. Say what moved, what is blocked, what is at risk and what comes next, using item keys such as FR-12. Do not guess dates: take them from the plan. Keep it under 250 words.',
|
|
1196
|
+
},
|
|
1197
|
+
},
|
|
1198
|
+
],
|
|
1199
|
+
}));
|
|
1200
|
+
server.registerResource('latest_handoff', new ResourceTemplate('flowrelay://projects/{project_id}/handoffs/latest', { list: undefined }), {
|
|
1201
|
+
title: 'Latest handoff',
|
|
1202
|
+
description: 'The latest active handoff of a project, rendered as Markdown.',
|
|
1203
|
+
mimeType: 'text/markdown',
|
|
1204
|
+
}, async (uri, { project_id }) => {
|
|
1205
|
+
const { handoffs } = await api.listHandoffs('active', 1, String(project_id));
|
|
1206
|
+
const handoff = handoffs[0];
|
|
1207
|
+
if (!handoff)
|
|
1208
|
+
throw new Error(`No active handoff in project ${String(project_id)}.`);
|
|
1209
|
+
return { contents: [{ uri: uri.href, mimeType: 'text/markdown', text: handoff.markdown ?? `# ${handoff.title}\n\n${handoff.summary}\n` }] };
|
|
1210
|
+
});
|
|
1088
1211
|
return server;
|
|
1089
1212
|
}
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@flowrelay/mcp-server",
|
|
3
|
-
"version": "1.
|
|
3
|
+
"version": "1.8.0",
|
|
4
4
|
"description": "Flow Relay MCP Server for Claude Desktop and Claude Code – handoffs, integrations and context events via natural conversation.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"license": "AGPL-3.0-or-later",
|