thismcp.codes

Elixir · BEAM · Model Context Protocol

this MCP codes.

A hub plaque, not a product pitch. Sockets for tools. Beams for processes. MCP on the BEAM — the workshop where this MCP codes.

Read the plaqueThe beam →
An indigo hexagonal MCP socket on a dark workshop plate, copper circuit traces fanning out, an amber beam striking the live core.
hex socket · amber beam · BEAM live

Three bays

Socket. Beam. Mix.

Elixir-flavored MCP: processes, not plugins. The protocol is the hex. The runtime is the beam that keeps it seated.

OTP

The socket

Model Context Protocol as a supervised port. Tools land as processes, not npm packages.

BEAM

The beam

Amber light, Erlang VM. One runtime fans context into isolated processes that refuse to die quietly.

MIX

The workshop

Compile the hub. Wire the traces. Hex is the shape of the fitting — and the package board.

Close view of the indigo hex MCP fitting with copper traces and a focused amber beam hitting the socket core.
The beam is the VM. The socket is the protocol.

Hub plaque

Not a waitlist.
A mark on the wall.

thismcp.codes is the punchline hostname for MCP work on Elixir — GenServers for tools, supervisors for agents, Mix for the bench.

It hangs in The Robot Lives / Noizu orbit. If the amber line is lit, this MCP codes.

How it seats

Three messages. One beam.

  1. 01

    Seat the hex

    MCP is the socket. Elixir holds it open. Agents find one shape instead of a cable drawer.

  2. 02

    Strike the beam

    A tool call is a message. Supervision restarts the bay. The amber line stays lit.

  3. 03

    Leave the plaque

    No waitlist. No SaaS funnel. A hub mark for MCP work in the Robot Lives / Noizu orbit.

Square mark of an indigo hexagonal MCP socket with an amber beam through its core and copper traces on a dark plate.

this MCP codes.

A static plaque for the Elixir MCP hub. No signup. No backend. The beam, the socket, and the hostname that says it out loud.

The Robot Lives