RTP Relational Tech MCP Server v0.6.0

Connect any MCP-compatible AI tool to the Relational Tech Project commons — the Studio's remixable builder tools, stories, and prompts, plus methodology, neighborhood recipes, frameworks, and field references. Search is semantic: describe a need in plain language.

350+ commons items
25 builder tools
45 builder stories
63 recipes
197 field references
15 frameworks & methodology

Connect

Add this to your AI tool's MCP configuration:

{
  "mcpServers": {
    "relational-tech": {
      "type": "streamable-http",
      "url": "https://mcp.relationaltechproject.org/mcp"
    }
  }
}

Endpoint:
https://mcp.relationaltechproject.org/mcp

Where this goes

No API key. No signup. Reads are public via row-level security; contributions land in a stewarded review queue — nothing publishes without a human.

Start here: two prompts

Once connected, invoke the practice-guide prompt to put your AI in a Neighboring Commons practice-guide stance for the rest of the conversation: relationships-first, asset-based, citing practitioners by name, calibrating confidence honestly.

Building a tool? Invoke relational-builder-stance instead. It loads the principles and working practices Relational Builder builds by, so Claude Code, Cursor, Lovable, or a chat window builds from the same ground: the first build as the core loop alive, one seeded neighbor, every post opening a path to a person, a look that comes from the place.

At a community build day with your own tools

Invoke the build-day prompt with the event code from the room's slide. Your AI sets the Builder stance, looks at what the room has already shared, pulls the city's live open data when the day has some, sizes the build for an afternoon, and when something works pins it to the room's demo wall with share-to-build-day-wall, next to the builds made in the Builder itself. Prefer email? Send the project to the build day inbox on the slide with the event code in the subject line, a link, and a screenshot.

What you can ask

Your AI will surface relevant recipes, frameworks, methodology, and practitioner references — with attribution and source URLs so you can read the original work.

What's in the toolbox

13 tools: search-studio-library, get-tool-details, find-patterns-by-context, suggest-contribution, submit-contribution, get-network-updates, get-builder-guidance, find-civic-data-endpoints, find-place-commons, search-prompt-seeds, get-prompt-seed, get-build-day-wall, share-to-build-day-wall

8 prompts: practice-guide, relational-builder-stance, build-day, design-neighborhood-tool, assess-relational-soil, create-builder-action-plan, remix-existing-tool, create-build-plan

12 resources: 9 methodology docs at rtp://knowledge/* (queried live from the commons) and 3 at rtp://builder/* — Relational Builder's principles, practices, and domain frames, generated from its source on every deploy

Source & details

Open source on GitHub. See the README for the full architecture, deployment guide, and how the commons works.

Health check: /health