Sequentum MCP

What Sequentum MCP MCP server does

Sequentum MCP MCP server gives an MCP-compatible AI client access to Sequentum account operations. It can list, search, and inspect web scraping agents, retrieve versions, and restore an earlier agent version. It also exposes controls for starting, stopping, killing, and deleting runs, along with status and run-file queries.

The server covers scheduled execution as well. An assistant can inspect schedules, create or update cron-based schedules, enable or disable them, remove schedules, and review scheduled runs. Space-related tools provide access to Sequentum workspaces and the agents associated with them.

Usage and billing data are available through balance, spending, credit-history, usage, cost-breakdown, and run-cost tools. These capabilities support questions about recent runs, failures, extracted files, schedule state, and Sequentum consumption.

How it works

Sequentum hosts and operates the MCP endpoint at https://mcp.sequentum.com/mcp. The client connects using Streamable HTTP, with automatic SSE fallback where supported. After connection, the user signs in with a Sequentum account and approves OAuth permissions; the available tools then operate against that account’s data and agents.

The service follows standard MCP behavior and can be used by clients that support OAuth authentication and the supported HTTP transports. It also supports Client ID Metadata Documents, with Dynamic Client Registration as a fallback for client identification.

Setup and configuration

There is no current local installation step for the supported deployment. Add the remote URL to an MCP client, or select Sequentum MCP from a client’s connector directory when available. Claude.ai and Claude Desktop list it as a connector. Cursor, Windsurf, VS Code/GitHub Copilot, ChatGPT Developer Mode, and Claude Code have documented connection paths using the same endpoint.

For Claude Code, the documented direct command is:

claude mcp add --transport http sequentum https://mcp.sequentum.com/mcp

After adding the server, complete the OAuth browser flow. In Claude Desktop, connection is handled through the connector directory rather than a manually entered URL. Organization administrators may need to enable the connector for team or enterprise workspaces.

Tools and capabilities

Sequentum MCP MCP server exposes tools in these areas:

• Agent listing, searching, inspection, version retrieval, and version restoration
• Run start, stop, termination, deletion, status, and file access
• Download URL retrieval for files produced by runs
• Schedule creation, updates, activation, deactivation, deletion, and run history
• Space and space-agent inspection
• Credit balance, spending, credit history, usage, and cost reporting

These tools let an assistant answer operational questions or perform account actions, such as checking whether an agent is still running, starting an agent, finding the latest extracted file, or comparing agent costs.

Limitations and notes

The former local stdio server and sequentum-mcp npm package are deprecated. The deprecated path used SEQUENTUM_API_KEY, but the supported approach is the hosted OAuth endpoint. There is no supported self-hosted deployment described in the material.

Connecting the server exposes Sequentum account data and allows the MCP client to view, run, and manage scraping agents. Credentials should be protected, and access should be granted only to clients that are trusted with the account’s data and controls.