flowstate-mcp-client Package Skill

Package: @epicdm/flowstate-mcp-client Repository: epic-flowstate-community Path: packages/flowstate-mcp-client Version: 1.0.7

Use this published Dojo skill as the package-level entrypoint. For detailed workflows, use the package-local skills listed below.

Primary Package Workflow

MCP Client Consumer Integration

Use this skill when another package wraps or embeds MCPClient.

Integration Pattern

Construct the client with the active base URL and bearer token.
Use health() or a lightweight tool list check for availability.
Cache listTools() results in the consumer if provider conversion is expensive.
Use callTool() for execution and preserve MCPClientError details where possible.
Call updateAuthToken() after token refresh instead of constructing a stale client.

Known Consumer

mcp-web-transport uses this package to cache tool definitions, convert them to provider tool shapes, execute tools, and check availability.

Pitfalls

The client returns unwrapped tool result, not the full server envelope.
Tool schemas are typed as any; consumers that need provider-specific strictness must validate or normalize schemas themselves.
console.log in the client is visible to consumers.
Do not use this package for /mcp Streamable HTTP integration.

Package Skill Inventory

Package Skill Inventory: @epicdm/flowstate-mcp-client

Skill Map

Skill	Type	Trigger	Teaches	Dojo
`flowstate-mcp-client`	orchestrator	Use when integrating, changing, testing, or documenting this package	When to use the client, route to REST/error/consumer/maintenance skills	local-only
`flowstate-mcp-client-rest-transport`	workflow	Use when calling FlowState MCP REST endpoints through `MCPClient`	`baseUrl`, `listTools`, `callTool`, `health`, auth token, timeout, URL encoding	ready-after-review
`flowstate-mcp-client-error-handling`	workflow/reference	Use when handling HTTP errors, tool failures, timeouts, and response envelopes	`MCPClientError`, method-specific status preservation, response shapes	ready-after-review
`flowstate-mcp-client-consumer-integration`	workflow	Use when wiring into `mcp-web-transport` or other UI/runtime packages	Tool caching, availability checks, provider tool conversion, token refresh	ready-after-review
`flowstate-mcp-client-contract-maintenance`	maintenance	Use before changing exports, types, endpoint paths, timeout/auth behavior, docs, or Dojo	Verification, mocked-fetch tests, docs drift, downstream references	local-only

Anti-Sprawl Decision

Do not create one skill per exported type. The package has one primary class and a few contract risks, so five compact skills cover the real workflows.

Deferred Skills

Streamable MCP HTTP protocol skill: defer because this client intentionally calls custom REST endpoints.
Dedicated browser auth skill: defer to consuming packages unless this package adds token refresh flows.
One skill per endpoint: fold into rest-transport.

Review Gate

Package Skills Review: @epicdm/flowstate-mcp-client

Verdict

Pass with fixes.

The skillset is intentionally small and teaches the REST client contract instead of listing exported symbols.

Findings

Severity	Skill	Issue	Evidence	Required Fix
Important	error-handling	`listTools()` and `health()` can collapse original HTTP errors into status `500`	`src/client.ts`	Document now; fix before promising status fidelity
Important	maintenance	Tests do not validate fetch behavior, headers, URL encoding, timeout, or error envelopes	`src/__tests__/client.test.ts`	Add mocked-fetch tests before Dojo publish
Important	docs	README/docs use stale scope/version/consumer information	README, `.flowstate/docs`	Update docs before publish
Minor	transport	Package is REST-only, not MCP `/mcp` Streamable HTTP	source/http server contract	Keep explicit in skills

Verification

Review worker ran:

yarn workspace @epicdm/flowstate-mcp-client test --runInBand
yarn workspace @epicdm/flowstate-mcp-client typecheck

Results:

Tests passed.
Typecheck passed.
Lint passed with 7 existing warnings: loose any, console logging, and one unused test import.
Build passed.

Dojo Publication Decision

Do not publish existing generated .flowstate/dojo artifacts. Rebuild from these reviewed workflow skills after mocked-fetch contract coverage is added or explicitly deferred.

flowstate-epic-flowstate-community-epicdm-flowstate-mcp-client

Tags

Publisher

Versions

Skill