# BigHub MCP Production Suite — Cursor Rules & AI Assistant Directives

You have access to the Model Context Protocol (MCP) Production Suite servers connected via stdio or SSE.

## Connected Servers
- `mcp-production-suite-ts`: TypeScript MCP reference server running with official `@modelcontextprotocol/sdk`.
- `mcp-production-suite-py`: Python MCP reference server running with official `mcp` Python SDK.
- `mcp-production-suite-sse`: SSE transport endpoint for remote or containerized tool execution (`http://localhost:3001/sse`).

## Operational Guidelines for Tool Invocations
1. **Schema Validation**: All tool parameters adhere strictly to JSON-RPC 2.0 schemas. Always provide required parameters as structured key-value pairs matching tool specifications.
2. **Error Handling**:
   - Inspect `isError` flags in MCP tool responses.
   - If an error code `-32602` (Invalid params) is returned, verify the parameter types and schema definitions before retrying.
   - Never suppress standard JSON-RPC protocol error codes.
3. **Transport Behavior**:
   - Stdio transport communicates over standard I/O streams. Never output raw diagnostic logs or `console.log` to stdout in MCP servers; use stderr or structured logging.
   - In Python, ensure `-u` unbuffered mode is active to prevent handshake timeouts.
4. **Environment Isolation**:
   - MCP tools execute in the context of the user's host environment or docker container. Keep execution scoped and idempotent.
