Drifts
Connect your agent to Drifts.bot for multi-sensory journeys with time-locked progression, structured sensory data, reviews, and hosting when you have a DRIFTS_API_KEY.
Overview
Drifts is an MCP server for the Build phase that connects agents to drifts.bot multi-sensory experiences with time-locked progression and optional hosted journeys.
What is this MCP server?
- Multi-sensory AI experiences with structured sensory payloads
- Time-locked progression gating content unlocks over real time
- Browse and search without an API key; journeys, reviews, and hosting require DRIFTS_API_KEY
- npm mcp-drifts stdio server version 1.0.2
- Configurable DRIFTS_API_URL defaulting to https://drifts.bot/api for local overrides
- Default API base https://drifts.bot/api via DRIFTS_API_URL
- Key-gated features: journeys, reviews, hosting; browse and search without key per env docs
What problem does it solve?
You want rich, time-gated sensory experiences for agents but do not want to implement drifts.bot auth, progression, and hosting APIs yourself.
Who is it for?
Solo builders making agent-led interactive content who need structured sensory data and progression without custom backend work.
Skip if: Teams needing vanilla CRUD backends, AWS security scans, or analytics-only MCP tools.
What do I get? / Deliverables
After install, your agent can browse Drifts catalog keylessly and, with DRIFTS_API_KEY, manage journeys, reviews, and hosted experiences from one MCP surface.
- Agent access to Drifts browse and search surfaces
- Journey, review, and hosting operations when API key is set
- Configurable API base for production or local drifts.bot endpoints
Recommended MCP Servers
Journey fit
Build covers integrating third-party experience APIs into agents before you distribute finished journeys to users. Agent-tooling fits MCP bridges to drifts.bot where browse and search may work keyless but journeys and hosting need credentials.
How it compares
Experience-hosting MCP for drifts.bot, not a code review skill or cloud scanner.
Common Questions / FAQ
Who is Drifts for?
Drifts is for developers using AI agents who build multi-sensory, time-locked experiences on drifts.bot via MCP.
When should I use Drifts?
Use Drifts when prototyping or shipping agent-driven journeys that need progression locks, reviews, and hosting—not for core app databases or security audits.
How do I add Drifts to my agent?
Configure io.github.geeks-accelerator/drifts with stdio and npm mcp-drifts; set DRIFTS_API_KEY for journeys and hosting, and optionally DRIFTS_API_URL for local API bases.