how_to_connect — async.elixirconf MCP Tool
how_to_connect
(how to connect) is one of 2 tools on the
async.elixirconf
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call how_to_connect from your client
- Claude Code async.elixirconf how_to_connect run in your project directory
- Claude Desktop async.elixirconf how_to_connect ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor async.elixirconf how_to_connect ~/.cursor/mcp.json
- VS Code async.elixirconf how_to_connect .vscode/mcp.json
- Zed async.elixirconf how_to_connect ~/.config/zed/settings.json
- Windsurf async.elixirconf how_to_connect ~/.codeium/windsurf/mcp_config.json
- Cline async.elixirconf how_to_connect ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI async.elixirconf how_to_connect ~/.gemini/settings.json
- Grok async.elixirconf how_to_connect .mcp.json (in your project root)
- ChatGPT async.elixirconf how_to_connect Settings → Connectors → Advanced → Developer mode
- Claude.ai async.elixirconf how_to_connect Settings → Connectors → Add custom connector
- LangChain async.elixirconf how_to_connect pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http async https://async.elixirconf.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.