# cinch-connectivity-mcp v2.2.1
# Cinch Connectivity Solutions — MCP Product Data Server
# Protocol: MCP (Model Context Protocol) 2026-07-28 and 2025-11-25

## What This Server Does
Provides structured access to Cinch's electronic connector catalog:
parts lookup, parametric search, category browsing, cross-references,
compatibility data, document search, and data export.

## How To Use (IMPORTANT)
Transport: Streamable HTTP (JSON-RPC 2.0)
Endpoint: POST https://mcp.cinch.com/mcp
Session: Stateless — NO initialization handshake required
Protocol revisions: this endpoint answers both 2026-07-28 and 2025-11-25
Authentication: None required (public access)

Required headers:
  Content-Type: application/json
  Accept: application/json, text/event-stream

## Quick Start Examples

### List all available tools:
curl -X POST https://mcp.cinch.com/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","method":"tools/list","id":1,"params":{}}'

### Call a tool (keyword search):
curl -X POST https://mcp.cinch.com/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","method":"tools/call","id":1,"params":{"name":"cinch_search_keyword","arguments":{"query":"circular connector"}}}'

## Speaking 2026-07-28 (optional)
The examples above are the 2025-11-25 shape and keep working unchanged.
Send the shape below ONLY to speak 2026-07-28. Still no handshake.

A request is treated as 2026-07-28 when — and only when —
params._meta carries "io.modelcontextprotocol/protocolVersion". Sending the
Mcp-Method header without it leaves the request on the 2025-11-25 leg.

Additional required headers:
  Mcp-Method: <the same value as body.method>          (every request)
  Mcp-Name: <the same value as params.name>            (tools/call only)

Additional required params._meta keys:
  "io.modelcontextprotocol/protocolVersion": "2026-07-28"
  "io.modelcontextprotocol/clientCapabilities": {}     ({} is valid)

### List all available tools (2026-07-28):
curl -X POST https://mcp.cinch.com/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "Mcp-Method: tools/list" \
  -d '{"jsonrpc":"2.0","method":"tools/list","id":1,"params":{"_meta":{"io.modelcontextprotocol/protocolVersion":"2026-07-28","io.modelcontextprotocol/clientCapabilities":{}}}}'

### Call a tool (2026-07-28):
curl -X POST https://mcp.cinch.com/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "Mcp-Method: tools/call" \
  -H "Mcp-Name: cinch_search_keyword" \
  -d '{"jsonrpc":"2.0","method":"tools/call","id":1,"params":{"name":"cinch_search_keyword","arguments":{"query":"circular connector"},"_meta":{"io.modelcontextprotocol/protocolVersion":"2026-07-28","io.modelcontextprotocol/clientCapabilities":{}}}}'

Omitting Mcp-Method or Mcp-Name is answered -32020 (headers and body disagree).
Omitting either _meta key is answered -32602 (invalid _meta envelope).
"initialize" is not served on this leg — it answers -32601. Use the
2025-11-25 shape for it, or skip it: the session is stateless.

## Common Mistakes (avoid these)
- Using GET instead of POST for /mcp (GET is for SSE streams only)
- Using wrong method names: "list_tools", "mcp/discover", "call_tool", "get_tools"
  Correct methods: "tools/list", "tools/call", "initialize" (optional)
- Sending "mcp/initialize" — no initialization is needed, just call tools directly
- Missing the Accept header — must include "application/json, text/event-stream"

## Available Tools (19)
  - cinch_get_part: Cinch Quick Part Lookup
  - cinch_get_part_details: Cinch Complete Part Details
  - cinch_search_parts: Cinch Search Parts by Category
  - cinch_get_categories: Cinch Browse Categories
  - cinch_get_category_filters: Cinch Category Filter Options
  - cinch_get_related_parts: Cinch Related Parts
  - cinch_search_documents: Cinch Search Documents
  - cinch_search_keyword: Cinch Keyword Search
  - cinch_export_category: Cinch Export Category to Excel
  - cinch_get_new_products: Cinch New Products
  - cinch_product_viewer: Cinch Interactive Product Viewer
  - cinch_get_extended_relationships: Cinch Extended Relationships
  - cinch_competitor_xref: Cinch Competitor Cross-Reference
  - cinch_compatibility_viewer: Cinch Compatibility Viewer
  - cinch_new_products_viewer: Cinch New Products Viewer
  - cinch_compare_parts: Cinch Compare Parts
  - cinch_discover_by_attributes: Cinch Discover by Attributes
  - cinch_export_by_asset: Cinch Export by Asset Type
  - cinch_get_part_image: Cinch Product Image

## Discovery Endpoints
- GET https://mcp.cinch.com/ — Server info + quick start (JSON)
- GET https://mcp.cinch.com/.well-known/mcp.json — Machine-readable discovery (JSON)
- GET https://mcp.cinch.com/llms.txt — This file
- GET https://mcp.cinch.com/health — Health check + tool list