How do I find my BLS Registration Key?

Register for an account at the [**BLS developer portal**](https://data.bls.gov/registrationEngine/), and you will receive your Registration Key via email. Copy and paste it below.

A series ID is a unique code identifying a specific statistical dataset, such as 'CUUR0000SA0' for the Consumer Price Index.

Can I query multiple series at once?

Yes. The `get_bls_timeseries_data` tool accepts an array of series IDs to retrieve metadata for multiple datasets in a single request.

BLS Public Data API MCP Server for CrewAI 2 tools — connect in under 2 minutes

Name: BLS Public Data API
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 2 Tools Framework

Connect your CrewAI agents to BLS Public Data API through Vinkius, pass the Edge URL in the `mcps` parameter and every BLS Public Data API 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="BLS Public Data API Specialist",
    goal="Help users interact with BLS Public Data API effectively",
    backstory=(
        "You are an expert at leveraging BLS Public Data API 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 BLS Public Data API "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 2 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 BLS Public Data API MCP Server

Empower your AI agent to orchestrate your entire economic research and labor auditing workflow with the BLS Public Data API, the authoritative source for United States Bureau of Labor Statistics data. By connecting the BLS API to your agent, you transform complex macroeconomic searches into a natural conversation. Your agent can instantly retrieve historical time series data, audit employment trends, and query specific series IDs without you ever touching a government portal. Whether you are conducting market research or managing regional economic constraints, your agent acts as a real-time data analyst, ensuring your intelligence is always verified and precise.

When paired with CrewAI, BLS Public Data API becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call BLS Public Data API 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

Series Auditing — Retrieve high-resolution time series data for thousands of BLS identifiers and maintain a clear view of economic changes.
Trend Oversight — Audit historical labor statistics to understand the longitudinal distribution of economic scale instantly.
Economic Discovery — Query specific series IDs like the Consumer Price Index (CPI) to identify relevant fiscal markers for your research.
Metadata Intelligence — Retrieve unique series identifiers and year-based metadata to assist in deep-dive data classification.
Operational Monitoring — Check API status to ensure your economic research workflow is always operational.

The BLS Public Data API MCP Server exposes 2 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 BLS Public Data API to CrewAI via MCP

Follow these steps to integrate the BLS Public Data API 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 2 tools from BLS Public Data API

Why Use CrewAI with the BLS Public Data API MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with BLS Public Data API 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

BLS Public Data API + CrewAI Use Cases

Practical scenarios where CrewAI combined with the BLS Public Data API MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries BLS Public Data API 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 BLS Public Data API, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain BLS Public Data API 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 BLS Public Data API against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

BLS Public Data API MCP Tools for CrewAI (2)

These 2 tools become available when you connect BLS Public Data API to CrewAI via MCP:

check_api_status

Check if the BLS Public Data service is operational

get_bls_timeseries_data

Provide series IDs as a comma-separated string (e.g., "CUUR0000SA0,LNS14000000"). Get historical data for specific BLS series IDs

Example Prompts for BLS Public Data API in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with BLS Public Data API immediately.

"Get Consumer Price Index (CPI) data for the last 5 years using BLS."

"Show employment statistics for series 'LNS14000000' (Unemployment Rate)."

"Compare data for series 'WPUFD4' and 'WPUFD491' from 2020 to 2023."

Troubleshooting BLS Public Data API MCP Server with CrewAI

Common issues when connecting BLS Public Data API 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.

BLS Public Data API + CrewAI FAQ

Common questions about integrating BLS Public Data API 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.