Sequentum MCP

Sequentum MCP

The Sequentum MCP Server connects your AI coding assistant to Sequentum using the Model Context Protocol (MCP), giving your AI tools the ability to create 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.

Tool Reference | Prompts Reference | Resources Reference | Troubleshooting | Changelog

Key Features

• Agent management: Build, 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.

Disclaimers

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.

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. Claude.ai and Claude Desktop are simpler still — Sequentum MCP is listed in Claude's connector directory, so there is nothing to enter by hand; see Claude.ai and Claude Desktop below. For other clients, 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.ai and Claude Desktop

Sequentum MCP is listed in Claude's connector directory, so there is no URL to enter by hand and no custom connector to create.

1. Open Settings and go to Connectors.
2. Browse the Directory, select Connectors, and find Sequentum MCP.
3. Click Connect and sign in with your Sequentum account.

Team and Enterprise workspaces: connector availability is governed at org level, so an admin may need to enable Sequentum MCP before members can connect from their own accounts.

Enabling per conversation: once connected, enable Sequentum in an individual conversation via the + button near the message composer, then select Connectors.

ChatGPT

Note: While the Sequentum app is pending directory approval, you can connect via Developer Mode. Apps & Connectors → Developer Mode is currently available on Plus, Pro, Business, Enterprise, and Education plans (Education is web-only). On Business / Enterprise / Education accounts, only workspace owners and admins can access Advanced settings — regular members will not see the option. See OpenAI's Developer Mode documentation for current eligibility.

1. In ChatGPT, go to Settings > Apps & Connectors > Advanced settings and enable Developer mode.
2. Navigate to Settings > Apps & Connectors and click Create app (it appears once Developer mode is enabled).
3. Enter the connector name Sequentum and URL: https://mcp.sequentum.com/mcp
4. Click Create. You'll be prompted to sign in with your Sequentum account via OAuth.

Once connected, enable Sequentum in a conversation via the + button near the message composer, then select your connector from the list.

Claude Code

Connect Sequentum MCP once from the connector directory (see Claude.ai and Claude Desktop above) and it is available in Claude Code on the same account.

To add it directly instead — useful per-project or in scripts:

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

Then launch Claude Code with claude and type /mcp to trigger the OAuth browser flow.

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.

Agents (auth.md)

An autonomous agent with no browser can register itself on behalf of a user instead of running the OAuth flow above. The server publishes no registration endpoint of its own: GET https://mcp.sequentum.com/auth.md (and /.well-known/auth.md) redirects to the manifest served by the Sequentum Control Center, which is the authorization server and holds the users, the claim page and the signing key. The agent follows that manifest:

1. Register with the user's email and the scopes it needs.
2. Show the user the verification link and code. The user signs in to Sequentum, enters the code and approves.
3. Poll until the claim completes, then exchange the identity assertion for an access token, passing resource=https://mcp.sequentum.com.
4. Call /mcp with that token as a bearer. Scope enforcement is the same as for any other token, so a tool outside the granted scopes is answered with an HTTP 403 insufficient_scope challenge.

There are no refresh tokens in this flow: when the access token expires, exchange the identity assertion again. Each exchange returns a new identity assertion and replaces the one you sent, so store the new one every time; the old one stops working shortly after. To try it against QA, see docs/oauth-scope-probe.md.

Local stdio mode (removed)

Running the server locally over stdio with SEQUENTUM_API_KEY (npx sequentum-mcp) was removed in 3.0.0. Connect to https://mcp.sequentum.com/mcp instead — see Set Up Your Client. Sequentum API keys still work for the REST API.

Example Usage

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

What agents ran yesterday?

Run agent now. Is agent still running? What agents are scheduled to run today? Download the extracted data from agent . How many records were found the last time was run? What is my current balance? Which agents cost the most this month? Schedule agent to run every Monday at 9am. Look at the run log for run at 9:22am. What caused the agent to fail? Show me the cost breakdown for agent in January. What were the most expensive runs for agent ? How much did I spend on server time vs exports last week?

Available Tools

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

• Agent Management (5 tools)
• list_agents
• get_agent
• search_agents
• get_agent_search_count
• get_personal_agent_count
• Run Management (7 tools)
• get_agent_runs
• get_agent_run_summary
• get_run_status
• start_agent
• stop_agent
• kill_agent
• delete_run
• File Management (2 tools)
• get_run_files
• get_file_download_url
• Version Management (2 tools)
• get_agent_versions
• restore_agent_version
• Schedule Management (8 tools)
• list_agent_schedules
• get_agent_schedule
• create_agent_schedule
• update_agent_schedule
• enable_agent_schedule
• disable_agent_schedule
• delete_agent_schedule
• get_scheduled_runs
• Billing & Credits (6 tools)
• get_credits_balance
• get_spending_summary
• get_credit_history
• get_agents_usage
• get_agent_cost_breakdown
• get_agent_runs_cost
• Space Management (6 tools)
• list_spaces
• get_space
• get_space_agents
• get_space_agent_count
• search_space_by_name
• run_space_agents
• Analytics & Diagnostics (4 tools)
• get_runs_summary
• get_records_summary
• get_run_diagnostics
• get_latest_failure
• Agent Builder (3 tools)
• start_agent_build
• get_agent_build_status
• [`stop_a