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