Sequentum Cloud MCP

The Sequentum MCP Server connects your AI coding assistant to Sequentum using the Model Context Protocol (MCP), giving your AI tools direct access to web scraping agents, run management, scheduling, analytics, and more. Sequentum hosts and manages a remote MCP server with OAuth authentication, so there's nothing to install.

Overview

sequentum-mcp makes the Sequentum platform directly accessible to MCP-compatible AI clients. From your editor or AI assistant, you can:

• Discover and manage web scraping agents

• Start, stop, and monitor runs in real time

• Configure schedules and batch operations across spaces

• Inspect run results, logs, and error diagnostics

• Track usage, billing, and credits

You can connect to the hosted OAuth MCP server (recommended) or run a local MCP server using Node.js and an API key.

Tool Reference | Troubleshooting | Changelog

Key Features

• Agent management: List, search, and get detailed information about your web scraping agents.

• Run automation: Start, stop, and monitor agent executions with real-time status tracking.

• Schedule management: Create and manage automated schedules using cron expressions.

• Analytics & diagnostics: Get run statistics, error analysis, and suggested fixes for failures.

• Space organization: Manage agent workspaces and run batch operations across spaces.

Security & Privacy

sequentum-mcp exposes your Sequentum account data to MCP clients, allowing them to view, run, and manage your web scraping agents. Keep your credentials secure and avoid sharing sensitive information that you don't want accessible to MCP clients.

• Account data access: Connected MCP clients can see agent metadata, runs, logs, and extracted files, depending on permissions granted.

• Actions: Clients can start, stop, and schedule agents if the granted permissions allow it.

• Credentials: Hosted mode uses OAuth tokens tied to your Sequentum account; local mode uses your Sequentum API key and has API access under that key.

• Client trust: Only configure MCP in clients and environments you trust, especially when using shared machines or team-wide configurations.

• Least privilege: Use separate accounts, API keys, or workspaces where appropriate to limit blast radius.

Avoid sharing configuration files, environment variables, or logs that contain API keys, OAuth tokens, or other sensitive information.

Getting Started

Add the Sequentum MCP server to your client with this configuration:

{
  "mcpServers": {
    "sequentum": {
      "url": "https://mcp.sequentum.com/mcp"
    }
  }
}

Most clients support the OAuth configuration. When you first connect, you'll be prompted to:

1. Log in with your Sequentum account

2. Accept the OAuth authorization

3. Grant access to the necessary permissions

Once authenticated, all tools become available in your client. For client-specific setup details, see Set Up Your Client below.

Set Up Your Client

Select your client below for specific setup instructions. All clients use the remote OAuth server at https://mcp.sequentum.com/mcp unless noted otherwise.

Cursor

Go to Cursor > Settings > Cursor Settings > MCP and follow the prompts to add the Sequentum MCP server. Cursor 1.0+ includes native OAuth and Streamable HTTP support.

You can also add the server manually by editing your mcp.json file using the configuration above.

Claude Desktop

Open developer tools via Settings > Developer > Edit Config, then add the configuration above to your config file. Restart Claude Desktop to pick up the changes.

Claude Code

Run the following command in your terminal:

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

Then launch Claude Code with claude. You'll be prompted to authenticate with OAuth to Sequentum.

VS Code / GitHub Copilot

Open the Command Palette with Ctrl+Shift+P (or Cmd+Shift+P on macOS) and select MCP: Add Server. Enter the Sequentum MCP server URL:

https://mcp.sequentum.com/mcp

Windsurf

Configure via the Configure MCP option in Cascade (Cmd+L or Ctrl+L). Add the Sequentum MCP server URL:

https://mcp.sequentum.com/mcp

Other Clients

The Sequentum MCP Server follows standard MCP protocols and works with any client that supports:

• OAuth authentication (recommended)

• Streamable HTTP with automatic SSE fallback

Use the server URL https://mcp.sequentum.com/mcp in your client's MCP configuration.

The server supports Client ID Metadata Documents (CIMD) as the preferred client identification method, with Dynamic Client Registration (RFC 7591) as a fallback. MCP clients that support CIMD (such as Cursor) can use their own URL as a client_id without any prior registration.

Alternative: Local Setup (API Key)

If you prefer to run the MCP server locally (e.g., for custom deployments, offline use, or CI/CD pipelines), you can use npx with an API key instead of the hosted OAuth server.

Requirements for local setup:

• Node.js v18 or higher

• npm

• Sequentum API key

Add the following config to your MCP client:

{
  "mcpServers": {
    "sequentum": {
      "command": "npx",
      "args": ["-y", "sequentum-mcp"],
      "env": {
        "SEQUENTUM_API_KEY": "sk-your-api-key-here"
      }
    }
  }
}

Get Your API Key

1. Log in to the Sequentum Control Center

2. Go to Settings > API Keys

3. Click Create API Key and copy the generated key (starts with sk-)

Custom Sequentum Instance

To connect to a custom Sequentum deployment, add the SEQUENTUM_API_URL environment variable:

{
  "mcpServers": {
    "sequentum": {
      "command": "npx",
      "args": ["-y", "sequentum-mcp"],
      "env": {
        "SEQUENTUM_API_KEY": "sk-your-api-key-here",
        "SEQUENTUM_API_URL": "https://your-custom-instance.sequentum.com"
      }
    }
  }
}

Local Environment Variables

Example Usage

Once connected, try these prompts to start using Sequentum context in your AI assistant:

What agents ran yesterday?
Run agent <agent name> now.
Is agent <agent name> still running?
What agents are scheduled to run today?
Download the extracted data from agent <agent name>.
How many records were found the last time <agent name> was run?
What is my current balance?
Schedule agent <agent name> to run every Monday at 9am.
Look at the run log for <agent name> run at 9:22am. What caused the agent to fail?

Available Tools

The Sequentum MCP Server provides tools across 8 categories for interacting with the Sequentum platform. See the Tool Reference for detailed documentation.

• Agent Management (3 tools)

  • list_agents

  • get_agent

  • search_agents

• Run Management (5 tools)

  • get_agent_runs

  • get_run_status

  • start_agent

  • stop_agent

  • kill_agent

• File Management (2 tools)

  • get_run_files

  • get_file_download_url

• Version Management (2 tools)

  • get_agent_versions

  • restore_agent_version

• Schedule Management (4 tools)

  • list_agent_schedules

  • create_agent_schedule

  • delete_agent_schedule

  • get_scheduled_runs

• Billing & Credits (3 tools)

  • get_credits_balance

  • get_spending_summary

  • get_credit_history

• Space Management (5 tools)

  • list_spaces

  • get_space

  • get_space_agents

  • search_space_by_name

  • run_space_agents

• Analytics & Diagnostics (4 tools)

  • get_runs_summary

  • get_records_summary

  • get_run_diagnostics

  • get_latest_failure

Troubleshooting

For more troubleshooting help, see the Troubleshooting Guide.

Links

• Sequentum MCP Server

• Sequentum Dashboard

• Sequentum API Documentation

• Model Context Protocol

License

MIT © Sequentum