Skip to main content
Connecting to the AskFutures MCP server uses standard OAuth 2.1 with PKCE — the same secure browser-based sign-in your MCP client already knows how to do. You don’t paste keys or manage secrets by hand.
MCP access is not self-serve yet. There is currently no toggle in the app to turn it on. To get access enabled on your account, email support@askfutures.com from the address you sign in with and ask for MCP access. Until it’s granted, you can sign in but tool calls won’t be authorized.

​
How sign-in works

When you add the server (see the quickstart), your client handles the whole flow for you:
1

Your client starts the flow

On first connect, the MCP client kicks off an OAuth 2.1 authorization request with PKCE — a proof-key handshake that keeps the exchange secure even though no shared client secret is involved.
2

You sign in on a hosted page

Your browser opens an AskFutures sign-in page. You authenticate there — the same account you use for the web app — and approve access for the client.
3

The client receives a token

AskFutures returns a short-lived access token to your client over the secure PKCE exchange. Your client stores it and sends it with every tool call.
4

Tokens refresh automatically

When the access token expires, your client uses its refresh token to get a new one in the background. You stay signed in without re-authenticating.

​
Token lifetimes

Refresh tokens are rotated: each time your client refreshes, it gets a brand new refresh token and the old one is retired. This is an OAuth 2.1 security requirement and your client handles it automatically. If you don’t use a connection for longer than the refresh window, you’ll simply be asked to sign in again next time.
All of this is automatic. Once you’ve signed in through your client, you generally won’t think about tokens again — the client refreshes and rotates them for you in the background.

​
Getting access enabled

Email support@askfutures.com from your account’s email address and ask for MCP access. We’ll enable it on your account.
Sign-in succeeding only means your identity is verified. Calls are rejected until MCP access is granted on your account. If you’ve already requested it and still see failures, reach out to support so we can check the grant.
No. MCP access uses the same account as the web app. Sign in with the email you already use, and request MCP access for that same address.

​
Next steps

Connect the MCP server

Add AskFutures to Claude Code, Cursor, or Codex.

Developers overview

The async create → wait → optimize model.

MCP tools

Every tool, what it does, and what it returns.