APS MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APS_SA_ID | Yes | Your service account ID | |
| APS_SA_EMAIL | Yes | Your service account email | |
| APS_CLIENT_ID | Yes | Your APS application client ID | |
| APS_SA_KEY_ID | Yes | Your service account key ID | |
| APS_CLIENT_SECRET | Yes | Your APS application client secret | |
| APS_SA_PRIVATE_KEY | Yes | Your service account private key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-accountsB | List all available Autodesk Construction Cloud accounts |
| get-folder-contentsC | List contents of a project or a specific subfolder in Autodesk Construction Cloud |
| get-issue-commentsC | Retrieves a list of comments associated with an issue in Autodesk Construction Cloud. |
| get-issue-root-causesB | Retrieves a list of supported root cause categories and root causes that you can allocate to an issue in Autodesk Construction Cloud. |
| get-issue-typesC | List all issue types in an Autodesk Construction Cloud project |
| get-issuesD | List all available projects in an Autodesk Construction Cloud account |
| get-item-versionsC | List all versions of a document in Autodesk Construction Cloud |
| get-projectsC | List all available projects in an Autodesk Construction Cloud account |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Multiple tools have unclear boundaries and overlapping purposes. 'get-issues' and 'get-projects' appear to have conflicting descriptions (both mention listing projects), and several tools like 'get-accounts', 'get-projects', and 'get-issues' seem to retrieve similar high-level resource lists. The descriptions don't clearly differentiate when to use each tool, leading to potential misselection.
All tools follow a consistent 'get-noun' pattern with hyphen-separated words, making them predictable and readable. The naming convention is uniform across all eight tools, with no deviations in style or structure.
Eight tools is a reasonable count for an Autodesk Construction Cloud server, slightly on the lower side but well-scoped for basic operations. It covers accounts, projects, issues, folders, and documents, though it might benefit from a few more tools for a more comprehensive surface.
The tool set is severely incomplete for the domain, focusing only on read operations ('get-') with no create, update, or delete capabilities. This creates significant gaps for managing resources like issues, projects, or documents, limiting agents to listing and retrieving without supporting full lifecycle workflows.