invoke — google oauth langchain agent MCP Tool
invoke
(invoke) is one of 2 tools on the
google oauth langchain agent
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call invoke from your client
- Claude Code google oauth langchain agent invoke run in your project directory
- Claude Desktop google oauth langchain agent invoke ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor google oauth langchain agent invoke ~/.cursor/mcp.json
- VS Code google oauth langchain agent invoke .vscode/mcp.json
- Zed google oauth langchain agent invoke ~/.config/zed/settings.json
- Windsurf google oauth langchain agent invoke ~/.codeium/windsurf/mcp_config.json
- Cline google oauth langchain agent invoke ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI google oauth langchain agent invoke ~/.gemini/settings.json
- Grok google oauth langchain agent invoke .mcp.json (in your project root)
- ChatGPT google oauth langchain agent invoke Settings → Connectors → Advanced → Developer mode
- Claude.ai google oauth langchain agent invoke Settings → Connectors → Add custom connector
- LangChain google oauth langchain agent invoke pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http google-oauth-langchain-agent https://google-auth-oauthlib-langchain-la-c1a755.getvda.ai/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.