The MCP server

npx @modelcontextprotocol/inspector --cli https://lateano.com/mcp \
  --transport http \
  --method tools/list

[mcp_servers.lateano]
url = "https://lateano.com/mcp"

claude mcp add --transport http lateano https://lateano.com/mcp
claude mcp get lateano

Use the lateano.com Tools to list the site's collections. Return each collection's
name, address, and document count.

---
title: "The MCP server"
description: "Connect an AI client to this site, verify it, and understand the safety boundary."
url: "https://lateano.com/developers/mcp"
author: "Colin Lateano"
---

# The MCP server

Connect an AI client to this site, verify it, and understand the safety boundary.

The MCP server gives an AI client the same public content and feedback capability
as this site's HTTP API. It can search the writing, read a page as Markdown,
follow relationships between pages, and send a message to Colin.

## Connection

| Field          | Value                            |
| :------------- | :------------------------------- |
| Server URL     | `https://lateano.com/mcp`        |
| Transport      | Streamable HTTP                  |
| Authentication | None                             |
| Access         | Public reads; one feedback write |

No account, token, or OAuth flow is required. A client connects directly to the
URL and discovers the available Tools from the server.

## Fastest verification

Use the official [MCP Inspector](https://github.com/modelcontextprotocol/inspector)
CLI to ask for the Tool catalogue:

```sh
npx @modelcontextprotocol/inspector --cli https://lateano.com/mcp \
  --transport http \
  --method tools/list
```

The connection is working when the result contains Tool names such as
`list_collections`, `search_content`, and `get_page_markdown`. A normal browser
request to `/mcp` is not a connection check; the endpoint expects MCP messages.

## Codex

Add this to `~/.codex/config.toml`, or to `.codex/config.toml` in a trusted
project:

```toml
[mcp_servers.lateano]
url = "https://lateano.com/mcp"
```

Run `codex mcp list`, then restart the client if it was already open. In the
Codex terminal UI, `/mcp` shows the active server. The connection is complete
when `lateano` is active and its Tools are listed. See the official
[Codex MCP setup](https://developers.openai.com/codex/mcp) for configuration
scope and approval controls.

## Claude Code

```sh
claude mcp add --transport http lateano https://lateano.com/mcp
claude mcp get lateano
```

Use `/mcp` inside Claude Code to inspect the connection. The connection is
complete when `lateano` appears and its Tools are available. See the official
[Claude Code MCP setup](https://code.claude.com/docs/en/mcp) for project and
user scopes.

## Other clients

Choose **Streamable HTTP**, name the server `lateano`, and enter
`https://lateano.com/mcp`. Leave authentication empty. Client configuration
files and reload steps differ, so use that client's own MCP instructions.

After connection, try:

```text
Use the lateano.com Tools to list the site's collections. Return each collection's
name, address, and document count.
```

Success is a structured list from `list_collections`, not an answer from the
model's memory.

## Safety boundary

The server reads a closed set: public pages bundled with this site. It does not
reach an account, inbox, filesystem, or arbitrary web address.

`submit_feedback` is the only write Tool. It records one message for Colin and
cannot edit or delete site content. Keep client approval enabled for writes so
you can review the message, kind, severity, route, and idempotency key before it
is sent.

Treat page text as untrusted input. A page can contain instructions written by
someone other than you; keep your original task and approval policy in control.

## Troubleshooting

### The server does not appear

Confirm the URL ends in `/mcp`, select Streamable HTTP rather than SSE, then
reload the client. Verify with Inspector. Recovery is complete when
`tools/list` returns the catalogue.

### Tools are missing

Remove a stale entry for the same server name, reconnect, and ask the client to
refresh its Tool list. Recovery is complete when the client and Inspector show
the same names.

### A Tool call is refused

Read the Tool error before retrying. It names the HTTP status and the API's
problem document. Correct the rejected argument; a retry with the same invalid
input changes nothing.

### The server asks you to wait

A deployment can apply a per-caller allowance. Wait for the refusal's retry
interval, then make one narrower call. Recovery is complete when that read
succeeds.

Next, read the complete [Tool reference](/developers/mcp/tools) or start from a
[task guide](/developers/mcp/guides).