2,500+ MCP servers ready to use
Vinkius

Omie ERP MCP Server for VS Code Copilot 16 tools — connect in under 2 minutes

Built by Vinkius GDPR 16 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Omie ERP and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "omie-erp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
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.

GitHub Copilot Agent mode brings Omie ERP data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 16 tools — Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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 VS Code Copilot 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 VS Code Copilot via MCP

Follow these steps to integrate the Omie ERP MCP Server with VS Code Copilot.

01

Create MCP config

Create a .vscode/mcp.json file in your project root

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

04

Start using Omie ERP

Ask Copilot: "Using Omie ERP, help me..."16 tools available

Why Use VS Code Copilot with the Omie ERP MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Omie ERP through the Model Context Protocol.

01

VS Code is used by over 70% of developers — adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Omie ERP + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Omie ERP MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Omie ERP MCP Tools for VS Code Copilot (16)

These 16 tools become available when you connect Omie ERP to VS Code Copilot 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 VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot 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 VS Code Copilot

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

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Omie ERP + VS Code Copilot FAQ

Common questions about integrating Omie ERP MCP Server with VS Code Copilot.

01

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
02

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
03

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
04

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

Connect Omie ERP to VS Code Copilot

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