2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 16 Tools Framework

LlamaIndex specializes in data-aware AI agents that connect LLMs to structured and unstructured sources. Add Omie ERP as an MCP tool provider through the Vinkius and your agents can query, analyze, and act on live data alongside your existing indexes.

Vinkius supports streamable HTTP and SSE.

python
import asyncio
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

async def main():
    # Your Vinkius token — get it at cloud.vinkius.com
    mcp_client = BasicMCPClient("https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    agent = FunctionAgent(
        tools=tools,
        llm=OpenAI(model="gpt-4o"),
        system_prompt=(
            "You are an assistant with access to Omie ERP. "
            "You have 16 tools available."
        ),
    )

    response = await agent.run(
        "What tools are available in Omie ERP?"
    )
    print(response)

asyncio.run(main())
Omie ERP
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.

LlamaIndex agents combine Omie ERP tool responses with indexed documents for comprehensive, grounded answers. Connect 16 tools through the Vinkius and query live data alongside vector stores and SQL databases in a single turn — ideal for hybrid search, data enrichment, and analytical workflows.

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 LlamaIndex 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 LlamaIndex via MCP

Follow these steps to integrate the Omie ERP MCP Server with LlamaIndex.

01

Install dependencies

Run pip install llama-index-tools-mcp llama-index-llms-openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

Save to agent.py and run: python agent.py

04

Explore tools

The agent discovers 16 tools from Omie ERP

Why Use LlamaIndex with the Omie ERP MCP Server

LlamaIndex provides unique advantages when paired with Omie ERP through the Model Context Protocol.

01

Data-first architecture: LlamaIndex agents combine Omie ERP tool responses with indexed documents for comprehensive, grounded answers

02

Query pipeline framework lets you chain Omie ERP tool calls with transformations, filters, and re-rankers in a typed pipeline

03

Multi-source reasoning: agents can query Omie ERP, a vector store, and a SQL database in a single turn and synthesize results

04

Observability integrations show exactly what Omie ERP tools were called, what data was returned, and how it influenced the final answer

Omie ERP + LlamaIndex Use Cases

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

01

Hybrid search: combine Omie ERP real-time data with embedded document indexes for answers that are both current and comprehensive

02

Data enrichment: query Omie ERP to augment indexed data with live information before generating user-facing responses

03

Knowledge base agents: build agents that maintain and update knowledge bases by periodically querying Omie ERP for fresh data

04

Analytical workflows: chain Omie ERP queries with LlamaIndex's data connectors to build multi-source analytical reports

Omie ERP MCP Tools for LlamaIndex (16)

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

01

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

02

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

03

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

04

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

05

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

06

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

07

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

08

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

09

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

10

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

11

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

12

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

13

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

14

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

15

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

16

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 LlamaIndex

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

01

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

02

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

03

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

Troubleshooting Omie ERP MCP Server with LlamaIndex

Common issues when connecting Omie ERP to LlamaIndex through the Vinkius, and how to resolve them.

01

BasicMCPClient not found

Install: pip install llama-index-tools-mcp

Omie ERP + LlamaIndex FAQ

Common questions about integrating Omie ERP MCP Server with LlamaIndex.

01

How does LlamaIndex connect to MCP servers?

Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
02

Can I combine MCP tools with vector stores?

Yes. LlamaIndex agents can query Omie ERP tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
03

Does LlamaIndex support async MCP calls?

Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.

Connect Omie ERP to LlamaIndex

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