chaport_get_chat — Chaport MCP by usefulapi MCP Tool
chaport_get_chat
(chaport get chat) is one of 14 tools on the
Chaport MCP by usefulapi
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call chaport_get_chat from your client
- Claude Code Chaport MCP by usefulapi chaport_get_chat run in your project directory
- Claude Desktop Chaport MCP by usefulapi chaport_get_chat ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Chaport MCP by usefulapi chaport_get_chat ~/.cursor/mcp.json
- VS Code Chaport MCP by usefulapi chaport_get_chat .vscode/mcp.json
- Zed Chaport MCP by usefulapi chaport_get_chat ~/.config/zed/settings.json
- Windsurf Chaport MCP by usefulapi chaport_get_chat ~/.codeium/windsurf/mcp_config.json
- Cline Chaport MCP by usefulapi chaport_get_chat ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Chaport MCP by usefulapi chaport_get_chat ~/.gemini/settings.json
- Grok Chaport MCP by usefulapi chaport_get_chat .mcp.json (in your project root)
- ChatGPT Chaport MCP by usefulapi chaport_get_chat Settings → Connectors → Advanced → Developer mode
- Claude.ai Chaport MCP by usefulapi chaport_get_chat Settings → Connectors → Add custom connector
- LangChain Chaport MCP by usefulapi chaport_get_chat pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http chaport https://chaport.usefulapi.io/mcpOther tools on this server
- chaport_whoami
- chaport_list_operators
- chaport_get_operator
- chaport_set_operator_status
- chaport_list_visitors
- chaport_get_visitor
- chaport_update_visitor
- chaport_get_last_visitor_chat
- chaport_list_chat_events
- chaport_get_chat_event
- chaport_update_last_visitor_chat
- chaport_send_operator_message
- chaport_list_webhooks
This list was read from the server itself, by connecting to it and calling tools/list on 24 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.