openapi_schema — MyReach MCP Resource
openapi_schema
is one of 3 resources on the
MyReach
MCP server. Connect the server and your client can attach it as context.
by client
How to attach openapi_schema from your client
- Claude Code MyReach Resource/openapi_schema run in your project directory
- Claude Desktop MyReach Resource/openapi_schema ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MyReach Resource/openapi_schema ~/.cursor/mcp.json
- VS Code MyReach Resource/openapi_schema .vscode/mcp.json
- Zed MyReach Resource/openapi_schema ~/.config/zed/settings.json
- Windsurf MyReach Resource/openapi_schema ~/.codeium/windsurf/mcp_config.json
- Cline MyReach Resource/openapi_schema ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MyReach Resource/openapi_schema ~/.gemini/settings.json
- Grok MyReach Resource/openapi_schema .mcp.json (in your project root)
- ChatGPT MyReach Resource/openapi_schema Settings → Connectors → Advanced → Developer mode
- Claude.ai MyReach Resource/openapi_schema Settings → Connectors → Add custom connector
- LangChain MyReach Resource/openapi_schema pip install langchain-mcp-adapters
Other resources on this server
MyReach also offers 4 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 14 November 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.