SignalEDI MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SIGNALEDI_API_KEY | No | Workspace key with the 'platform' scope for send/partner/QBO tools. If not set, the server runs in demo mode. | |
| SIGNALEDI_BASE_URL | No | Base URL for the SignalEDI API. Defaults to https://signaledi.com. | https://signaledi.com |
| SIGNALEDI_MCP_TELEMETRY | No | Set to '0' to disable local metric lines (redacted per-tool latency/success metrics to stderr). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsA | Search the bundled public SignalEDI developer index. Returns authoritative MCP resource URIs and short snippets; it does not search customer data or private partner guides. Local read-only operation. |
| get_document_schemaA | Get a public X12 starter schema for the local inventory (850/810/856 baseline, 837 Professional partial). Returns an honest capability label and is explicitly not a trading-partner implementation guide. Refuses EDIFACT, HL7, and unknown sets. Local read-only operation. |
| generate_integration_exampleA | Generate a sandbox-safe cURL, Node.js, or Python example for the current SignalEDI REST contract. Uses environment-variable placeholders and synthetic values, sets outbound environment to SANDBOX, refuses production hosts, and never embeds credentials. Local read-only operation. |
| explain_edi_errorA | Explain an EDI validation or functional-ack error using the local X12 dictionary (meaning, typical cause, fix, lookup_x12 cross-refs). Never calls the network; works in the docs profile. Local read-only operation. |
| generate_test_documentA | Render a synthetic X12 sample for the local inventory (850/810/856 baseline, 837 Professional partial). Returns an honest capability label. controlNumber and the transaction's primary date apply to every fixture; poNumber applies only to 850 and 810. Refuses EDIFACT, HL7, and unknown sets. Local only; works in the docs profile. Local read-only operation. |
| lookup_x12A | Search the local X12 dictionary by segment id, ack code, or free text (segment names and purposes). Local only; works in the docs profile. Local read-only operation. |
| lookup_element_definitionA | Alias for lookup_x12 — search segment maps and ack codes (850/810/856/837 dictionaries). Local read-only operation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| scaffold-integration | Plan and scaffold a sandbox-first SignalEDI integration without performing writes. |
| onboard-partner | Plan partner onboarding with public schemas and an explicitly provisioned sandbox. |
| debug-rejection | Diagnose a functional acknowledgement or validation rejection. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| SignalEDI MCP quickstart | Install, choose a profile, configure, and run first prompts. |
| SignalEDI OpenAPI | Live public /api/v1 OpenAPI document from the hosted engine; the request sends no caller content or credentials. |
| X12 reference | Segment and acknowledgement-code reference used by developer tools. |
| External developer workflows | Capability profiles, environment boundaries, governed connection control-plane safety, and the recommended MCP-to-API workflow. |
| X12 850 Purchase Order starter schema | Public baseline fields and segments; not a partner-specific implementation guide. |
| X12 810 Invoice starter schema | Public baseline fields and segments; not a partner-specific implementation guide. |
| X12 856 Ship Notice / Manifest starter schema | Public baseline fields and segments; not a partner-specific implementation guide. |
| X12 837 Health Care Claim - Professional starter schema | Public baseline fields and segments; not a partner-specific implementation guide. |
TDQS
Scored across 7 tools
lookup_x12 and lookup_element_definition are explicitly the same operation under different names, creating direct overlap. search_docs and lookup_x12 also share a search-like purpose, though descriptions differentiate them. Other tools are clearly distinct.
All tool names follow a consistent snake_case verb_noun pattern (search_, get_, lookup_, generate_, explain_). No mixed conventions or irregular prefixes exist.
With 7 tools, the server is well within the ideal 3-15 range for its EDI reference scope. The one redundant alias tool is a minor blemish but does not make the set bloated or thin.
The tool surface covers the main workflows for an EDI documentation/sandbox server: searching docs, retrieving schemas, looking up X12 definitions, generating examples, explaining errors, and producing test documents. Minor gaps exist (e.g., no explicit supported-transaction-set listing), but no critical dead ends.