Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
ACC (acc-mcp) 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.
93/100
tool-list score
9
tools declared
remote
at its publisher
—
calls last 7d
What it does
Autodesk Construction Cloud via APS — projects, issues, RFIs, documents, submittals.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http acc-acc-mcp https://acc-mcp.itmartin24.workers.dev/mcp
# 2 — ask your agent for something these tools do
# acc_list_projects, acc_create_issue, acc_update_issue and 6 more
ACC (acc-mcp) costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SCAll 10 servers
scanbimlabs10 servers
2 categories
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 acc-acc-mcp https://acc-mcp.itmartin24.workers.dev/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
9 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.
Enumerate every ACC and BIM 360 project the authenticated APS app can see by walking all accessible hubs and their project lists. When to use: The agent needs to discover project IDs before calling any other tool (e.g. the user says 'show me my projects' or 'find issues in the Tower project' and no project_id is known yet). Also useful to confirm hub membership for a project. When NOT to use: Do
No parameter schema on file.
Create a new ACC issue (field observation, coordination clash, safety, quality, etc.) in the target project via the APS Construction Issues API. When to use: The user wants to log a new issue — e.g. 'open a high-priority issue about the leaking valve on level 3' or a downstream agent detected a defect during a model review and needs to record it for the project team. When NOT to use: Do not use
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | ACC project ID. MUST use the 'b.' prefix literal (e.g. 'b.a1b2c3d4-...'). The worker strips the prefix internally for the Issues endpoint. Obtain via acc_list_projects. |
| title | string | yes | Short issue title, 1–255 chars. Required. |
| description | string | yes | Detailed issue description / body. Plain text, up to ~10,000 chars. Required. |
| priority | string | no | Issue priority. Defaults to 'medium' if omitted. |
| assigned_to | string | no | Optional APS user ID (oxygen ID / ACC user UUID) of the assignee. Leave null for unassigned. |
| due_date | string | no | Optional due date in ISO 8601 date format (YYYY-MM-DD). |
Patch an existing ACC issue — change status, priority, assignee, or description via the APS Construction Issues API. When to use: The user asks to close/reopen/escalate an issue, reassign it, or edit its body. Typical agent flow: acc_list_issues → pick an id → acc_update_issue. When NOT to use: Do not use to create issues (acc_create_issue) or to add comments (not supported by this server). APS
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | ACC project ID. MUST use the 'b.' prefix literal. Obtain via acc_list_projects. |
| issue_id | string | yes | UUID of the issue to update, as returned by acc_list_issues or acc_create_issue. |
| status | string | no | New status. Project workflow may forbid certain transitions (e.g. draft → closed). |
| priority | string | no | New priority. |
| assigned_to | string | no | APS user ID of the new assignee. Omit to leave unchanged. |
| description | string | no | Replacement description body. Plain text. |
List and filter issues from a single ACC project (limit 50 per call) via the APS Construction Issues API. When to use: The user or upstream agent needs to review open issues, count issues by status/priority, or look up an issue_id before calling acc_update_issue. E.g. 'show me all critical open issues on the Tower project'. When NOT to use: Do not use to fetch RFIs (use acc_list_rfis) or to sear
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | ACC project ID. MUST use 'b.' prefix literal. Obtain via acc_list_projects. |
| status | string | no | Optional status filter. Typical values: open, in_review, closed, draft. |
| priority | string | no | Optional priority filter. Typical values: critical, high, medium, low. |
| assigned_to | string | no | Optional assignee APS user ID filter. Accepted but not currently forwarded as a URL filter by this server — filter client-side if needed. |
Create a new Request For Information (RFI) in an ACC project via the APS Construction RFIs API. RFI is created in 'draft' status — the project workflow owner typically transitions it to 'submitted'. When to use: The user needs a formal question-of-record to the design or GC team — e.g. 'raise an RFI asking for clarification on the Level 2 beam schedule'. RFIs are the auditable channel for clarifi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | ACC project ID. MUST use 'b.' prefix literal. Obtain via acc_list_projects. |
| subject | string | yes | Short RFI subject/title, 1–255 chars. Required. |
| question | string | yes | Full RFI question body. Plain text, up to ~10,000 chars. Required. |
| assigned_to | string | no | Optional APS user ID of the person the RFI is directed to. |
| priority | string | no | RFI priority. Defaults to 'medium' if omitted. |
List and filter RFIs from a single ACC project (limit 50 per call) via the APS Construction RFIs API. When to use: The user wants to review open RFIs, count outstanding ones, or look up an RFI ID. E.g. 'how many RFIs are still open on the Tower project?' When NOT to use: Do not use for issues (use acc_list_issues) or document search (use acc_search_documents). APS scopes: data:read account:read
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | ACC project ID. MUST use 'b.' prefix literal. Obtain via acc_list_projects. |
| status | string | no | Optional RFI status filter. Typical values: draft, submitted, open, answered, closed, void. |
Full-text search the ACC Docs repository of a project for drawings, specs, submittals, and other files via the APS Data Management search endpoint. When to use: The user wants to find a document by keyword (filename, sheet number, or metadata match). E.g. 'find the latest A-201 sheet' or 'search for mechanical specs on Tower project'. When NOT to use: Do not use to upload a file (use acc_upload_
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | ACC project ID. MUST use 'b.' prefix literal. The worker re-adds the prefix for Data Management URL formatting. Obtain via acc_list_projects. |
| query | string | yes | Free-text search string matched against filenames, titles, and indexed metadata. 1–500 chars. |
| document_type | string | no | Optional APS document type filter (e.g. 'items:autodesk.bim360:File', 'items:autodesk.bim360:Document'). |
Upload a file from a public source URL into an ACC project folder. Runs the full four-step APS Data Management flow: top-folder discovery → storage object creation → OSS PUT of bytes → first-version item creation. When to use: The user wants to push a document/photo/model into ACC Docs — e.g. 'upload this site photo to the Tower project Photos folder' or an automation needs to archive an exported
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | ACC project ID. MUST use 'b.' prefix literal. Obtain via acc_list_projects. |
| file_url | string | yes | Publicly fetchable HTTPS URL of the source file. Must return 2xx to an unauthenticated GET. Max practical size ~100MB for this single-PUT implementation. |
| file_name | string | yes | Destination filename in ACC, including extension. 1–255 chars. Avoid path separators. |
| folder_path | string | no | Case-insensitive substring of the target top-level folder's display name. Defaults to 'Project Files'. Common values: 'Project Files', 'Plans', 'Photos', 'Submittals'. |
Fetch the full ACC project metadata record (name, type, status, dates, extension attributes) for a single project via APS Data Management. If hub_id is omitted the tool picks the first accessible hub, which may be wrong on multi-hub tenants. When to use: The user asks 'tell me about project X' or an agent needs project metadata (start/end dates, type, Forma/BIM 360 flavor) before deciding which d
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | ACC project ID. MUST use 'b.' prefix literal (this endpoint — unlike Issues/RFIs — wants the prefixed form). Obtain via acc_list_projects. |
| hub_id | string | no | Optional ACC/BIM 360 hub ID. Also uses the 'b.' prefix literal. If omitted, the first hub returned by APS is used — prefer supplying this explicitly on multi-hub tenants to avoid 404s. |
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 ACC (acc-mcp) 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: —
ATool-list grade · score 93 / 100
Release 1.0.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
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.
Threat score100
Client score93
Findings0 threat · 2 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestc2b506df951970cb3346e45825c1c48230f40091c8a7eb28a140a3e02f038246
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| acc_list_projects | no tags | |
| acc_create_issue | external-sink | external-sink: keyword "create_issue" |
| acc_update_issue | no tags | |
| acc_list_issues | no tags | |
| acc_create_rfi | no tags | |
| acc_list_rfis | no tags | |
| acc_search_documents | untrusted-input | untrusted-input: keyword "fetch" |
| acc_upload_file | external-sink | external-sink: keyword "upload_file" |
| acc_project_summary | untrusted-input | untrusted-input: keyword "fetch" |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digestc2b506df951970cb
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
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 ACC (acc-mcp) 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.