How to Use the BIM 360 Field MCP in Cursor

Q: How do I configure the BIM 360 Field server in Cursor?

Create a .cursor/mcp.json file in your project root. Add the BIM 360 Field MCP Server details under the mcpServers key, and Cursor will instantly make the tools available in agent mode.

Write custom site-reporting scripts in Cursor using live BIM 360 Field issue logs and project checklists.

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 Cursor

Create your Vinkius account to connect BIM 360 Field to Cursor 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 Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Generate code with live BIM 360 Field context in Cursor

This MCP Server uses `list_projects` to fetch your actual BIM 360 Field project list directly into Cursor. When building custom construction dashboards, the editor uses these records to let the AI generate precise data parsers. By calling `get_project` directly from Cursor's agent mode, the editor understands the exact structure of your active BIM 360 Field jobsite. You write working code faster in Cursor because the AI sees the real BIM 360 Field payload format instead of guessing.

Debug BIM 360 Field checklist sync scripts in Cursor

This MCP toolset uses `list_checklists` to pull actual BIM 360 Field QA/QC data straight into your Cursor editor's context window. If you are writing an integration in Cursor to sync BIM 360 Field inspections to an external database, you can test your logic live. You can ask the Cursor editor to write a migration script for a specific BIM 360 Field subcontractor using `list_companies` to fetch vendor profiles. The Cursor agent uses this data to map the correct BIM 360 Field vendor IDs directly into your active code file.

Auto-populate BIM 360 Field schemas in Cursor

This server uses `list_issue_types` to pull your configured BIM 360 Field categories directly into your Cursor workspace. Building custom BIM 360 Field notification webhooks in Cursor requires knowing your exact site setup, and this tool provides it instantly. The Cursor agent can map these BIM 360 Field types to your database schema by invoking `list_locations` to parse physical zones. Cursor uses this location nesting logic to ensure your code matches the physical areas defined in your Autodesk project.

Setup guide

Set up BIM 360 Field MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the BIM 360 Field MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent BIM 360 Field transactions." If the MCP tools are loaded correctly, Cursor will call the BIM 360 Field tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/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 Cursor

Create a `.cursor/mcp.json` file in your project root. Add the BIM 360 Field MCP Server details under the `mcpServers` key, and Cursor will instantly make the tools available in agent mode.

This specific server is read-only, letting you run tools like `list_issues` to pull data. Cursor does not support creating or editing issues, keeping your production BIM 360 Field data safe from accidental AI writes.

No, Vinkius hosts the MCP Server for you. You just add the endpoint to your Cursor configuration, and the AI agent handles the BIM 360 Field API calls in the background.

Ask the Cursor agent to list your project vendors. The agent will run `list_companies` behind the scenes and print the active BIM 360 Field subcontractor directory directly in your sidebar.

Your company directories, issue types, and task lists are queried through an encrypted sandbox. Cursor only accesses the specific API responses required to complete your active coding prompt.

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