@mgsoftwarebv/mcp-server-bridge 3.3.8 → 3.4.1

package/README.md

@@ -1,6 +1,6 @@
 # @mgsoftwarebv/mcp-server-bridge
 
-An MCP server that connects **Cursor / Claude Desktop / Windsurf** directly to your **Refront** Postgres database, exposing tickets, customers, projects, AI dev sessions and time tracking as MCP tools and resources.
+An MCP server that connects **Cursor / Claude Desktop / Windsurf** directly to your **Refront** Postgres database, exposing tickets, customers, projects, documents and time tracking as MCP tools and resources.
 
 Since v3.0 the bridge talks straight to Postgres via Drizzle ORM — the previous PostgREST/JWT transport has been removed.
 
@@ -88,7 +88,7 @@ How it resolves which provider a tool acts on:
 
 - **`teamId` provided** → it is validated against your memberships and used.
 - **`teamId` omitted, you belong to one provider** → that provider is used automatically (no change for single-provider users).
-- **`teamId` omitted, you belong to several** → list/create tools return the list of your providers and ask the AI to re-call with a `teamId`. By-id and session tools resolve across all your providers (the record id disambiguates), and accept `teamId` to narrow.
+- **`teamId` omitted, you belong to several** → list/create tools return the list of your providers and ask the AI to re-call with a `teamId`. By-id tools resolve across all your providers (the record id disambiguates), and accept `teamId` to narrow.
 
 Use **get-teams** to list the providers you can act on and copy a `teamId`.
 
@@ -126,17 +126,6 @@ Document text runs through a built-in **humanizer** that strips AI-sounding patt
 
 Optional PDF compilation: pass `compilePdf: true` to trigger the `compile-document-pdf` Trigger.dev job after create/update. This requires `TRIGGER_SECRET_KEY` (and optionally `TRIGGER_API_URL`) in the bridge `env`; without it the dashboard compiles the PDF when the document is opened or shared.
 
-### AI Development Tracking
-- **start-ai-session-smart** — start an AI dev session with time tracking
-- **track-manual-follow-up** — record a manual follow-up prompt and adjust the time estimate
-- **sync-session-todos** — replace/extend the todo list for a session
-- **add-follow-up-todos** — append todos that came up during follow-up
-- **update-session-status** — change the session status (`started`, `in_progress`, `paused`, `completed`, `failed`)
-- **get-session-context** — read back current session state (ticket, todos, follow-ups)
-- **get-completion-context** — full context bundle for generating a customer response
-- **save-customer-response** — store the AI-generated customer response for provider approval
-- **complete-ai-session** — finalize the session, create/update a draft agenda event
-
 ### Time Tracking
 - **log-hours** — log work hours as a draft agenda event (see the `/hours` Cursor command)