For everyone deciding what to try next while waiting on a free GPU.

The execution environment
for AI agents.

AI agents like Claude and GPT access serious compute — including GPUs — over MCP. From running code to training jobs, with zero infrastructure to manage.

Copies Seyval's MCP server URL and opens the connector settings

mcp.seyval.dev
LIVE
1 start_run · MCP tool
2 repository my-org/experiments
3 commit 9f3ab21
4 compute gpu-h100
5
6→ Building image... → Streaming logs... live
7✓ Run completed in 38m 12s
8 Artifacts: runs/9f3a.../outputs/
9 Cost: $4.38 (node released after run)

Participating organizations

Agentic AI Foundation
Agentic AI Foundation

透明性・協力・標準化を基盤に、エージェンティックAIイノベーションの公共利益を推進するグローバルな中立オープン基盤組織。

How it works

From zero to GPUs for your agent, in minutes

Three steps to connect an execution environment to your AI agent. No DevOps, no Kubernetes manifests.

01
Connect

Link your repository

Just register the GitHub repo you want to run. Seyval analyzes the code at a given commit and surfaces the entry points and arguments you can run.

register_repository
github.com/you/experiments
start_analysis
✓ 3 entry points found
02
Run

Your agent launches jobs

Agents like Claude and ChatGPT start runs over MCP. Just pick the compute you need, from T4 to H100.

run-a1f2 · gpu-h100RUNNING
run-b3c4 · gpu-l40sRUNNING
run-d5e6 · gpu-t4IDLE
03
Collect

Results come back automatically

Logs stream in real time and artifacts land in S3. The agent reads the results and moves to the next experiment.

traffic chart
loss 2.41loss 0.38 · GPU 94%

Why Seyval

Serious compute for AI agents

GPU provisioning, job execution, logs, and artifacts — one platform your agents can drive autonomously.

Your agents

Claude Code
ChatGPT
Codex

Seyval Platform

MCP Gateway
GPU Runtime
Logs & Artifacts

Cloud infra

EKS
Karpenter
Slurm (BYO)

T4 to H100, on demand

The right GPU is provisioned exactly when needed and scales to zero when done. No idle costs.

MCP-native by design

Built on the Model Context Protocol from day one. Claude or ChatGPT launches a job with a single tool call.

A disposable environment per run

Every run gets its own purpose-built image, and GPU jobs run one job per node. When the run ends the node is torn down, leaving nothing behind.

Durable execution

Long-running training and experiment jobs survive restarts, crashes, and deployments — Temporal under the hood.

Logs & artifacts, collected

Execution logs stream in real time, artifacts are saved to S3 automatically, and every run's cost is recorded.

Bring your own compute

Connect your Slurm/HPC cluster or lab machines and use them from agents through the same interface.

How this differs

Hand the GPU chores to your agent.

Rolling your own GPUs

Before

Launch the instance, line up drivers and CUDA, install dependencies, and remember to shut it down. Every experiment repeats the same chore.

With Seyval

Pick a compute type. Image builds, node provisioning, and teardown are automatic, and the cost is recorded per run.

ML platforms built for people

Before

Designed around a human submitting jobs from a console or SDK. Driving one from an agent means writing your own API glue anyway.

With Seyval

MCP-native from day one. Agents launch jobs with a tool call, then read logs and artifacts to decide the next move.

Driving HPC by hand

Before

Write the sbatch script, convert the container to SIF, watch for free nodes, and relearn the conventions on every cluster.

With Seyval

Connect once over SSH and it behaves like the managed GPUs. Your code and data stay inside the cluster.

Enterprise ready

Built for scale, security, and control

Keep compute inside your own cluster

Connect your lab or corporate Slurm/HPC cluster over SSH and your code and data never leave your environment. Seyval only submits the job and collects the results.

+12
OWNER / ADMIN / MEMBER

Workspaces & access control

Three roles — owner, admin, member — govern access. SAML and OIDC federation with your corporate IdP is supported, configured per tenant at onboarding.

[commit]9f3ab21
[compute]gpu-h100 · 38m 12s
[cost]$4.38

Every run on record

Which commit, on which machine, at what cost. Logs, artifacts, and spend are recorded per run.

ap-northeast-1KMS CMKTLS in transitCloudTrail

Where your data lives

Everything stays in the Tokyo region (ap-northeast-1). Each region is isolated with its own infrastructure and KMS keys, and data is encrypted at rest and in transit.

GitHub AppMCPClaude CodeChatGPTCodexVS CodeSlurmApptainerAmazon S3

Fits your existing workflow

Connect private repositories through the GitHub App and analyze automatically on push or PR. Works from any MCP-compatible AI client.

Frequently asked

Real compute,
for AI agents.