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