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 Desktop uses a different setup via Custom Connectors — see 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 Desktop

> Note: Custom connectors are currently in beta. Free plan users are limited to one custom connector.

Claude Desktop connects to remote MCP servers using Custom Connectors rather than the config file. The setup differs based on your plan type. For full details, see Claude's custom connectors documentation.

Free, Pro, and Max plans:

1. Navigate to Settings > Connectors.
2. Click "Add custom connector" at the bottom of the section.
3. Enter the Sequentum MCP server URL: https://mcp.sequentum.com/mcp
4. Click "Add" to finish.

Team and Enterprise plans:

An Owner or Primary Owner must first add the connector to the organization:

1. Navigate to Organization settings > Connectors.
2. Click "Add custom connector" at the bottom of the section.
3. Enter the Sequentum MCP server URL: https://mcp.sequentum.com/mcp
4. Click "Add" to finish.

Then, each team member connects individually:

1. Navigate to Settings > Connectors.
2. Find the Sequentum connector in the list (it will have a "Custom" label).
3. Click "Connect" to authenticate.

Enabling per conversation:

Once configured, enable the Sequentum connector in individual conversations via the "+" button on the lower left of the chat interface, 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

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

| Variable | Required | Default | Description |
|----------|----------|---------|-------------|
| SEQUENTUM_API_KEY | Yes | -- | Your Sequentum API key (format: sk-...). Get this from the Sequentum Control Center under Settings > API Keys. |
| SEQUENTUM_API_URL | No | https://dashboard.sequentum.com | The base URL of your Sequentum instance. Override if using a custom deployment. |

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?
Which agents cost the most this month?
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?
Show me the cost breakdown for agent <agent name> in January.
What were the most expensive runs for agent <agent name>?
How much did I spend on server time vs exports last week?

Available Tools

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

<!-- BEGIN AUTO GENERATED TOOLS -->

- Agent Management (3 tools)
- list_agents
- get_agent
- search_agents
- Run Management (6 tools)
- get_agent_runs
- 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 (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
- Agent Builder (3 tools)
- start_agent_build
- get_agent_build_status
- stop_agent_build

<!-- END AUTO GENERATED TOOLS -->

Available Prompts

The server includes 9 reusable prompt templates that guide the AI through common multi-step workflows. See the Prompts Reference for detailed documentation.

<!-- BEGIN AUTO GENERATED PROMPTS -->

- Debugging & Diagnostics
- debug-agent -- Diagnose why an agent is failing
- compare-runs -- Compare last successful vs failed run
- Health & Monitoring
- agent-health-check -- Comprehensive health overview for an agent
- daily-operations-report -- Daily ops report across all agents
- space-overview -- Overview of all agents in a space
- Execution
- run-and-monitor -- Start an agent and monitor until completion
- schedule-agent -- Walk through creating a schedule
- Billing & Costs
- spending-report -- Spending and credits report
- cost-analysis -- Analyze costs across agents
- Agent Building
- build-agent-from-prompt -- Build a new agent from a natural language description
- inspect-agent-draft -- Inspect a build session and decide whether to save or discard

<!-- END AUTO GENERATED PROMPTS -->

Available Resources

The server exposes 18 read-only resources (7 static + 11 templates) that AI clients can browse and pull into context. See the Resources Reference for detailed documentation.

<!-- BEGIN AUTO GENERATED RESOURCES -->

- Static Resources (7)
- sequentum://agents -- First page of all agents
- sequentum://spaces -- All accessible spaces
- sequentum://billing/balance -- Current credits balance
- sequentum://billing/spending -- Monthly spending summary
- sequentum://billing/agents-usage -- Top agents by cost
- sequentum://analytics/runs -- Runs in the last 24 hours
- sequentum://analytics/upcoming-schedules -- Scheduled runs for next 7 days
- Resource Templates (11)
- sequentum://agents/{agentId} -- Agent detail with configuration
- sequentum://agents/{agentId}/versions -- Agent version history
- sequentum://agents/{agentId}/schedules -- Agent scheduled tasks
- sequentum://agents/{agentId}/cost-breakdown -- Agent cost by usage type
- sequentum://agents/{agentId}/runs -- Agent run history
- sequentum://agents/{agentId}/runs/{runId} -- Specific run status
- sequentum://agents/{agentId}/runs/{runId}/files -- Run output files
- sequentum://agents/{agentId}/runs/{runId}/diagnostics -- Run error diagnostics
- sequentum://agents/{agentId}/latest-failure -- Most recent failure diagnostics
- sequentum://spaces/{spaceId} -- Space details
- sequentum://spaces/{spaceId}/agents -- Agents in a space

<!-- END AUTO GENERATED RESOURCES -->

Troubleshooting

| Error | Solution |
|-------|----------|
| OAuth login not opening | Ensure your client supports OAuth and Streamable HTTP. Try restarting the client. For Claude Desktop, use Custom Connectors instead of the config file. |
| Connection refused | Verify the URL is https://mcp.sequentum.com/mcp and check your network connection. |
| SEQUENTUM_API_KEY required | Local mode only. Add your API key to the env section of the MCP config. |
| API Error 401: Unauthorized | Your API key or OAuth token is invalid or expired. Re-authenticate or generate a new key. |
| API Error 404: Not Found | The agent, run, or file doesn't exist, or you don't have access to it. |
| API Error 429: Too Many Requests | Rate limit exceeded. Wait a moment and try again. |

For more troubleshooting help, see the Troubleshooting Guide.

CORS Origin Allowlist

When the MCP server is accessed from a browser (e.g. the Claude web app or the ChatGPT connector), it checks the Origin header against an allowlist. By default the following origins are permitted:

- https://claude.ai, https://claude.com, and all subdomains (e.g. team.claude.ai)
- https://chatgpt.com, https://platform.openai.com, and all subdomains under chatgpt.com (e.g. connector.chatgpt.com)
- https://dashboard.sequentum.com
- https://mcp.sequentum.com
- http://localhost:<port>, http://127.0.0.1:<port>, and http://[::1]:<port> when DEBUG=1

To add your own origins (e.g. an internal dashboard), set the ALLOWED_ORIGINS environment variable to a comma-separated list of exact origins:

ALLOWED_ORIGINS="https://my-dashboard.example.com,https://other.example.com"

These origins are appended to the defaults — Claude, ChatGPT, and Sequentum access is preserved. Wildcards and regular expressions are not supported via the env var; if you need a subdomain wildcard, add a RegExp entry directly in src/server/cors.ts.

> Note: Origin matching is case-sensitive and does not include a path or query string. Native MCP clients (Cursor, Claude Desktop, Claude Code) send no Origin header and are not affected by this allowlist.

Privacy Policy

The Sequentum MCP Server accesses your Sequentum account data — including agent metadata, run history, scheduled tasks, billing information, and output files — solely to fulfill the requests you make through your AI assistant. By default, the MCP server acts as an authenticated proxy between your MCP client and the Sequentum API: request data is forwarded to the API and responses are returned to your client without being persisted or shared with third parties.

Operators may enable verbose request logging via the DEBUG=1 environment variable for troubleshooting. In that mode the server redacts Authorization, Cookie, and x-api-key headers, but writes request bodies (which may include tool arguments) to stderr. The hosted server at mcp.sequentum.com does not run with DEBUG=1.

For the full Sequentum privacy policy, see https://www.sequentum.com/privacy-policy.

Links

- Sequentum MCP Server
- Sequentum Dashboard
- Sequentum API Documentation
- Model Context Protocol

License

MIT © Sequentum