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