Invite people, agents, and devices
Use Client Explorer group invitations for membership, then issue governed runtime keys from ThisMCP™.
Easy Setup
Make MCP onboarding consistent enough for IT and simple enough for every team member.
ThisMCP™ keeps onboarding simple: invite through Client Explorer, then govern runtime MCP access through user-bound gateway keys.
Onboarding should use the identity system your team already trusts, then apply gateway policy at runtime.
- Client Explorer remains the source of truth for membership and invitations.
- ThisMCP™ access keys are issued only after a user is a Client Explorer group member.
- Gateway policy still filters discovery, requests, responses, approvals, budgets, and capsules.
Runtime access
Invite becomes a working environment.
Each participant gets runtime access that matches their role, client, capsule, and policy state.
Invite accepted
Machine-readable endpoint settings
Environment checked
Client, credentials, local services
Runtime handed off
Group or capsule endpoint issued
Benefits
What changes for the team.
Issue governed access
Runtime keys stay bound to Client Explorer users, local roles, approval rules, capsules, and manifest state.
Use local resources first
Prefer available local, peer, and deterministic resources before spending cloud API calls or model tokens when policy allows.
Next Step