How do I get Omie API credentials (App Key and App Secret)?

Log in to your Omie ERP account, go to **Configurações > Aplicativos** (Settings > Applications), and create a new application. Omie will automatically generate an **App Key** and **App Secret** for you. Copy both values immediately — the App Secret is shown only once. Paste them into the respective fields below. These credentials are used to authenticate all API requests.

Can I create new clients and products through this integration?

Yes! Use the `create_client` tool to add new clients (customers/suppliers) and `create_product` to add new products to your Omie catalog. You'll need to provide the data as JSON objects matching Omie's schema. The AI agent can help you structure the data correctly. After creation, you'll receive the new client or product code for future reference.

How can I monitor overdue invoices and payments?

Use `list_accounts_receivable` to see all money owed to your company, and `list_accounts_payable` to see all money you owe. Each entry includes the due date, amount, and status. You can filter and identify overdue items by comparing the due date with today's date. The AI agent can help you analyze the results and highlight which invoices need immediate attention.

What ERP modules are accessible through this API?

This integration covers the core Omie modules: **Clients** (customers, suppliers, transporters), **Products & Services** (catalog management), **Sales Orders** (pedidos de venda), **Accounts Receivable** (contas a receber), **Accounts Payable** (contas a pagar), **Bank Accounts** (contas correntes), and **Inventory/Stock** (estoque). Additional modules like NF-e, NFS-e, CRM, and purchases are available through Omie's full API but may be added in future updates.

Omie ERP MCP Server for CrewAI 16 tools — connect in under 2 minutes

Name: Omie ERP
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 16 Tools Framework

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

Connect your Omie ERP account to any AI agent and take full control of your business management workflows through natural conversation.

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

What you can do

Client Management — List, create, update, and inspect clients (customers, suppliers) with full contact and tax information
Product Catalog — Browse products and services, check details, create new items, and monitor stock levels
Sales Orders — List, create, and inspect sales orders with line items, pricing, and payment terms
Financial Monitoring — Track accounts receivable and payable to monitor cash flow and identify overdue items
Bank Accounts — List configured bank accounts and check balances for financial reconciliations
Inventory Control — Monitor stock levels, check product availability, and identify items needing reorder
Services Catalog — List and manage non-physical services offered to clients

The Omie ERP MCP Server exposes 16 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 Omie ERP to CrewAI via MCP

Follow these steps to integrate the Omie ERP 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 16 tools from Omie ERP

Why Use CrewAI with the Omie ERP MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Omie ERP 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 the 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

Omie ERP + CrewAI Use Cases

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

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

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

Omie ERP MCP Tools for CrewAI (16)

These 16 tools become available when you connect Omie ERP to CrewAI via MCP:

create_client

You must provide at minimum the business name (razao_social) and CNPJ/CPF. Optional fields include trade name, address, contacts, email, phone, payment terms, and credit limits. The response includes the newly created client code which can be used for future references. Data must be provided as a JSON object matching Omie's client schema. Create a new client (customer/supplier) in Omie ERP

create_product

You must provide at minimum the product code (codigo_produto) and description. Optional fields include NCM, unit, cost price, sale price, stock quantity, and tax configuration. The response includes the newly created product details. Data must be provided as a JSON object matching Omie's product schema. Create a new product in Omie ERP

create_sales_order

You must provide the client code (codigo_cliente) and at least one line item with product code, quantity, and price. Optional fields include discounts, taxes, shipping info, and payment terms. The response includes the newly created order code. Data must be provided as JSON matching Omie's order schema. Create a new sales order (pedido de venda) in Omie ERP

get_client

Use the client_id (codigo_cliente) obtained from list_clients to inspect full client details. This is useful for verifying client data before creating orders or invoices. Get detailed information about a specific client

get_product

Use the product_code (codigo_produto) obtained from list_products to inspect full product details. This is useful for verifying product data before creating orders. Get detailed information about a specific product

get_sales_order

Use the order_id (codigo_pedido) obtained from list_sales_orders to inspect full order details. This is useful for verifying order data before invoicing. Get detailed information about a specific sales order

get_stock_summary

Use the product_code (codigo_produto) obtained from list_products to inspect stock details. This helps determine if a product is available for sale or needs reordering. Get stock summary for a specific product

list_accounts_payable

Each entry includes supplier, due date, amount, status (open, paid, overdue), and payment method. You can optionally specify page number and records per page. Use this to monitor outgoing payments and identify bills that are due or overdue. List all accounts payable (contas a pagar) in Omie ERP

list_accounts_receivable

Each entry includes client, due date, amount, status (open, paid, overdue), and payment method. You can optionally specify page number and records per page. Use this to monitor incoming payments and identify overdue invoices that need follow-up. List all accounts receivable (contas a receber) in Omie ERP

list_bank_accounts

Each account includes bank name, agency, account number, and current balance. Use this to verify which bank accounts are available for financial transactions and reconciliations. List all bank accounts (contas correntes) configured in Omie ERP

list_clients

Each client includes business name (razao_social), trade name (nome_fantasia), CNPJ/CPF, contact information, address, and client code. You can optionally specify page number and records per page (default: 50). Use this to browse your client database or find a specific client by name or document. List all clients (customers, suppliers) in Omie ERP

list_products

You can optionally specify page number and records per page (default: 50). Use this to browse your product catalog or find a specific product by code or description. List all products and services in Omie ERP

list_sales_orders

You can optionally specify page number and records per page. Use this to browse your sales pipeline or find a specific order by number or client. List all sales orders (pedidos de venda) in Omie ERP

list_services

Services are non-physical offerings sold to clients (consulting, maintenance, etc.). You can optionally specify page number and records per page. Use this to browse your service catalog. List all services (serviços) registered in Omie ERP

list_stock

Each entry includes product code, description, quantity in stock, minimum stock level, and warehouse location. You can optionally specify page number and records per page. Use this to monitor inventory levels and identify products that need reordering. List stock/inventory levels for all products in Omie ERP

update_client

You must provide the client_id (codigo_cliente) and the fields to update. Only the fields provided in client_data will be updated. This is useful for correcting client information, updating addresses, or changing payment terms. The client_id must exist in the system. Update an existing client in Omie ERP

Example Prompts for Omie ERP in CrewAI

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

"List all my clients and show me their total outstanding balances."

"Create a new sales order for client TechCorp with 5 units of product 'Consulting Hours' at R$ 150/hour."

"Show me all overdue accounts payable and the total amount owed."

Troubleshooting Omie ERP MCP Server with CrewAI

Common issues when connecting Omie ERP 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

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

Omie ERP + CrewAI FAQ

Common questions about integrating Omie ERP 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.