> For the complete documentation index, see [llms.txt](https://docs.trycaliber.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trycaliber.ai/using-caliber/for-practitioners.md). # For practitioners Practitioner surfaces: my usage, habit, Caliber MCP, and what managers can see. If your role is **member**, Caliber is mostly about **you**: your usage, your habit progress, and optional agent access via MCP. You do not get org-wide Home. ## My usage Open **My usage** / your person page (`/practitioners/` or `/me` redirects). You will see personal spend and activity signals for tools you use. ## Habit Habit level, XP, and quests live on your person experience (and `/habit` redirects to your own page). Weekly habit digests can arrive in Slack when your org connected Slack and digests are enabled. ## Caliber MCP Install Caliber into Cursor or Claude agents from **Connect → MCP** (`/connect/mcp`). Agents query Caliber with **the same visibility you have** when signed in. Members only see their own data through MCP; admins see org-wide tools. ## What my manager can see about me Depending on your org’s setup, team leads and admins can see aggregates and person-level usage for people in their scope: spend, activity, tool membership that drives seat cost, delivery signals, and (if Analysis is enrolled) transcript-derived workflow signals used for coaching or policy review. They cannot use Caliber Slack integration to read your Slack DMs or channel history. Provider connectors do not pull IDE file contents via GitHub’s stated connect policy. If Analysis / abusive-use screening is enabled for enrolled users, policy review may include redacted transcript content. Ask your admin whether your org enrolled that path. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.trycaliber.ai/using-caliber/for-practitioners.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.