2,500+ MCP servers ready to use
Vinkius

Bsale MCP Server for CrewAI 15 tools — connect in under 2 minutes

Built by Vinkius GDPR 15 Tools Framework

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

Vinkius supports streamable HTTP and SSE.

python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Bsale Specialist",
    goal="Help users interact with Bsale effectively",
    backstory=(
        "You are an expert at leveraging Bsale 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 Bsale "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 15 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
Bsale
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 Bsale MCP Server

Connect your Bsale cloud POS account to any AI agent and take full control of your Chilean retail and invoicing operations through natural conversation.

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

  • Electronic Document Emission — Issue SII-compliant boletas, facturas electrónicas, credit notes, and dispatch guides directly through your AI agent
  • Product Catalog Management — Browse, search, and create products with full variant (SKU) support, pricing tiers, and web descriptions
  • Inventory & Stock Control — Check real-time stock levels across all office branches and track variant-level availability
  • Client Registry — Search, inspect, and register customers with RUT, business activity (giro), and contact details for tax compliance
  • Configuration Intelligence — Query your document types, payment methods, price lists, and office configurations instantly

The Bsale MCP Server exposes 15 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 Bsale to CrewAI via MCP

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

01

Install CrewAI

Run pip install crewai

02

Replace the token

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

03

Customize the agent

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

04

Run the crew

Run python crew.py. CrewAI auto-discovers 15 tools from Bsale

Why Use CrewAI with the Bsale MCP Server

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

01

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

02

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

03

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

04

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

Bsale + CrewAI Use Cases

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

01

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

02

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

03

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

04

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

Bsale MCP Tools for CrewAI (15)

These 15 tools become available when you connect Bsale to CrewAI via MCP:

01

create_client

The client can then be associated with future invoices and sales documents. For Chilean tax compliance, include the RUT and business activity (giro) when available. Register a new client in the system

02

create_document

Requires the document type ID and at minimum one line item with product details. The document is automatically sent to the Chilean SII (Servicio de Impuestos Internos) for validation. Issue a new electronic tax document

03

create_product

The product will be available for inclusion in future documents and can be associated with variants (SKUs), price lists, and stock management across multiple offices. Create a new product in the catalog

04

get_client

Get full details of a specific client

05

get_document

Get full details of a specific tax document

06

get_product

Get full details of a specific product

07

list_clients

Use limit and offset for pagination. List all registered clients

08

list_document_types

List available SII document types

09

list_documents

Documents are returned with their SII-compliant folio numbers, emission dates, and net/tax/total breakdowns. Use optional limit and offset parameters for pagination. List tax documents (invoices, boletas, credit notes)

10

list_offices

List all office branches and locations

11

list_payment_types

List accepted payment methods

12

list_price_lists

g., retail, wholesale, distributor). Each price list can have different pricing for the same product variants. List all configured price lists

13

list_products

Use limit and offset for paginated browsing of large catalogs. List all products and services in your catalog

14

list_stocks

Returns available quantities per location. Check stock levels across offices

15

list_variants

Each variant has its own barcode, cost, and pricing configuration across different price lists. List all SKU variants for a product

Example Prompts for Bsale in CrewAI

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

01

"Show me the last 10 invoices issued in my Bsale account."

02

"Check stock levels for all variants of product ID 1542."

03

"Register a new client 'Distribuidora Los Andes Ltda' with RUT 76.543.210-K."

Troubleshooting Bsale MCP Server with CrewAI

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

01

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

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.

Bsale + CrewAI FAQ

Common questions about integrating Bsale MCP Server with CrewAI.

01

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.
02

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.
03

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.
04

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.
05

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.

Connect Bsale to CrewAI

Get your token, paste the configuration, and start using 15 tools in under 2 minutes. No API key management needed.