The MCP connection that gives your agent hands

One URL. Your agent can create servers, deploy, and roll back.

copied
agent · session Illustrative

claude mcp add --transport http sdlc https://mcp.sdlc.works

agentConnected to sdlc.works. I can now build, deploy, roll back, and spin up full copies of your app — servers, database, secrets included. What should I do first?

ship it

building · releasing

deployed ✓

Setup is one command. Here is what happens.

Scroll

Paste the URL. The platform introduces itself.

The first message explains everything it can do here.

Your terminal Your agent What it now knows live
claude mcp add --transport http sdlc https://mcp.sdlc.works
Agent Illustrative

Connected to sdlc.works. I can now build, deploy, roll back, and spin up full copies of your app — servers, database, secrets included. What should I do first?

59 actions. Nobody read a doc.

One hub runs everything. And remembers it.

One sentence in. The hub carries it out, end to end.

Everything is written down: what you asked, what happened, what it used.

Ask anything, and the answer is true. All 59 actions.

You one sentence Your agent over MCP One hub runs & remembers What it remembers What you asked for What actually happened What it used - keys, access Release history Your app the real one, running Servers Database Secrets A full copy a second everything Servers Database Secrets Your users You one sentence Your agent over MCP One hub runs & remembers What it remembers What you asked for What actually happened What it used - keys, access Release history Your app the real one, running Servers Database Secrets Your users A full copy a second everything Servers Database Secrets

Your agent never gets stuck. Here is why.

One fixed menu. Nothing to hallucinate.

Errors say why, in words. It adjusts.

Even the 401 explains how to sign in.

  • list projects
  • read a workflow
  • start a build
  • list build artifacts
  • make a copy of prod
  • release
  • roll back
  • …59 total
  • branch_already_exists
  • invalid_branch_name
  • branch_frozen_for_cleanup
  • branch_restore_window_expired
  • …39 named

HTTP/2 401 WWW-Authenticate: Bearer resource_metadata="https://mcp.sdlc.works/.well-known/oauth-protected-resource", scope="mcp"

An agent deployed this platform.

One request was wrong. It read the error and continued.

Session · deploy of sdlc.works
list projects 4 found
read workflow (qa) provision · build · release · roll back
start build @ commit 66d67bb | runningsucceeded
get the build artifact sdlcserv:default_qa_66d67bb
release @ commit pin refused: wrong workflow for a pinned commit
release (fixed) deployed

Real session, shortened. Mistake included.

You stay in control.

Destructive actions are labeled.

delete a branch · labeled: destructive

Payments go to you, never it.

checkout link → sent to you

It only has your access.

your access · nothing more

Give your agent hands.

Add it. Let it introduce itself.

your terminal

claude mcp add --transport http sdlc https://mcp.sdlc.works

copied to clipboard