How to Use the BIM 360 Field MCP in VS Code Copilot

Q: Can I share my BIM 360 Field configuration with my team in VS Code Copilot?

Yes, you can commit a .vscode/mcp.json file to your shared Git repository. This lets every developer on your team access the BIM 360 Field MCP tools automatically inside VS Code Copilot.

Share BIM 360 Field project tools across your entire engineering team directly inside VS Code Copilot.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect BIM 360 Field MCP to VS Code Copilot

Create your Vinkius account to connect BIM 360 Field to VS Code Copilot and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup BIM 360 Field with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Manage BIM 360 Field schemas with this MCP Server

This MCP Server configures `list_issue_types` so every developer using VS Code Copilot can see how issues are categorized. Keep your entire engineering team aligned on BIM 360 Field data structures inside VS Code Copilot. VS Code Copilot uses this shared context to write accurate BIM 360 Field integration code. Developers don't have to look up field definitions because VS Code Copilot runs `list_issues` to see live examples of active BIM 360 Field tickets.

Validate BIM 360 Field hierarchies in VS Code Copilot

This integration runs `list_locations` to pull the exact BIM 360 Field hierarchy configured in Autodesk directly into VS Code Copilot. Writing code for multi-floor BIM 360 Field construction projects is tricky in VS Code Copilot when location paths are nested. You can ask VS Code Copilot to write a parser for these BIM 360 Field locations using `list_tasks` to map equipment. VS Code Copilot cross-references the output with these tasks to ensure your code correctly assigns equipment to physical rooms on the jobsite.

Audit BIM 360 Field users in VS Code Copilot

This server uses `list_users` to pull the directory of active personnel straight into VS Code Copilot. When building custom access control lists for your BIM 360 Field apps, you need to know who is who inside VS Code Copilot. The VS Code Copilot agent can match these users against the BIM 360 Field details returned by `get_project`. This makes it easy to write unit tests in VS Code Copilot that simulate real BIM 360 Field permissions without hardcoding dummy names.

Setup guide

Set up BIM 360 Field MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the BIM 360 Field MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the BIM 360 Field tools listed. Try asking: "List my recent BIM 360 Field transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "bim-360-field-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by BIM 360 Field. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect BIM 360 Field now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about BIM 360 Field MCP in VS Code Copilot

Yes, you can commit a `.vscode/mcp.json` file to your shared Git repository. This lets every developer on your team access the BIM 360 Field MCP tools automatically inside VS Code Copilot.

Just ask VS Code Copilot to show the active checklists for your project ID. The agent will execute `list_checklists` and format the BIM 360 Field inspection names right in your chat panel.

No, Vinkius manages the authentication on its secure environment. You only need to add your Vinkius token to your VS Code Copilot configuration to authorize the BIM 360 Field tools.

You need VS Code version 1.96 or higher with the GitHub Copilot extension active. This setup supports the external MCP Server protocol required to run the BIM 360 Field tools.

Your BIM 360 Field project lists, user directories, and safety checklists are transmitted through a SOC 2 compliant tunnel. VS Code Copilot only fetches the specific records requested by your editor and never stores your construction logs.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript