• Blog
  • Docs
  • Pricing
  • We’re hiring!
Log inSign up
valdottown

valdottown

blog

Val Town's Blog
Public
Like
9
blog
Home
Code
9
components
13
posts
16
routes
6
styles
2
utils
9
IMAGES.md
README.md
TODOs.md
H
index.ts
Branches
4
Pull requests
2
Remixes
18
History
Environment variables
Val Town is a collaborative website to build and scale JavaScript apps.
Deploy APIs, crons, & store data – all from the browser, and deployed in milliseconds.
Sign up now
Code
/
/
x
/
valdottown
/
blog
/
branch
/
mcp
/
version
/
61
/
code
/
posts
/
2025-11-14-mcp.md
/
posts
/
2025-11-14-mcp.md
Code
/
/
x
/
valdottown
/
blog
/
branch
/
mcp
/
version
/
61
/
code
/
posts
/
2025-11-14-mcp.md
/
posts
/
2025-11-14-mcp.md
Search
11/14/2025
Viewing readonly version of mcp branch: v61
View latest version
2025-11-14-mcp.md
title:
Introducing Val Town MCP
description:
Bring Val Town to your favorite LLM
pubDate:
2025-11-14:00:00.000Z
author:
Steve Krouse

On Val Town, you can deploy TypeScript apps in 100ms. Now with the Val Town MCP server, you can do that from Claude, ChatGPT, Cursor, VSCode, or wherever you do your AI coding. Try it!

Val Town MCP

If you've been following my tweets recently – "I've gotta rant about LLMs, MCP, and tool-calling for a second", "MCP is mostly nonsense", "MCP is overhyped" – you might be surprised by this announcement. Well, how did you think I got those salty takes except by building an MCP server?

Yes, I think MCP is dubious as a protocol. But for now, MCP is the right way for Val Town to meet developers where they are. In Cursor or Claude Code or Zed or wherever.

We have guides for some of the popular LLMs—Claude Code, ChatGPT, Claude Web/Desktop—but it should work with any MCP client. If you'd like a hand with setup, ask in our discord server or send us an email.

Why MCP

MCP is not perfect (again, see tweets), and the whiplash from AI tooling is real, but MCP has a few things going for it:

  1. Meet developers where they are
  2. Write once, integrate everywhere
  3. Ship faster

Instead of fast-following all the best AI coding assistants with Townie, Val Town MCP can be used with the latest and greatest LLM of your choosing.

MCP also allows us to ship faster: whereas traditional APIs require careful version control for backward compatibility to prevent breaking changes, an MCP spec can change continuously because LLMs read the spec and run inference at runtime.

How we got here

There's a common thread running through every AI feature we've implemented (e.g., Townie, the vt CLI, and now MCP). On Val Town, whatever you and your LLM are coding is live immediately. It's the idea from Bret Victor's Inventing on Principle talk:

Creators need an immediate connection to what they're creating...when you're making something, if you make a change, or you make a decision, you need to see the effect of that immediately.

When you (or your LLM) make an edit, your code is deployed on Val Town immediately. And that goes for all code on Val Town: all code is deployed by default, either on prod or in a branch—not locally on your machine.

Val Town isn't an AI company, but this always-deployed model works quite well with LLMs. Just give your favorite LLM a branch, and the code it writes will be alive by default.

Bring Val Town MCP to your favorite LLM, and let us know what you think.

FeaturesVersion controlCode intelligenceCLIMCP
Use cases
TeamsAI agentsSlackGTM
DocsShowcaseTemplatesNewestTrendingAPI examplesNPM packages
PricingNewsletterBlogAboutCareers
We’re hiring!
Brandhi@val.townStatus
X (Twitter)
Discord community
GitHub discussions
YouTube channel
Bluesky
Open Source Pledge
Terms of usePrivacy policyAbuse contact
© 2025 Val Town, Inc.