Read-only MCP servers

An agent with write access to a CDN, DNS or firewall API can do damage faster than anyone can review it. These servers only read. They have no tool that creates, updates, deletes, activates or purges anything, so an agent can’t make those writes through them. Why I only build them this way.

Akamai

16 tools across CDN properties, DNS, EdgeWorkers and network lists:

Area	What the agent can do
Properties	Fuzzy search by name from an in-memory index, read rule trees, versions, hostnames and activation history
DNS	List zones, search records by name or type
EdgeWorkers	List workers and versions, read a version’s code bundle, regex search across its files
Network lists	Search IP, geo and block lists, read their contents
Utility	List groups and CP codes, translate reference error codes

Run it with uvx readonly-mcp-akamai (Python 3.11 or newer), or use the container from GHCR. Configuration is the usual EdgeGrid credentials as environment variables, and the API client itself can be read-only too. Source: desty2k/readonly-mcp-akamai.

TeamCity

Released 2026-11-02 as 1.0.0 (release post). 29 tools across projects, build configurations, builds, logs, tests and build infrastructure:

Area	What the agent can do
Projects	Search projects and browse the hierarchy
Build configurations	Find a configuration from a vague name across names and project paths, read steps, triggers, parameters and branches
Builds	Search build history, read a build, its statistics and its snapshot-dependency chain
Logs	Read a log by page or from the tail, search it with surrounding context
Tests and problems	Ask why a build failed and get problems, failed tests and error lines in one call; read investigations and muted tests
Infrastructure	Read the queue with wait reasons, agents and pools, artifacts, VCS changes and server health
URLs	Paste a TeamCity web URL and get the project, configuration, build or change it points to

Run it with uvx readonly-mcp-teamcity, or use the container from GHCR. Create the token with TeamCity’s Read-only preset; I checked that preset against TeamCity 2026.2.1, where it could read everything the tools need and could not pin a build. Source: desty2k/readonly-mcp-teamcity.