OpenAPI specification & receptivity reference — Uphealth Signal MCP Resource

OpenAPI specification & receptivity reference is one of 2 resources on the Uphealth Signal MCP server. Connect the server and your client can attach it as context.

by client

How to attach OpenAPI specification & receptivity reference from your client

• Claude Code Uphealth Signal Resource/OpenAPI specification & receptivity reference run in your project directory
• Claude Desktop Uphealth Signal Resource/OpenAPI specification & receptivity reference ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Uphealth Signal Resource/OpenAPI specification & receptivity reference ~/.cursor/mcp.json
• VS Code Uphealth Signal Resource/OpenAPI specification & receptivity reference .vscode/mcp.json
• Zed Uphealth Signal Resource/OpenAPI specification & receptivity reference ~/.config/zed/settings.json
• Windsurf Uphealth Signal Resource/OpenAPI specification & receptivity reference ~/.codeium/windsurf/mcp_config.json
• Cline Uphealth Signal Resource/OpenAPI specification & receptivity reference ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Uphealth Signal Resource/OpenAPI specification & receptivity reference ~/.gemini/settings.json
• Grok Uphealth Signal Resource/OpenAPI specification & receptivity reference .mcp.json (in your project root)
• ChatGPT Uphealth Signal Resource/OpenAPI specification & receptivity reference Settings → Connectors → Advanced → Developer mode
• Claude.ai Uphealth Signal Resource/OpenAPI specification & receptivity reference Settings → Connectors → Add custom connector
• LangChain Uphealth Signal Resource/OpenAPI specification & receptivity reference pip install langchain-mcp-adapters

Other resources on this server

• Signal template catalog & cue vocabulary

Uphealth Signal also offers 2 prompts — things you invoke, where a resource is context you attach.

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.