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