#82 — MCP server: the firm's own agents on the firm's own data
Expose Firmary to the firm's Claude/ChatGPT/agents via MCP. For a self-hosted platform this is a standout: the firm's agents act on their own data on their own infrastructure. Size: M. Source: product-roadmap.md §7.
4 Comments
·about 2 months agoAgent A — plan delivered (docs/product/mcp-server-plan.md, on dev at b806e3c). Moving to Under Review.
The one-paragraph version: one MCP endpoint in the same image (/api/mcp, Streamable HTTP), authenticated by the same agent principals as REST (#84) and managed like staff (#56) — so tenant fencing, roles, segment scoping, and audit all come from machinery that already exists; there is no 'MCP admin mode' by construction. Tool surface is CURATED (~12 read tools mirroring firm workflows + MCP resources for reference data), not a table dump — agents do better with 20 sharp tools than 200 endpoints. Writes arrive in Phase B as propose-only pending approvals (the concrete #83 guardrails mechanism), so 'chase the missing documents' becomes drafts a human approves. Self-host story: zero extra services, off by default, and the moat sentence stays literally true — the firm's agents act on the firm's data on the firm's infrastructure.
Decisions for you: M1–M5 in the doc (in-app vs sidecar, tool curation, transport fallback, the shared write-posture decision, and whether to market it as bring-your-own-AI).
·about 2 months agoAgent A claiming the PLAN you asked for (this card + its sibling — same headless goal, planned together so the REST and MCP surfaces share one principal/auth/authz story, interlocking with the agents-as-staff plan from #56). Deliverable: a design doc per card with explicit owner decisions; no code in this slice. Implementation of the webhooks piece stays deferred until Agent B?s in-flight migration lands (concurrent-migration stop condition). Started: 2026-07-09 07:25 America/Chicago.
·about 2 months ago@claude please create a plan for this using best practices. the goal is to be able to run the whole app headless if someone wants to
Migrated to https://github.com/Firmary/firmary-os/issues/382 during the 2026-08-23 GitHub migration (status corrections and full history carried over). Quackback is now the public user-feedback portal; internal tracking for this item continues on GitHub.