tumiki

Tumiki is an MCP-based platform that orchestrates AI agents with business tools through a centralized MCP Proxy server. It exposes a gateway where AI agents (or external clients) can connect via MCP to access tool integrations, logging, and authorization managed by the system. The included MCP proxy handles routing, authentication, and activity logging, allowing you to connect agents like Claude, GPT models, or custom agents to tools such as Notion, Slack, Google Calendar, and other business apps via a unified interface. In practice, you would deploy the proxy alongside your frontend dashboard and database stack, then configure the MCP connections for each tool and agent. The result is a cohesive environment where agents can perform actions, read data, and execute workflows across multiple SaaS apps with centralized permission and audit trails.

Prerequisites:

• Node.js >= 22.14.0
• pnpm >= 10.11.0
• Docker (optional for local dev environment with containers)

Step-by-step installation:

1. Clone the repository git clone https://github.com/rayven122/tumiki.git cd tumiki

2. Install dependencies (pnpm is recommended) pnpm install

3. (Optional) Start Docker containers for local development (PostgreSQL, Redis, Keycloak) pnpm docker:up

4. Set up development environment (first time only) pnpm setup:dev

5. Start development servers pnpm dev

Notes:

• The project is a monorepo managed with Turborepo and pnpm workspaces. Individual components live under apps/ and packages/.
• For a containerized setup, you can customize and run docker-compose configurations found under docker/.

Tips and common considerations:

• If you’re wiring MCP connections, ensure MCP_HOST and MCP_PORT are set to reachable addresses for your agents.
• The MCP proxy relies on authentication/authorization utilities; configure Keycloak or other providers as described in docs/environment-variables.md.
• Use pnpm docker:up and docker:down to manage local infrastructure (PostgreSQL, Redis, Keycloak) for development and testing.
• For production deployment, consider scaling the MCP proxy behind a reverse proxy and ensuring secure certificates and proper secret management for credentials.