get_entry_parameters — Arcology Knowledge Node MCP Tool Read-only
get_entry_parameters
(get entry parameters) is one of 9 tools on the
Arcology Knowledge Node
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_entry_parameters from your client
- Claude Code Arcology Knowledge Node get_entry_parameters run in your project directory
- Claude Desktop Arcology Knowledge Node get_entry_parameters ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Arcology Knowledge Node get_entry_parameters ~/.cursor/mcp.json
- VS Code Arcology Knowledge Node get_entry_parameters .vscode/mcp.json
- Zed Arcology Knowledge Node get_entry_parameters ~/.config/zed/settings.json
- Windsurf Arcology Knowledge Node get_entry_parameters ~/.codeium/windsurf/mcp_config.json
- Cline Arcology Knowledge Node get_entry_parameters ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Arcology Knowledge Node get_entry_parameters ~/.gemini/settings.json
- Grok Arcology Knowledge Node get_entry_parameters .mcp.json (in your project root)
- ChatGPT Arcology Knowledge Node get_entry_parameters Settings → Connectors → Advanced → Developer mode
- Claude.ai Arcology Knowledge Node get_entry_parameters Settings → Connectors → Add custom connector
- LangChain Arcology Knowledge Node get_entry_parameters pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http arcology-knowledge-node https://arcology-mcp.fly.dev/mcp
Other 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.