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