Skip to main content
Glama
tzenderman

Cin7 Core Meta MCP Server

by tzenderman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SERVER_URLNoYour MCP server's public URL (e.g., https://your-server.example.com). Required for HTTP/OAuth mode.
CIN7_API_KEYNoYour Cin7 Application Key from Integrations → API.
MCP_LOG_FILENoEnable file logging with rotation (optional).
CIN7_BASE_URLNoOverride the Cin7 base URL (default: https://inventory.dearsystems.com/ExternalApi/v2/).https://inventory.dearsystems.com/ExternalApi/v2/
MCP_LOG_LEVELNoLogging level (default: INFO).INFO
ALLOWED_EMAILSNoComma-separated list of allowed email addresses (leave empty to allow all authenticated users).
CIN7_ACCOUNT_IDNoYour Cin7 AccountID from Integrations → API.
ISSUE_REPORT_PATHNoPath where report_issue appends its ISSUE_REPORT lines (default: ./data/issue_reports.log)../data/issue_reports.log
SCALEKIT_CLIENT_IDNoScaleKit application client ID. Required for HTTP/OAuth mode.
SCALEKIT_RESOURCE_IDNoScaleKit resource identifier (e.g., res_xxx). Required for HTTP/OAuth mode.
SCALEKIT_CLIENT_SECRETNoScaleKit application client secret. Required for HTTP/OAuth mode.
SCALEKIT_ENVIRONMENT_URLNoScaleKit environment URL (e.g., https://yourapp.scalekit.com). Required for HTTP/OAuth mode.
SCALEKIT_INTERCEPTOR_SECRETNoSecret for verifying interceptor payloads. Required for HTTP/OAuth mode.

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

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_api_endpointsA

Search Cin7 Core's REST endpoints by keyword.

Args: keyword: Substring to match against path, summary, group, and parameter names. Case-insensitive. methods: Optional list of HTTP methods to restrict results to. Valid values: GET, POST, PUT, PATCH, DELETE. limit: Maximum number of results to return. Default 25.

Returns: {"results": [{"method","path","summary","group"}, ...], "total": int, "truncated": bool}. On empty keyword, returns the same shape with an additional error key.

get_api_endpoint_schemaA

Return the full schema for one Cin7 API endpoint.

Args: method: HTTP verb. Case-insensitive. path: Endpoint path. Leading slashes are stripped; the lookup is case-sensitive on the path itself.

Returns: {"method","path","group","summary","description", "query_params","request_body_schema","request_body_example", "response_schema","response_example"}. On unknown endpoint, returns {"error": "..."} with a did_you_mean hint if a close match exists.

invoke_api_endpointA

Validate, then execute, a Cin7 Core REST API call.

Args: method: HTTP verb (GET, POST, PUT, PATCH, DELETE). Case-insensitive. path: Endpoint path, e.g. "Product", "advanced-purchase", "sale/order". Leading slashes are stripped. query_params: Query-string parameters. Validated against the endpoint's declared params. body: JSON request body. Validated against the endpoint's required body fields (extras are permitted).

Returns: Success: {"status": 200, "data": <json>, "rate_limit_remaining": "59"}. Cin7 4xx response: {"status": 4xx, "data": <body or null>, "errors": [...]}. Validation failure: {"status": null, "data": null, "errors": [...]}.

Raises: Cin7AuthError | Cin7NotFoundError | Cin7RateLimitError | Cin7APIError: Transport-level failures the model cannot fix.

report_issueA

File a structured bug report for later developer review.

Args: summary: One-line headline of what went wrong. tool_name: Which MCP tool was being used when the issue occurred. One of list_api_endpoints, get_api_endpoint_schema, invoke_api_endpoint. tool_arguments: The exact kwargs you passed to the tool. Include enough information for someone else to reproduce the call. observed_behavior: What actually happened. Be specific. expected_behavior: What you expected to happen instead. severity: low, medium, or high. Default medium. error_message: Exception class + message, if one was raised. response_excerpt: Truncated snippet of the response body. Capped at 2000 chars. client_context: Optional notes — model name, conversation topic, any context that would help the developer reproduce.

Returns: {"report_id", "stored_in_file", "stored_in_log", "thanks"} on success, or {"error": "..."} if a required field is invalid.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.5/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a unique, clearly defined purpose: listing endpoints, getting schemas, invoking endpoints, and reporting issues. There is no overlap or ambiguity.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern (e.g., get_api_endpoint_schema, invoke_api_endpoint, list_api_endpoints, report_issue).

Tool Count5/5

With 4 tools, the server is well-scoped for managing API interactions (discovery, schema inspection, execution, and issue reporting). Neither too sparse nor excessive.

Completeness4/5

The set covers core workflows: discover endpoints, fetch schemas, make API calls, and report issues. A minor gap is the lack of explicit rate limit querying, but rate limit info is included in invocation responses.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources