Rivvers AI & Developer Portal

Welcome to the Rivvers AI & Developer Portal repository. This project provides first-party design tokens, static vector assets, machine-readable LLM manifests (llms.txt), and Model Context Protocol (MCP) servers to enable seamless AI-supported workflows for the Rivvers coworking network.

The public developer portal is deployed and accessible at: 👉 ai.rivvers.de

---

📂 Repository Structure

• brand/: Contains corporate design guidelines, Tailwind configuration templates, custom CSS variables, and official SVG vector assets (logos, symbols, waves).
• mcp-server/: A stateless Node.js / TypeScript Model Context Protocol (MCP) server exposing tools to query physical locations and search coworking spaces.
• web/: Source files for the static website served at ai.rivvers.de via GitHub Pages.
• llms.txt: A machine-readable entry point manifest for LLMs, scrapers, and autonomous agents.

---

⚡ Getting Started (Quick Setup)

1. Build the MCP Server

To run the stateless MCP server locally:

cd mcp-server
npm install
npm run build

2. Configure Your MCP Client

After running the build step, the console will automatically print a copy-pasteable configuration block with the absolute path of the built file. Add this block to your MCP client (such as Claude Desktop):

{
  "mcpServers": {
    "rivvers-hub": {
      "command": "node",
      "args": [
        "/Users/sebastianfuss/projects/ai ci/mcp-server/build/index.js"
      ]
    }
  }
}

---

🤝 Collaboration & Contribution

For United Workspace Developers

Important

Source of Truth: The primary development repository for this project is hosted on our internal GitLab instance.

• Always commit and push changes directly to the GitLab origin.
• The repository is automatically mirrored to GitHub for public access and hosting the developer portal via GitHub Pages.

For External Contributors

We welcome open-source contributions! Since this repository is mirrored:

1. Please open a Pull Request (PR) or Issue here on GitHub.
2. The United Workspace maintainers will review your changes and integrate/merge them back into our internal GitLab repository, which will then mirror back to GitHub.