Skip to main content
​
MCP server 2.0
MCP server 2.0 is a breaking release. If you connect to https://mcp.sequentum.com/mcp, check each item below.Transport and runtime
  • Node 20 is the minimum runtime for the deprecated local stdio path (see Connect). Node 18 fails at install.
  • The HTTP transport is stateless. Mcp-Session-Id is ignored entirely — there is no per-client session state. GET /mcp no longer opens an SSE stream; it returns 405 Method Not Allowed (or 401 first, with the RFC 9728 WWW-Authenticate challenge, if unauthenticated). DELETE /mcp is a no-op that always answers 200.
  • MAX_SESSIONS is no longer read. Remove it from any deployment configuration.
  • Mcp-Method is required on requests carrying the 2026-07-28 _meta envelope, and Mcp-Name on name-carrying requests (tools/call, prompts/get, and resources/read). Clients on 2025-11-25 or earlier — including every existing connector that hasn’t opted into the envelope — are unaffected and need send neither.
Error responses
  • Rate-limit error code changed from -32029 to -32010. MCP 2026-07-28 reserves -32020..-32099 for the specification itself.
  • An unknown tool name is now a protocol error, not a tool result. tools/call with an unrecognized name previously returned HTTP 200 with {result: {content: [...], isError: true}}; it now returns {error: {code: -32602, message: "Tool X not found"}}. If you branched on isError to detect an unknown tool, handle the JSON-RPC error instead.
  • Schema-invalid tool arguments now fail before the handler runs, with different message text. A missing required parameter previously produced Error: Invalid parameter 'agentId': ... and now produces Input validation error: Invalid arguments for tool get_agent: data must have required property 'agentId'.
  • Unknown or invalid resource URIs return -32602 (invalid params) instead of -32603 (internal error).
Result shapes
  • get_agent_runs and search_agents now return an object instead of a bare array. get_agent_runs returns { runs, returned, limit, truncated } and search_agents returns { agents, returned, limit, truncated }, each with an extra note when the page came back full. The list itself is unchanged, but if you read the result as an array, read runs or agents from it instead. The wrapper is what makes a capped page distinguishable from a complete one.
New tools
  • Four exact-count tools answer “how many” without counting a capped list: get_agent_run_summary (overall plus per-status run totals for an agent), get_agent_search_count, get_space_agent_count, and get_personal_agent_count. See Tools.
OAuth discovery
  • /.well-known/oauth-authorization-server no longer returns a metadata document. It answers 302 with a Location pointing at the authorization server’s own document. Clients that follow redirects are unaffected; a client that read the body without following the redirect must now follow it, or read authorization_servers from /.well-known/oauth-protected-resource.
​
stdio transport and API-key auth deprecated for MCP
  • The stdio transport and SEQUENTUM_API_KEY authentication for the MCP server are deprecated and will be removed in a future release. Connect to https://mcp.sequentum.com/mcp over HTTP with OAuth 2.1 — see Connect.
  • The sequentum-mcp npm package is deprecated. Existing installs keep working.
  • There is no supported self-hosted deployment. If you need Sequentum MCP somewhere that can’t reach mcp.sequentum.com, contact support.
  • This applies to the MCP server only. Sequentum API keys remain fully supported for the REST API.
​
Docs site overhaul
  • New Mintlify-based documentation site at docs.sequentum.com (replaces the old Confluence).
  • Information architecture rebuilt around Agent Builder and an API-first reference.
  • Migrated extraction-command reference content from the legacy Cloud Manual.
​
Agent Builder GA
  • Agent Builder is generally available. Build extraction agents from a single prompt.
  • New API surface under /api/v1/agent-builder for programmatic session control.