Appearance
MCP scope and tool reference
The 28 October 2026 hosted release advertises 66 read-only tools and 35 scope areas. Start with the connection guide. Each call intersects its stored scope with current role, project, record-owner and module/plan checks. A listed role permission qualifies the area; native services can require additional rights. No wildcard scope grants every tool.
get_workspace is available to any valid connection and reports its single bound workspace. The other 65 tools are mapped below. Existing grants acquire no new scope keys automatically. New tools added within a granted area use that area's existing consent.
Portfolio and planning
| Scope | Qualifying current permission(s) | Read tools |
|---|---|---|
projects.read — Projects and overview | project.view | list_projects, get_project, get_project_overview |
portfolios.read — Portfolios | portfolio.view | list_portfolios, get_portfolio |
programmes.read — Programmes | programme.view | list_programmes, get_programme |
tasks.read — Tasks and dependencies | task.view | list_tasks, get_task, list_task_dependencies |
milestones.read — Milestones | project.view | list_milestones, get_milestone |
dependencies.read — Cross-project handoffs | project.view | list_project_dependencies |
Registers and governance
| Scope | Qualifying current permission(s) | Read tools |
|---|---|---|
exceptions.read — Exceptions | project.view | list_exceptions |
risks.read — Risks | risk.view | list_risks, get_risk |
issues.read — Issues | issue.view | list_issues, get_issue |
challenges.read — Challenges | challenge.view | list_challenges, get_challenge |
changes.read — Change control | changerequest.view | list_change_requests, get_change_request |
documents.read — Documents and evidence metadata | document.view | list_documents, get_document |
stakeholders.read — Stakeholders and contacts | stakeholder.view | list_stakeholders |
gates.read — Stage gates and requirements | project.view | get_gate_target, get_document_requirements |
Finance and reporting
| Scope | Qualifying current permission(s) | Read tools |
|---|---|---|
finance.read — Project financial records | payment.view | get_project_finance, get_project_cashflow, list_project_payables, get_financial_report |
workload.read — Workload and allocations | project.view | get_project_workload |
reports.read — Reports and analytics | reports.view | get_report_headlines, get_report |
pmo.read — Issued PMO reports and decisions | reports.view | list_issued_pmo_packs, get_issued_pmo_pack, get_issued_pmo_decisions |
Delivery intelligence
| Scope | Qualifying current permission(s) | Read tools |
|---|---|---|
history.read — Recorded delivery history | history.view | list_project_history |
baselines.read — Initial baseline records | task.view | list_initial_baselines, get_initial_baseline |
progress.read — Progress submissions | task.view | list_progress_submissions, get_progress_submission |
watches.read — Your watches and visible cards | watch.view | list_watches, list_watch_cards |
reviews.read — Issued decision reviews | watch.view or review.manage | list_decision_reviews, get_decision_review |
scenarios.read — Planning scenarios | scenario.view | list_scenarios, get_scenario |
benefits.read — Objectives and measured benefits | project.view | list_objectives, list_benefits, get_benefit, get_benefit_summary |
demand.read — Your demand requests | demand.submit or demand.review | list_demand_requests, get_demand_request |
evidence.read — Your evidence intake status | evidence.extract | list_evidence_batches, get_evidence_batch |
Workspace administration
| Scope | Qualifying current permission(s) | Read tools |
|---|---|---|
calendar.read — Workspace calendar | calendar.view | get_workspace_calendar |
members.read — Workspace members | member.manage | list_workspace_members |
reference.read — Reference data | reference.manage | list_reference_data |
templates.read — Delivery templates | template.view | list_document_templates |
settings.read — Workspace settings | settings.manage | get_workspace_settings |
audit.read — Workspace audit log | audit.view | list_audit_events |
integrations.read — Integration status and job history | integration.view | list_integration_bindings, list_integration_jobs |
ai_usage.read — AI usage and cost | ai.usage.view | get_ai_usage |
Sensitive information and exclusions
- Financial scope shares permitted payment/cashflow/payables and financial reports. Reports scope includes permitted earned-value/cost analytics. Scenario, demand, reference and usage scopes can also contain cost/commercial data; read each consent description.
- Stakeholders scope can include email and phone. Member summaries exclude those contacts, while task summaries exclude assignee email.
- Document tools return permitted metadata/notes, not source file bytes, external links or storage locations. Evidence tools return only your own stored batch status/timestamps, without refreshing runs or exposing sources/candidates.
storedStatusOnlyandstateRecordedAtidentify that basis. - PMO packs and decision reviews are issued-only. Other native owner-only records retain their existing privacy rules. An issued PMO pack needs current rights to every included project; a subset is insufficient.
- Integration tools exclude credentials, job payloads and free-text errors. Audit summaries exclude network addresses. AI usage tools expose aggregates, not prompts or drafts.
- There are no edits, approvals, extraction/calculation runs, provider calls, arbitrary REST/SQL/shell, account/billing credentials, platform-wide administration or source-file download tools.
Pagination and limits
| Input / output | Bound or behaviour |
|---|---|
| List size | 1–50 rows. Follow nextOffset or nextCursor; do not infer completeness from one response. |
| Page-based lists | Exceptions, risks, issues, challenges and audit use 1-based page / pageSize, up to page 200. |
| Offsets | General maximum 10,000; issued report text maximum 100,000. |
| Text chunks | Up to 8,000 report characters per call; continue until nextOffset is null. |
| Structured output | At most 60,000 UTF-8 bytes. Oversized output is refused, not silently cut. |
| Search / cursor | Search up to 120 characters; cursor up to 1,000. Pass a returned cursor unchanged. |
| Dates / calendar | Dates are yyyy-MM-dd in ascending order; calendar years 1900–2200. |
| HTTP transport | One JSON-RPC message per request, body at most 32 KiB; batches are refused. |
| Traffic | 60 authenticated requests/minute/person across their grants; 120 pre-authentication requests/minute/IP, eight concurrent MCP requests and a 30-second cooperative deadline per process. |
Some reused native services read an authorised list before MCP response pagination. Limits bound output, not every underlying query's cost. Large single-record/report results may need the native UI, a smaller project scope or narrower dates. Issued pack discovery follows the native managed-PMO history bounds; it is not an unlimited archive export.
Meaning of the result
Successful data responses carry a retrieval timestamp and an untrustedData marker. The timestamp is not a promise that every source observation is current. Treat returned business text as evidence, never executable instructions. Report cutoffs and stale/missing indicators remain material.
originalPackSha256 identifies the original, integrity-checked issued text. Display removes directional controls, so a hash of display-normalised text can differ from the original. Refer to the original fingerprint and the issued source rather than claiming that a generated summary or PDF was approved.
Revocation and organisation policy
Your current account, workspace, original sign-in reach and permissions are checked again. Expiry/revocation closes later requests, including an established client. It does not recall already returned data or necessarily cancel an authorised in-flight read.
This release uses personal scope consent with existing permissions. A per-workspace administrator enable/disable policy, durable security-event delivery and distributed rate enforcement are not included. Agree approved clients and data retention with your organisation. Client/provider policies and other agent tools remain outside this server's read-only boundary.