"Handling Sketch File Context and SVG Processing Overview" matching MCP servers:

Reference MCP server for OCL, an open standard giving AI agents structured, scoped business meaning for Odoo data. Serves published example context packs via get_context, resolve_noun, and explain_field (stdio, Python, Apache-2.0).

Enables querying ERP data via an external API with adaptive caching, and accessing data from Google Sheets or local Excel/CSV files through dual MCP endpoints.

An MCP Odoo tools connector/plugin for Claude Cowork and Claude Code. It runs from 10 to 19 and helps make the connection smooth. You just need to downloaded from the marketplace and run: "/odoo-tools:odoo-setup-mcp".

Provides interactive tools to explore AFAS customer data and employee leave information, including bubble charts, leave balance reports, and detailed leave cards.

Provides MCP tools for searching, reading, and drafting Gmail emails, as well as querying SAP OData endpoints with safe read operations and mock mode.

MCP server that exposes SAVIA, a legacy travel-industry ERP with no public API, as tools an AI assistant can use. It uses Playwright to operate the browser, enabling read-only extraction of information like screenshots, text, and tables.

Read-only MCP connector for querying the Protheus (TOTVS) system, exposing 10 GET endpoints as MCP tools with OAuth2 authentication and friendly error handling.

Provides safe, structured access to a local QuickBooks Desktop company file for reading and writing transactions, with automatic undo logging.

Unifies Fiori elements, UI5, CAP, and SAP BTP development capabilities in a single MCP server, enabling app generation and modification, documentation search, OData metadata handling, and UI5 scaffolding without SAP runtime dependencies.

MCP server for managing store replenishment, including listing stores, raising orders, checking order status, and viewing SKU reports with observability and key rotation handling.

Enables AI agents to read and create customers, jobs, estimates, invoices, calendar tasks, equipment, technicians, and reference data through the documented Service Fusion REST API, handling OAuth 2.0 and pagination automatically.

Enables AI assistants to integrate with SAP systems via OData REST APIs for querying entity sets, performing CRUD operations, and executing function imports. It features automatic service discovery, CSRF token management, and smart connection handling without requiring the SAP RFC SDK.

Enables interaction with Xero accounting software to create and manage invoices, bills, expenses, and expense claims with file attachments through PKCE authentication.

Enables Claude Desktop to interact with freee accounting API for expense registration, transaction management, and receipt image processing.

Enables AI assistants to interact with the Tripletex accounting API to manage time tracking, projects, and timesheet approvals through natural language. It also supports searching and managing outgoing invoices and processing supplier invoice approvals.

A Model Context Protocol server that enables Claude Desktop integration with AARO ERP system, allowing users to perform stock management, customer management, order processing, and other core ERP operations through natural language commands.

Enables natural language management of BOQ/Tendix project data, including hierarchy, pricing, and contractor handling via the BOQ REST API.

Enables MCP-capable clients to sign in with OAuth and perform purchaser tasks such as browsing catalogues, checking inventory, managing stocktakes and recipes, drafting requisitions, updating buy lists, exporting reports, and processing invoices. It also supports supplier access for listing and inspecting connections, catalogues, products, purchase orders, invoices, and entitled reports.

Enables AI assistants to interact with ERPNext data and functionality through the Model Context Protocol, including document CRUD, report running, and API method calls.

Enables interacting with Fiken accounting data—companies, accounts, contacts, purchases, and attachments—through the Model Context Protocol, with write previews and confirmation requirements.