GI account / connectivity — Genomic Intelligence MCP Resource

GI account / connectivity is one of 6 resources on the Genomic Intelligence MCP server. Connect the server and your client can attach it as context.

by client

How to attach GI account / connectivity from your client

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

Other resources on this server

• GI model catalog
• GI task overview
• GI OpenAPI contract
• GI demo sequences
• GI recent jobs

Genomic Intelligence 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.