@capxul/mcp 4.20.0-beta.5 → 4.20.0-beta.7

package/README.md

@@ -39,16 +39,16 @@ stderr.
 | `onboarding.completeOrganization` | `org:manage`    | Claim the Account, then create or resume an Organization.       |
 | `me.get`                          | `account:read`  | Read the signed-in person's profile.                            |
 | `account.status`                  | `account:read`  | Where the account is on the readiness ladder.                   |
-| `account.balance`                 | `account:read`  | Balance and available balance.                                  |
+| `account.balance`                 | `account:read`  | Exact positions and nullable single-asset amounts.              |
 | `org.list`                        | `org:manage`    | List accessible Organizations.                                  |
-| `org.roles`                       | `org:manage`    | List valid invitation role labels.                              |
+| `org.roles`                       | `org:manage`    | List active Organization role labels.                           |
 | `org.members`                     | `org:manage`    | Read member lifecycle states.                                   |
-| `org.invite`                      | `org:manage`    | Invite one Person by email and role.                            |
-| `org.acceptInvitations`           | `org:manage`    | Accept invitations for the signed-in email.                     |
-| `org.activateMember`              | `org:manage`    | Submit the verified role grant for a ready member Account.      |
 
 Prompts, resources, and the money tools arrive in a later slice.
 
+`org.members` returns each member's attached `accountId`. Pending members
+without an Account remain visible with `accountId: null`.
+
 When `POSTHOG_PROJECT_TOKEN` is set, PostHog MCP Analytics adds two fields to
 every tool schema. `context` is required. The server converts it to a safe
 journey category before capture. `conversation_id` is optional. The server
@@ -72,11 +72,8 @@ once and consents to the scopes; the agent presents the token after that. Call
 exercise this path. The hosted live service fails closed until the browser
 approval handoff lands.
 
-The staff journey is `org.roles` → `org.invite` → invitee Person onboarding →
-`org.acceptInvitations` → founder `org.activateMember` → poll `org.members`
-until `active`. The invitee supplies their ready `accountId` from
-`account.status`. Activation uses the existing verified Permission execution
-and needs the founder signer. The other staff tools do not sign.
+Invitation authoring and digest-bound acceptance use the SDK or CLI. MCP exposes
+Organization and member reads but does not author or activate invitations.
 
 ## Environment
 
@@ -120,10 +117,11 @@ write. The hermetic MCP Analytics proof verifies identity, intent, and an
 echoed conversation across two stateless requests. The staging analytics
 receipt must pass before this slice is released.
 
-The three-phase staging staff harness also proves two isolated People, a ready
-Organization, invitation, staff Account onboarding, invitation acceptance,
-verified Permission assignment, and final active membership. The Base Sepolia
-assignment transaction is
+The historical three-phase staging staff harness, recorded before the MCP
+invitation tools were retired, proved two isolated People, a ready Organization,
+invitation, staff Account onboarding, invitation acceptance, verified Permission
+assignment, and final active membership. It does not describe the current MCP
+tool surface. The Base Sepolia assignment transaction is
 [`0x7e717946…48766d`](https://sepolia.basescan.org/tx/0x7e717946f87dac1345d9487806e5856d85a0f08e15fb11072af0c2311548766d).
 
 Read [CONTEXT.md](./CONTEXT.md) before adding a tool or changing the