Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
제작자가 쓴 설명(영어 원문)
Turn the web into structured, reliable, actionable enterprise data for AI Agents
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
웹, 데스크톱, 모바일의 Claude에서 쓸 수 있어요:
https://mcp.sequentum.com/mcp터미널에서 이 명령어를 실행하세요
claude mcp add --transport http sequentum https://mcp.sequentum.com/mcp프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"sequentum": {
"url": "https://mcp.sequentum.com/mcp"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"sequentum": {
"type": "http",
"url": "https://mcp.sequentum.com/mcp"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요:
https://mcp.sequentum.com/mcp메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
아직 이 서버의 도구 목록을 읽지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검
레지스트리 이름이 도메인 sequentum.com 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트를 점검할 때 도구 목록을 읽어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(3.0.1)은 11일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, Apify MCP Server
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
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.
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.
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:
Once authenticated, all tools become available in your client. For client-specific setup details, see Set Up Your Client below.
Select your client below for specific setup instructions. All clients use the remote OAuth server at https://mcp.sequentum.com/mcp unless noted otherwise.
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.
Sequentum MCP is listed in Claude's connector directory, so there is no URL to enter by hand and no custom connector to create.
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.
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.
Sequentum and URL: https://mcp.sequentum.com/mcpOnce connected, enable Sequentum in a conversation via the + button near the message composer, then select your connector from the list.
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.
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
Configure via the Configure MCP option in Cascade (Cmd+L or Ctrl+L). Add the Sequentum MCP server URL:
https://mcp.sequentum.com/mcp
The Sequentum MCP Server follows standard MCP protocols and works with any client that supports:
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.
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.
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?
The Sequentum MCP Server provides 43 tools across 9 categories for interacting with the Sequentum platform. See the Tool Reference for detailed documentation.
list_agentsget_agentsearch_agentsget_agent_search_countget_personal_agent_countget_agent_runsget_agent_run_summaryget_run_statusstart_agentstop_agentkill_agentdelete_runget_run_filesget_file_download_urlget_agent_versionsrestore_agent_versionlist_agent_schedulesget_agent_schedulecreate_agent_scheduleupdate_agent_scheduleenable_agent_scheduledisable_agent_scheduledelete_agent_scheduleget_scheduled_runsget_credits_balanceget_spending_summaryget_credit_historyget_agents_usageget_agent_cost_breakdownget_agent_runs_costlist_spacesget_spaceget_space_agentsget_space_agent_countsearch_space_by_namerun_space_agentsget_runs_summaryget_records_summaryget_run_diagnosticsget_latest_failurestart_agent_buildget_agent_build_statusstop_agent_build36 of the 43 tools declare an outputSchema and return structuredContent next to the usual text block (MCP 2026-07-28). The text block is unchanged, so clients that ignore structured content see no difference. The seven acknowledgement-only tools (stop_agent, kill_agent, delete_run, restore_agent_version, delete_agent_schedule, enable_agent_schedule, disable_agent_schedule) return text only.
start_agent returns { "run": … } in async mode and { "data": … } in sync mode.list_spaces, get_space_agents, list_agent_schedules, get_scheduled_runs, get_agent_versions, get_run_files) have an array schema. Clients on a 2025 protocol revision receive it wrapped as { "result": [...] }, as the SDK projects it.The server includes 9 reusable prompt templates that guide the AI through common multi-step workflows. See the Prompts Reference for detailed documentation.
debug-agent -- Diag앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요