Terminology licenses — Medical Terminologies MCP MCP Resource

Terminology licenses is one of 4 resources on the Medical Terminologies MCP MCP server. Connect the server and your client can attach it as context.

by client

How to attach Terminology licenses from your client

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

Other resources on this server

• Server info
• CID-10 chapters
• Usage stats (hosted endpoint)

Medical Terminologies MCP also offers 3 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.