Entity Profile Widget — GleanMark Trademark Search MCP Resource

Entity Profile Widget is one of 14 resources on the GleanMark Trademark Search MCP server. Connect the server and your client can attach it as context.

by client

How to attach Entity Profile Widget from your client

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

Other resources on this server

• Search Results Widget
• Trademark Detail Widget
• Mark Comparison Widget
• Owner Search Widget
• Attorney Search Widget
• Ranked Results Widget
• Workspace List Widget
• Workspace Activity Widget
• Workspace Summary Widget
• Portfolio Marks Widget
• Risk Summary Widget
• Tracked Owners Widget
• TTAB Activity Widget

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.