Build with Futurecast

Futurecast has an agent platform. Anything that speaks MCP or plain HTTPS can read a user's boards and futures and queue changes, with the user's approval.

Connect

  • MCP endpoint: https://api.futurecastapp.com/mcp
  • REST API: https://api.futurecastapp.com/v1/agent/... with the full OpenAPI spec at api.futurecastapp.com/openapi.json
  • CLI: npm install -g futurecast, then run futurecast login

How access works

Every connection starts with the user. Your client registers itself (OAuth 2.1, PKCE, dynamic registration), sends the user to authorize, and Futurecast shows a pairing code. The user approves the connection inside the app and chooses what you can do:

  • read — see the synced catalog of futures and boards
  • write — queue changes like creating futures or organizing boards
  • visions — queue AI vision images (needs write too)

Tokens only work while the grant is active. The user can revoke any agent in Futurecast at any time.

The two rules

  1. The phone is the source of truth. Reads come from a private mirrored catalog the user's phone keeps in sync. While it is seeding, results may be partial and responses say so. Private boards are simply absent.
  2. Writes are queued, not instant. A write returns queued with a command_id, and it applies the next time the user opens Futurecast. Creation responses include the id the item will have once applied, so you can chain calls freely. Never tell a user a change is live until the command reports applied.

Support

Questions or a stuck integration: see futurecastapp.com/support