Kituwa · MCP registry · updated 23 servers
Every MCP we run,
Every MCP we run,
in one place.
A server we build or install gets a card, a documentation page and a place in this registry. The list below is generated from the registry itself, so a new server appears here the moment its entry lands.
23MCP servers
5Connected now
286Tools in registry
11Categories
Catalog
In-house first, then vendors by category
In-house
1 Servers we build and run ourselves. These carry our own safety rules and are the ones the console can inspect.Browser
3 Drive a real browser for checks, screenshots and end-to-end tests.Code
3 Work with repositories, diffs, review and static analysis.Data
3 Talk to a database or cache. Connection strings stay in the client environment, never in this registry.Design
2 Produce or inspect diagrams and design files.Desktop
1 Touch the machine itself: pointer, windows, input. Local stdio only, never exposed.Infrastructure
6 Cloud, containers, clusters and the homelab.Trinity Homelab
Infrastructure · remoteRead-only eyes on this host and its containers.
http
Open
AWS MCP
Infrastructure · opencodeAWS API discovery over a signed proxy.
stdio
Open
Cloudflare
Infrastructure · remoteEdge DNS, WAF and Workers through OAuth.
http
Open
Docker
Infrastructure · opencodeContainers, images, volumes, networks.
stdio
Open
Kubernetes
Infrastructure · opencodeCluster objects without kubectl verbs.
stdio
Open
Terraform
Infrastructure · opencodePlan, apply and inspect declared infrastructure.
stdio
Open
Media
1 Transcode, inspect and cut audio and video.Reasoning
1 Structure a problem before acting on it.Utility
1 Small deterministic helpers such as time and identifiers.Web
1 Fetch and read pages on the public web.Nothing matchesTry a shorter word, or clear the search field.
A server is missing?
Add a server
A new MCP is not done until it has a registry entry and a documentation page. The rule and the fields are in the docs.