Skip to main content
The current API is sufficient for agent integration via raw HTTP — every flow on this site works today against https://api.riftmap.dev/api/v1 with a workspace API key. Two packaging layers are designed but deferred until there’s pull from real users. Building them before users ask risks designing for hypothetical workflows.

​
MCP server (riftmap-mcp)

Wraps the agent‑facing endpoints as MCP tools so Claude Code, Cursor, and Cline can use them without any HTTP plumbing in the agent’s prompt. Planned layout:
  • Published to PyPI as a separate package: pipx install riftmap-mcp.
  • Python implementation using Anthropic’s official mcp SDK.
Planned tool surface:
Auth: environment variables only.

​
CLI (riftmap)

Same surface as a shell command for CI pipelines and humans who’d rather pipe JSON than write curl invocations. Planned commands:
  • Ships as a riftmap console_script on PyPI, separate from internal operator tooling.
  • JSON output by default (agent‑friendly); --pretty flag for human reading.
  • Same env contract as the MCP server.

​
Order when building

CLI first — its auth and base‑URL plumbing is reused by the MCP server, which then becomes thin tool definitions over the CLI logic.

​
Why not now

The data and endpoints are the load‑bearing piece. Packaging is mechanical once the surface is stable. If you want either of these tomorrow and would actually use it, email hello@riftmap.dev — concrete demand is what unblocks the build.