How do I obtain my HCSS API credentials?

You must request API access through the **HCSS Developer Portal** (developer.hcssapps.com). Once approved, you will receive your Client ID, Client Secret, and Ocp-Apim-Subscription-Key.

Can I see the real-time location of my equipment?

Yes! Use the `get_equipment_location` tool with the unique equipment ID. It will return the latest GPS coordinates recorded by the Telematics system.

Does this integration cover both HeavyJob and HeavyBid?

Yes, this MCP server includes tools for both modules, allowing you to access timecard data from HeavyJob and estimate/bid data from HeavyBid in a single interface.

Is the integration secure for construction data?

Absolutely. The integration uses industry-standard OAuth 2.0 Client Credentials flow and HTTPS. Your credentials are encrypted and stored securely within the Vinkius Cloud infrastructure.

HCSS MCP Server for CrewAI 11 tools — connect in under 2 minutes

Name: HCSS
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 11 Tools Framework

Connect your CrewAI agents to HCSS through Vinkius, pass the Edge URL in the `mcps` parameter and every HCSS tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="HCSS Specialist",
    goal="Help users interact with HCSS effectively",
    backstory=(
        "You are an expert at leveraging HCSS tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in HCSS "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 11 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About HCSS MCP Server

Connect your HCSS platform to any AI agent and take full control of your heavy construction workflows, from estimating to field data and equipment tracking, through natural conversation.

When paired with CrewAI, HCSS becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call HCSS tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Field Data Management — List construction jobs and retrieve timecard data from HeavyJob to monitor site progress.
Estimating Insights — Access bidding estimates and bid items from HeavyBid to stay aligned with project budgets.
Equipment Telematics — Monitor your fleet with real-time GPS locations and latest meter readings (odometer/hours).
Resource Coordination — List employees and business units defined across the HCSS ecosystem.
Pre-Construction Tracking — Browse active pre-con projects and project lifecycles.
Operational Efficiency — Use AI to identify equipment utilization trends or job cost variances in seconds.

The HCSS MCP Server exposes 11 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect HCSS to CrewAI via MCP

Follow these steps to integrate the HCSS MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 11 tools from HCSS

Why Use CrewAI with the HCSS MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with HCSS through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

HCSS + CrewAI Use Cases

Practical scenarios where CrewAI combined with the HCSS MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries HCSS for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries HCSS, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain HCSS tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries HCSS against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

HCSS MCP Tools for CrewAI (11)

These 11 tools become available when you connect HCSS to CrewAI via MCP:

get_bid_items

List bid items for a specific estimate

get_equipment_location

Get current GPS coordinates for a specific piece of equipment

get_equipment_meters

Get latest meter readings (odometer/hours) for equipment

list_business_units

List all business units in HCSS

list_cost_codes

List cost codes defined in the system

list_employees

List all employees synced in HCSS

list_equipment

List all tracked equipment/fleet from Telematics

list_estimates

List bidding estimates from HeavyBid

list_jobs

List all construction jobs/projects

list_precon_projects

List active pre-construction projects

list_timecards

List timecards from HeavyJob

Example Prompts for HCSS in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with HCSS immediately.

"List all active construction jobs."

"Show the current location of Excavator ID EX-992."

"What are the bid items for estimate ID 2024-001?"

Troubleshooting HCSS MCP Server with CrewAI

Common issues when connecting HCSS to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

HCSS + CrewAI FAQ

Common questions about integrating HCSS MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.