{"version":"2.1.285","anchor":"sdkmcp-surface-names-mcpconnect-sessionappend-mcp-serv","canonical_anchor":"sdkmcp-surface-names-mcpconnect-sessionappend-mcp-serv","heading":"New names for MCP connections and appending to a session","tier":"internal","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/sdkmcp-surface-names-mcpconnect-sessionappend-mcp-serv","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### New names for MCP connections and appending to a session\n\nThree new names appear for connecting to MCP, appending to a session and a plain MCP server call, next to existing ones\n\n**Unclear.** What uses these names and whether anything restricts them is not clear.\n\n**What**\n\nThree new names appear alongside existing ones:\n\n- `mcp.connect`, next to `mcp.call`.\n\n- `session.append`, next to `session.send`.\n\n- A new MCP server event for a plain call, next to the existing one for a file call.\n\nMCP (Model Context Protocol) is the way Claude Code connects to outside tools and services. The names look like new actions for controlling Claude Code from code and new usage-reporting names.\n\n**Why**\n\nThey suggest new ways to connect to MCP and to add to a session from code.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}