_ registry / mcp streamable-http · checked 2h ago

acc-mcp

https://acc-mcp.itmartin24.workers.dev

Registry code: 45871758936352ff

api record

Autodesk Construction Cloud via APS — projects, issues, RFIs, documents, submittals.

from a public catalogue that lists it, not from the operator

endpoint
https://acc-mcp.itmartin24.workers.dev/mcp
protocol
streamable-http ·2024-11-05
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
237ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 9 tools
1 auth-required 8 never probed 1 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • acc_list_projects auth-required 2h ago

    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 not call this repeatedly in a loop — cache the result; if the user already supplied a project_id starting with 'b.', skip discovery. APS scopes: data:read account:read. No write scope needed. Rate limits: APS default ~50 req/min per app per endpoint; BIM 360 hubs endpoints are pageable (limit 200). This tool fans out 1 hubs call + N project calls (one per hub) so call it sparingly on tenants with many hubs. Errors: 401 (APS token expired — refresh and retry once); 403 (app not provisioned in the BIM 360/ACC account — ask user to have an account admin add the APS client_id); 404 (rare, indicates hub deleted mid-call); 429 (rate limit — back off 60s); 5xx (ACC upstream — retry with jitter). Side effects: None. Read-only and idempotent.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • acc_create_rfi unknown never probed

    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 clarifications; issues are for field observations. When NOT to use: Do not use for informal observations (use acc_create_issue) or to answer an existing RFI (not supported here). APS scopes: data:read data:write account:read. Rate limits: APS default ~50 req/min per endpoint per app. RFIs share the Construction API umbrella with issues (~100 req/min combined). Errors: 401 (APS token expired — refresh); 403 (user lacks RFI create permission on project); 404 (project_id not found — verify 'b.' prefix and hub membership); 422 (validation — subject/question missing or priority enum invalid); 429 (rate limit — back off 60s); 5xx (ACC upstream — retry with jitter, check for duplicate before retrying). Side effects: Creates a persistent RFI record. NOT idempotent — retry on 5xx risks duplicates; dedupe by subject before retrying.

    mcp-tool

    {
  "type": "object",
  "required": [
    "project_id",
    "subject",
    "question"
  ],
  "properties": {
    "subject": {
      "type": "string",
      "examples": [
        "Clarification on Level 2 beam schedule"
      ],
      "description": "Short RFI subject/title, 1–255 chars. Required."
    },
    "priority": {
      "enum": [
        "critical",
        "high",
        "medium",
        "low"
      ],
      "type": "string",
      "examples": [
        "high"
      ],
      "description": "RFI priority. Defaults to 'medium' if omitted."
    },
    "question": {
      "type": "string",
      "examples": [
        "Drawing S-201 shows W14x22 but schedule lists W14x26 for gridline C/4. Please confirm which is correct."
      ],
      "description": "Full RFI question body. Plain text, up to ~10,000 chars. Required."
    },
    "project_id": {
      "type": "string",
      "examples": [
        "b.a1b2c3d4-1234-5678-9abc-def012345678"
      ],
      "description": "ACC project ID. MUST use 'b.' prefix literal. Obtain via acc_list_projects."
    },
    "assigned_to": {
      "type": "string",
      "examples": [
        "ABC123XYZ456"
      ],
      "description": "Optional APS user ID of the person the RFI is directed to."
    }
  }
}
    arguments 51 lines
  • acc_search_documents unknown never probed

    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_file); do not use to fetch issues/RFIs. If you already have a document URN, fetch it directly with an agent that has Data Management folder/item access. APS scopes: data:read account:read. No write scope required. Rate limits: APS Data Management ~50 req/min per app per endpoint; pageable (limit 200 upstream). Avoid tight query loops. Errors: 401 (APS token expired — refresh); 403 (user lacks Docs view permission on the project); 404 (project_id not found — verify 'b.' prefix and hub membership); 422 (invalid filter syntax — simplify query text); 429 (rate limit — back off 60s); 5xx (ACC upstream — retry with jitter). Side effects: None. Read-only and idempotent.

    mcp-tool

    {
  "type": "object",
  "required": [
    "project_id",
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "examples": [
        "A-201 floor plan"
      ],
      "description": "Free-text search string matched against filenames, titles, and indexed metadata. 1–500 chars."
    },
    "project_id": {
      "type": "string",
      "examples": [
        "b.a1b2c3d4-1234-5678-9abc-def012345678"
      ],
      "description": "ACC project ID. MUST use 'b.' prefix literal. The worker re-adds the prefix for Data Management URL formatting. Obtain via acc_list_projects."
    },
    "document_type": {
      "type": "string",
      "examples": [
        "items:autodesk.bim360:Document"
      ],
      "description": "Optional APS document type filter (e.g. 'items:autodesk.bim360:File', 'items:autodesk.bim360:Document')."
    }
  }
}
    arguments 30 lines
  • acc_project_summary unknown never probed

    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 downstream tool to call. When NOT to use: Do not use as a cheap existence check — prefer acc_list_projects which returns hub_id with every project and is one call regardless of tenant size. APS scopes: data:read account:read. Forma / BIM 360 hubs endpoints only require data:read. Rate limits: APS default ~50 req/min per endpoint; BIM 360 hubs endpoints pageable (limit 200). Cache results for the session. Errors: 401 (APS token expired — refresh); 403 (user lacks project view or app not in account); 404 (project not in the chosen hub — supply the correct hub_id, or call acc_list_projects first); 422 (malformed project_id — confirm 'b.' prefix); 429 (rate limit — back off 60s); 5xx (ACC upstream — retry). Side effects: None. Read-only and idempotent.

    mcp-tool

    {
  "type": "object",
  "required": [
    "project_id"
  ],
  "properties": {
    "hub_id": {
      "type": "string",
      "examples": [
        "b.abcdef01-2345-6789-abcd-ef0123456789"
      ],
      "description": "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."
    },
    "project_id": {
      "type": "string",
      "examples": [
        "b.a1b2c3d4-1234-5678-9abc-def012345678"
      ],
      "description": "ACC project ID. MUST use 'b.' prefix literal (this endpoint — unlike Issues/RFIs — wants the prefixed form). Obtain via acc_list_projects."
    }
  }
}
    arguments 22 lines
  • acc_upload_file unknown never probed

    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 report into Project Files. When NOT to use: Do not use for files already in ACC; do not use for files behind auth-gated URLs (fetch step is an unauthenticated GET). For very large files (>100MB), prefer the chunked/signed-S3 upload flow, not this single-PUT implementation. APS scopes: data:read data:write data:create account:read. Rate limits: APS Data Management ~50 req/min per endpoint; OSS upload bandwidth typically 100 MB/min per app. This tool issues 3–5 APS calls per upload, so budget accordingly. Errors: 401 (APS token expired — refresh); 403 (user lacks folder write permission — ask account admin to grant 'Edit' on folder); 404 (project_id not found or folder_path does not match any top folder — verify 'b.' prefix, hub membership, and folder name); 422 (invalid file_name or conflicting version); 429 (rate limit — back off 60s); 5xx (ACC/OSS upstream — retry with jitter BUT be cautious: storage object may already be created so reuse, do not re-create). Also: if source file_url returns non-2xx, the tool throws before touching ACC. Side effects: Creates a storage object, uploads bytes, and creates a versioned item in the target folder. NOT idempotent — a retry may create a duplicate item with a new version. Surface the returned item_id to the user to avoid re-uploads.

    mcp-tool

    {
  "type": "object",
  "required": [
    "project_id",
    "file_url",
    "file_name"
  ],
  "properties": {
    "file_url": {
      "type": "string",
      "examples": [
        "https://cdn.example.com/photos/site-2026-04-18.jpg"
      ],
      "description": "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": {
      "type": "string",
      "examples": [
        "site-2026-04-18.jpg"
      ],
      "description": "Destination filename in ACC, including extension. 1–255 chars. Avoid path separators."
    },
    "project_id": {
      "type": "string",
      "examples": [
        "b.a1b2c3d4-1234-5678-9abc-def012345678"
      ],
      "description": "ACC project ID. MUST use 'b.' prefix literal. Obtain via acc_list_projects."
    },
    "folder_path": {
      "type": "string",
      "examples": [
        "Photos"
      ],
      "description": "Case-insensitive substring of the target top-level folder's display name. Defaults to 'Project Files'. Common values: 'Project Files', 'Plans', 'Photos', 'Submittals'."
    }
  }
}
    arguments 38 lines
  • acc_create_issue unknown never probed

    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 to modify an existing issue (use acc_update_issue) and do not use for RFIs (use acc_create_rfi). APS scopes: data:read data:write account:read. Rate limits: ACC Issues API limited to ~100 req/min per app; APS default ~50 req/min per endpoint — batch creations with backoff. Errors: 401 (APS token expired — refresh); 403 (user lacks 'Create Issues' permission on the project or scope insufficient — surface to user); 404 (project_id not found — verify the 'b.' prefix and that the project belongs to a hub the app can see via acc_list_projects); 422 (validation — required field like title/description missing or priority enum invalid); 429 (rate limit — retry after 60s); 5xx (ACC upstream — retry with jitter, do not double-create). Side effects: Creates a persistent issue record visible to all project members. NOT idempotent — a retry on a 5xx may create duplicates; dedupe by title before retrying.

    mcp-tool

    {
  "type": "object",
  "required": [
    "project_id",
    "title",
    "description"
  ],
  "properties": {
    "title": {
      "type": "string",
      "examples": [
        "Leaking valve on Level 3 mech room"
      ],
      "description": "Short issue title, 1–255 chars. Required."
    },
    "due_date": {
      "type": "string",
      "examples": [
        "2026-05-01"
      ],
      "description": "Optional due date in ISO 8601 date format (YYYY-MM-DD)."
    },
    "priority": {
      "enum": [
        "critical",
        "high",
        "medium",
        "low"
      ],
      "type": "string",
      "examples": [
        "high"
      ],
      "description": "Issue priority. Defaults to 'medium' if omitted."
    },
    "project_id": {
      "type": "string",
      "examples": [
        "b.a1b2c3d4-1234-5678-9abc-def012345678"
      ],
      "description": "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."
    },
    "assigned_to": {
      "type": "string",
      "examples": [
        "ABC123XYZ456"
      ],
      "description": "Optional APS user ID (oxygen ID / ACC user UUID) of the assignee. Leave null for unassigned."
    },
    "description": {
      "type": "string",
      "examples": [
        "Observed active drip at VAV-312 supply connection during 2026-04-18 walkthrough. Photos attached in linked RFI."
      ],
      "description": "Detailed issue description / body. Plain text, up to ~10,000 chars. Required."
    }
  }
}
    arguments 58 lines
  • acc_update_issue unknown never probed

    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 scopes: data:read data:write account:read. Rate limits: ACC Issues API ~100 req/min per app; APS default ~50 req/min per endpoint. Errors: 401 (APS token expired — refresh); 403 (user lacks edit permission or status transition not allowed by project workflow); 404 (project_id or issue_id not found — verify 'b.' prefix on project_id and that issue_id belongs to that project); 422 (validation — invalid status/priority enum or illegal state transition); 429 (rate limit — back off 60s); 5xx (ACC upstream — retry with jitter). Side effects: Mutates the issue record. Idempotent when the same body is resent (PATCH semantics) — safe to retry.

    mcp-tool

    {
  "type": "object",
  "required": [
    "project_id",
    "issue_id"
  ],
  "properties": {
    "status": {
      "enum": [
        "open",
        "in_review",
        "closed",
        "draft"
      ],
      "type": "string",
      "examples": [
        "closed"
      ],
      "description": "New status. Project workflow may forbid certain transitions (e.g. draft → closed)."
    },
    "issue_id": {
      "type": "string",
      "examples": [
        "7f3e2a1b-4c5d-6e7f-8a9b-0c1d2e3f4a5b"
      ],
      "description": "UUID of the issue to update, as returned by acc_list_issues or acc_create_issue."
    },
    "priority": {
      "enum": [
        "critical",
        "high",
        "medium",
        "low"
      ],
      "type": "string",
      "examples": [
        "critical"
      ],
      "description": "New priority."
    },
    "project_id": {
      "type": "string",
      "examples": [
        "b.a1b2c3d4-1234-5678-9abc-def012345678"
      ],
      "description": "ACC project ID. MUST use the 'b.' prefix literal. Obtain via acc_list_projects."
    },
    "assigned_to": {
      "type": "string",
      "examples": [
        "ABC123XYZ456"
      ],
      "description": "APS user ID of the new assignee. Omit to leave unchanged."
    },
    "description": {
      "type": "string",
      "examples": [
        "Root cause confirmed as cracked fitting; scheduling replacement."
      ],
      "description": "Replacement description body. Plain text."
    }
  }
}
    arguments 63 lines
  • acc_list_issues unknown never probed

    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 search documents. APS scopes: data:read account:read. No write scope required. Rate limits: ACC Issues API ~100 req/min per app; results pageable (limit 50 here, max 200 upstream). For large projects, call once and filter client-side instead of looping. Errors: 401 (APS token expired — refresh); 403 (user lacks 'View Issues' permission on project or scope insufficient); 404 (project_id not found — verify 'b.' prefix and hub membership via acc_list_projects); 422 (invalid filter value — check status/priority spelling); 429 (rate limit — back off 60s); 5xx (ACC upstream — retry with jitter). Side effects: None. Read-only and idempotent.

    mcp-tool

    {
  "type": "object",
  "required": [
    "project_id"
  ],
  "properties": {
    "status": {
      "type": "string",
      "examples": [
        "open"
      ],
      "description": "Optional status filter. Typical values: open, in_review, closed, draft."
    },
    "priority": {
      "type": "string",
      "examples": [
        "critical"
      ],
      "description": "Optional priority filter. Typical values: critical, high, medium, low."
    },
    "project_id": {
      "type": "string",
      "examples": [
        "b.a1b2c3d4-1234-5678-9abc-def012345678"
      ],
      "description": "ACC project ID. MUST use 'b.' prefix literal. Obtain via acc_list_projects."
    },
    "assigned_to": {
      "type": "string",
      "examples": [
        "ABC123XYZ456"
      ],
      "description": "Optional assignee APS user ID filter. Accepted but not currently forwarded as a URL filter by this server — filter client-side if needed."
    }
  }
}
    arguments 36 lines
  • acc_list_rfis unknown never probed

    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. No write scope required. Rate limits: APS default ~50 req/min per endpoint; ACC Construction API shared ~100 req/min cap. Pageable (limit 50 here; upstream max 200). Errors: 401 (APS token expired — refresh); 403 (user lacks RFI view permission); 404 (project_id not found — verify 'b.' prefix and hub membership); 422 (invalid filter value); 429 (rate limit — back off 60s); 5xx (ACC upstream — retry). Side effects: None. Read-only and idempotent.

    mcp-tool

    {
  "type": "object",
  "required": [
    "project_id"
  ],
  "properties": {
    "status": {
      "type": "string",
      "examples": [
        "open"
      ],
      "description": "Optional RFI status filter. Typical values: draft, submitted, open, answered, closed, void."
    },
    "project_id": {
      "type": "string",
      "examples": [
        "b.a1b2c3d4-1234-5678-9abc-def012345678"
      ],
      "description": "ACC project ID. MUST use 'b.' prefix literal. Obtain via acc_list_projects."
    }
  }
}
    arguments 22 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/45871758936352ff/badge.svg)](https://brick.blue/agent/45871758936352ff)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.