A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Nothing to run from here
AiDOOS Virtual Delivery Center is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
5
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Plan a Virtual Delivery Center for any initiative: pods, roles, AI agents, Delivery Units.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http aidoos-virtual-delivery-center-mcp https://aidoos.com/mcp
# 2 — ask your agent for something these tools do
# create_delivery_plan, refine_delivery_plan, estimate_delivery_cost and 2 more
AiDOOS Virtual Delivery Center costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
AIAll 1 server
aidoos1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http aidoos-virtual-delivery-center-mcp https://aidoos.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Create a structured delivery plan for an initiative the user describes. Given a plain-language description of something to build, implement, modernize, migrate, or scale, this returns a plan with teams (pods), roles, AI agents, work modules sized in Delivery Units, a phased timeline, and a recommended plan size. Use this tool when a user describes a project or initiative and wants to understand th
| Parameter | Type | Required | Notes |
|---|---|---|---|
| initiative | string | yes | A plain-language description of what the user wants to build, implement, modernize, migrate, or scale. Pass through the user's own words when possible. For example: 'Build a customer portal in 12 week |
| industry | string | no | Optional industry hint (for example FinTech, SaaS, Healthcare, Retail, Manufacturing, or Public Sector). Improves sizing accuracy. |
| company_size | string | no | Optional company size hint: 'startup', 'small' (<200), 'medium' (200-1000), 'enterprise' (1000+). |
Revise an existing delivery plan based on the user's requested changes. Given a plan_id and instructions such as adjusting the timeline, adding or removing scope, or changing the team composition, this returns the updated plan and replaces the stored plan with the revised version. Use this tool when the user wants to modify a plan created earlier in the conversation.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan_id | string | yes | The plan_id returned by a prior create_delivery_plan call. |
| feedback | string | yes | What the user wants changed in the plan. Examples: 'compress to 8 weeks', 'remove the QA pod and use AI test generation only', 'add data migration as a separate workstream'. |
Estimate the size and cost of a specific list of work items. Given short descriptions of deliverables, this returns each item sized in Delivery Units, a total, an indicative cost, and a recommended plan size. Use this tool when the user has already broken the work into specific items and wants sizing. When the user describes an overall goal without a breakdown, use create_delivery_plan instead.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| modules | array | yes | List of work modules to estimate. Each item is a 1-2 sentence description of a deliverable, e.g. 'Tenant onboarding flow with SSO integration' or 'Migrate 200 SAP custom reports to Power BI'. |
| industry | string | no | Optional industry hint for calibration. |
| company_size | string | no | Optional company-size hint: startup, small, medium, enterprise. |
Retrieve a previously created delivery plan by its plan_id. Returns the plan's current status and contents. Use this tool when the user wants to revisit or summarize a plan created earlier in the conversation.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan_id | string | yes | The plan_id from a prior create_delivery_plan or refine_delivery_plan call. |
Summarize how to proceed with a delivery plan. Given a plan_id, this returns the plan size, an indicative cost, the available plan tiers, and referral links to the AiDOOS website where the user can review options and get started. Use this tool when the user asks how to proceed or what the next step is for a plan created earlier in the conversation. This tool is advisory only: it does not take paym
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan_id | string | yes | The plan_id from a prior create_delivery_plan / refine_delivery_plan call. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install AiDOOS Virtual Delivery Center or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish AiDOOS Virtual Delivery Center can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.