BranderUX MCP vs Val Town

A side-by-side look at the BranderUX MCP and Val Town MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

BranderUX MCP logoBranderUX MCPDeveloper Tools · Remote HTTP/SSECreate and control BranderUX projects, elements, screens and keys from your agent via browser OAuth.40FairAuth: not declaredVal Town logoVal TownDeveloper Tools · Local subprocess (stdio)Deploy serverless TypeScript on Val Town: HTTP vals, cron, SQLite, email, OAuth.47FairAuth: not declared

Verdict: choose BranderUX MCP for developer tools work over a hosted endpoint; choose Val Town for developer tools as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

BranderUX MCP logoChoose BranderUX MCP when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a remote HTTP/SSE transport.
  • You have the keys it needs: BRANDER_API_BASE, BRANDER_APP_BASE, MCP_RESOURCE_URL, OAUTH_ISSUER_URL.
Explore BranderUX MCP

Val Town logoChoose Val Town when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
Explore Val Town

Feature & specification comparison

Rows where the two servers differ are marked.

SpecBranderUX MCP logoBranderUX MCPVal Town logoVal Town
CategoryDeveloper ToolsDeveloper Tools
Quality signal40/100 · Fair47/100 · Fair
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsBRANDER_API_BASEBRANDER_APP_BASEMCP_RESOURCE_URLOAUTH_ISSUER_URLNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars010
Directory activity 0 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

BranderUX MCP tools

No tool names declared yet. Check the project README from the listing page.

Val Town tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

BranderUX MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-66": {
      "url": "https://mcp.branderux.com/mcp"
    }
  }
}

Val Town

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "val-town": {
      "command": "npx",
      "args": [
        "-y",
        "@changesets/cli"
      ]
    }
  }
}

Frequently asked questions

BranderUX MCP is categorized under Developer Tools and uses a remote HTTP/SSE transport. Val Town belongs to Developer Tools and uses a local stdio subprocess. Pick BranderUX MCP for developer tools work and Val Town for developer tools.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

BranderUX MCP has no declared pricing — check the project's own site. Val Town has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add mcp-66 and val-town as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, BranderUX MCP has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Val Town has 47/100 (Fair) with 1 views, 0 installs and 10 GitHub stars.