"Spec-WorkFlow documentation or implementation" matching MCP servers:

Enables interaction with IntelliMatch recruiting and iSuite insurance systems through spec-driven MCP tools, allowing natural language queries for candidate search, policy management, claims, and workflows.

Provides offline access to SAP documentation and real-time SAP Community content, integrating official documentation with community-driven solutions for comprehensive developer support.

This MCP server provides tools to interact with the AgileWorks business process platform via its Web API, enabling document management, workflow operations, user administration, and more.

MCP server for HERO handyman software, providing 34 OAuth-secured read/write tools with multi-tenant support and built-in API correctness checks.

Enables AI agents to bridge Shopify, Odoo, and Asana for e-commerce operations, turning a Shopify order into an Odoo sale order and Asana fulfillment task in a single call, with Excel export support.

An MCP server for searching SAP Help Portal documentation, enabling AI assistants to search, browse, and retrieve SAP documentation programmatically.

SBIS (Saby) API for AI assistants: documents and their workflow stages, electronic signature, certificates, employees and organizations. 45 methods, each with a read/write/destructive safety class.

MCP server for synthetic vendor-management workflow, providing structured access to vendor records, contracts, spending, renewals, and security reviews. Currently exposes read-only vendor data over local stdio.

Enables an AI assistant to interact with a Notory inventory instance through its REST API, allowing lookups and modifications based on token scope. It automatically discovers available endpoints from the live OpenAPI spec, covering over 200 endpoints beyond just assets.

Enables AI assistants to search, browse, and generate example payloads from Sage Intacct REST API documentation using OpenAPI specs.

A version-agnostic MCP server for Odoo that enables AI agents to interact with any Odoo app's data, schema, and source code, supporting tasks like data CRUD, schema mapping, code analysis, and feature implementation.

A Model Context Protocol server implementation providing standardized access to Xero's accounting and business features, enabling operations like contact management, invoice creation, and chart of accounts management through MCP.

MCP server for 1C:Enterprise ERP with 35 tools: metadata inspection, document CRUD, register queries, and BSP integration. First MCP server for Russian ERP systems (300,000+ organizations). JSON-RPC 2.0 compliant BSL implementation.

MCP server for ERPNext that provides full CRUD operations, workflow management, custom fields, and DocType management.

ABAP Development Tools MCP server with comprehensive tooling and documentation for SAP systems

This Model Context Protocol server exposes the Wafeq Public API — all 251 endpoints, generated straight from the OpenAPI spec into MCP tools, plus two hand-written ones. Every tool carries a safety category (🟢 read-only / 🟡 write / 🟠 state change / 🔴 irreversible or destructive) so your assistant knows what an action does before it calls it — including the difference between saving an invoice

Enables AI agents to connect to Odoo 16+ databases via MCP, providing read tools, diagnostics, schema discovery, and gated write workflow with multi-instance support.

An MCP server implementation that integrates with Odoo ERP systems, enabling AI assistants to interact with Odoo data and functionality through the Model Context Protocol.

Connects Claude Desktop or Claude Code to a company's Odoo instance with a one-click extension or installer, automatically negotiating the right API (web session, JSON-2, or JSON-RPC) for any Odoo version. Exposes tools that let Claude search, read, count, group, create, update, delete, and link Odoo records as the logged-in user, with an optional read-only mode.

This foundation-only service is intended to enable narrowly bounded, typed operations over Shayona business data, starting with an approval-bound, redacted-preview workflow for emailing customer service credentials. It is designed to keep usernames and decrypted passwords out of MCP results, previews, errors, logs, traces, and approval state.