Interfaces

Model Context Protocol

Preview

Bring DigitalStack into your AI client. The MCP server exposes your platform as governed tools — read-first by default, with write commands that require explicit scopes and confirmation, all grounded in your live workspace and bound by your own permissions.

Preview

MCP is available for Claude today with a focused set of working tools. More tools arrive as their underlying capabilities ship — each is labeled honestly in the tool catalog.

Why MCP

Ask in natural language

Your AI client can ask about projects and delivery health and get grounded answers — no glue code.

Your permissions, enforced

Tools run with your identity. The MCP server holds no privileged access — DigitalStack authorizes every call.

The same platform as tools

MCP exposes the same governed capabilities as the REST API — read tools plus confirmed, scope-gated commands your client can call.

MCP or REST?

Choose MCP

  • • An AI assistant should answer questions grounded in your workspace
  • • You want conversational access without building an integration
  • • Grounded insight — project health, status, risks, work items, and cross-workspace context
  • • Governed actions — draft-first writes that require your confirmation and explicit scopes

Choose REST

  • • You’re building an application or automation
  • • You need to create or update data, or export documents
  • • You want precise, typed control over each request
Explore the REST API

Supported clients

Claude is connectable today. Other MCP-compatible clients are on the way.

ClaudeAvailable

Claude Desktop, Claude Code, and the Claude web app.

ChatGPTPlanned

OpenAI ChatGPT connectors.

Cursor & IDE clientsPlanned

Cursor, VS Code, and other MCP-compatible editors.

GitHubPlanned

Repositories, issues, and pull requests.

Other MCP clientsPlanned

Any MCP-compatible application.

What you can ask today

These map to tools that work end-to-end right now. Richer natural-language questions (risk, full context) are coming to MCP.

List my active projects and their current status.
Give me the delivery health and current alerts for project {project_id}.
Acknowledge Project Health alert delivery_risk:blocked_items for project {project_id}.
Show my active projects from the public Projects API.
Get project {project_id}.
After I confirm, create a project named Acme replatform.
After I confirm, update project {project_id} client name to Acme Inc.
After I confirm, mark project {project_id} active.
After I confirm, archive project {project_id}.
List members for project {project_id}.
After I confirm, add user {user_id} to project {project_id} as viewer.
After I confirm, change project member {member_id} to editor.
After I confirm, remove project member {member_id}.
Show settings for project {project_id}.
After I confirm, set project {project_id} ticket prefix to ACME.
Which of my projects are currently at risk, and why?
Search this project’s context for “Shopify Tax”.
Show me the current Context Engine coverage and freshness posture.
List the newest ready context packages.
Explain context package {package_id} and its provenance.
Search governed context for rollout terminology.
Show the evidence references behind context package {package_id}.
Which providers contribute to Context Engine and what authority do they have?
Give me my morning briefing and the items that need attention today.
Review the current scope, effort, roles, risks, and baseline posture for estimate {estimate_id}.
Draft a reviewed proposal to adjust contingency and explain the evidence, but do not change the estimate.
After I confirm, submit proposal {proposal_id} for baseline review.
Mark this Today attention item resolved after I confirm.
Summarize the current sprint and explain the largest blockers.
Show me sprint planning readiness for project {project_id}.
Suggest sprint planning moves for project {project_id} after I confirm.
Show me the delivery timeline for project {project_id}.
List milestones for project {project_id}.
Get milestone {milestone_id}.
List workstreams for project {project_id}.
After I confirm, mark milestone {milestone_id} at risk.
After I confirm, move milestone {milestone_id} target date to 2026-08-07.
After I confirm, update milestone {milestone_id} to 70% complete.
Explain the major dependencies and risks affecting this project.
List the blocked work items for this sprint.
Show me the current work-item board for this team.
Tell me what EA-1650 is about, who owns it, what was discussed, and what it relates to.
Show me the recent transition history for this work item.
What can I safely do to this work item right now?
Add this note to the work item after I confirm it.
Move this work item into progress if that transition is allowed.
Assign this work item to Jordan after verifying Jordan is eligible.
Prepare a confirmed due-date command for this work item for next Friday.
Prepare a confirmed five-point estimate command for this work item.
Prepare a confirmed label command for api and triage on this work item.
Link this work item as depending on the API contract work item.
Raise a high-severity blocker on this work item for missing credentials.
Pin this work item to focus because it is a customer escalation.
What changed on this work item recently, and what is blocking it?
List enhancement runs for this work item.
Enhance this work item for engineering readiness, then show me the generated drafts before applying anything.
Show me this enhancement run and the drafts ready for review.
Show me the current operation status for this enhancement run.
Run the implementation-plan action for this enhancement run after I confirm.
Draft requirements for this enhancement run and call out unresolved assumptions.
Rewrite this work item description so an engineer can start without ambiguity.
Draft a lightweight design note for this work item.
Show me the likely files and tests for this enhancement run, plus anything still missing.
Show me the applyable drafts for this enhancement run.
Show me the review artifacts for this enhancement run.
Prepare the apply package for these selected drafts and show the field-level diff for confirmation.
Apply these selected drafts after I review the diff and explicitly confirm.
List my draft time entries for this week.
Show me this time entry.
Adjust this draft time entry after I confirm the fields.
Void this draft entry after I confirm.
Show me my current timer.
Show me my time day and any gaps that still need review.
Draft today's time from my DigitalStack work evidence and show me what remains unresolved.
After I review the proposal, apply this time draft with my explicit confirmation.
Log 90 minutes to the selected project after I confirm the fields.
Start my timer for the selected project after I confirm the attribution.
Pause my active timer after I confirm.
Resume my paused timer after I confirm.
Stop my active timer and record the result after I confirm.
Discard my current timer after I confirm.
Submit my reviewed time day after I explicitly confirm.
Recall this submitted time day after I confirm.
List my pending time approvals.
Approve this eligible time submission after I inspect it and confirm the decision.
List recent time import runs.
Import Timely time for this date range after I confirm.
List open time reconciliation findings.
Scan this date range for time reconciliation issues after I confirm.
Resolve this reconciliation finding after I confirm the action.

Next steps

Connect your MCP endpoint

https://mcp.digitalstack360.com/mcp
Sign in to connect