# HTTP 413 payload-too-large

> HTTP 413 payload-too-large is an MCP server for developer tools. Remote MCP server that explains the meaning of HTTP status code 413. It runs as a hosted remote server, so there is nothing to install locally.

- **Kind:** MCP server
- **Platforms:** API
- **Repository:** https://github.com/sadri-dridi/named-mcp-utilities
- **MCP Registry name:** io.github.sadri-dridi/http-413
- **Categories:** [developer tools](https://ai-powered.com/categories/developer-tools)
- **Listing updated:** 2026-11-18

## About

This server is one of a set of small single-purpose MCP endpoints published in the named-mcp-utilities repository. Its registry entry describes it only as giving the meaning of HTTP 413, the status code for a payload that is too large.

It runs as a remote streamable-http endpoint hosted on a Cloudflare Workers subdomain, so there is nothing to install locally; an MCP client connects to the URL given in the registry. The README presents the repository's servers as publicly listed utilities for autonomous clients, each with its own intake, but gives no tool list or usage details for this one.

It suits agents or developers who want a lightweight lookup for a single status code. Because the available documentation is minimal, the exact output and any tool names are not documented.

## Features

- **HTTP 413 lookup:** Provides the meaning of HTTP status 413 (payload too large) to connected MCP clients.
- **Remote streamable-http:** Served from a hosted endpoint over streamable HTTP, with no package to install.
- **Single-purpose design:** Focused on one narrow question, in line with the other small servers in the same repository.
- **Official registry name:** Published under the io.github.sadri-dridi/http-413 registry name.

## Good for

- Letting an agent look up what a 413 response means while debugging an upload failure
- Adding a minimal status-code reference to an MCP client's toolset
- Testing connectivity to a remote streamable-http MCP server

## Install

### Claude Code (Terminal)

```sh
claude mcp add --transport http http-413 https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-413/mcp
```

### Claude Desktop (Settings → Connectors → Add custom connector)

```sh
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-413/mcp
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "http-413": {
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-413/mcp"
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "http-413": {
      "type": "http",
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-413/mcp"
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "http-413": {
      "serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-413/mcp"
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

```json
{
  "mcpServers": {
    "http-413": {
      "type": "http",
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-413/mcp"
    }
  }
}
```

## FAQ

### What does this MCP server do?

Its registry description says it gives the meaning of HTTP 413.

### How do I connect to it?

Point an MCP client at the streamable-http remote URL listed in the registry entry; no local package is published.

### Is there anything to install?

No. The registry lists no packages, only a hosted remote endpoint.

### Where is the source repository?

It is listed in the sadri-dridi/named-mcp-utilities repository on GitHub, alongside many similar servers.

### How do I add HTTP 413 payload-too-large to Claude Code?

Run this command in your terminal: claude mcp add --transport http http-413 https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-413/mcp

### What are the best alternatives to HTTP 413 payload-too-large?

The closest alternatives to HTTP 413 payload-too-large are HTTP 431 header-fields-too-large, HTTP 414 uri-too-long, HTTP 415 unsupported-media, HTTP 429 too-many-requests and HTTP 412 precondition-failed.

## Where this comes from

- Description: written from the project's README and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.

## Alternatives

- [HTTP 431 header-fields-too-large](https://ai-powered.com/mcp/http-431-header-fields-too-large): HTTP 431 header-fields-too-large is an MCP server for developer tools.
- [HTTP 414 uri-too-long](https://ai-powered.com/mcp/http-414-uri-too-long): HTTP 414 uri-too-long is an MCP server for developer tools.
- [HTTP 415 unsupported-media](https://ai-powered.com/mcp/http-415-unsupported-media): HTTP 415 unsupported-media is an MCP server for developer tools.
- [HTTP 429 too-many-requests](https://ai-powered.com/mcp/http-429-too-many-requests): HTTP 429 too-many-requests is an MCP server for developer tools.
- [HTTP 412 precondition-failed](https://ai-powered.com/mcp/http-412-precondition-failed): HTTP 412 precondition-failed is an MCP server for developer tools.
- [HTTP 422 unprocessable](https://ai-powered.com/mcp/http-422-unprocessable): HTTP 422 unprocessable is an MCP server for developer tools.
- [HTTP 426 upgrade-required](https://ai-powered.com/mcp/http-426-upgrade-required): HTTP 426 upgrade-required is an MCP server for developer tools.
- [HTTP 425 too-early](https://ai-powered.com/mcp/http-425-too-early): HTTP 425 too-early is an MCP server for developer tools.

---
Source: https://ai-powered.com/mcp/http-413-payload-too-large
