Account status
No data creditsCheck your plan and limits before a workflow.
“What is my BestTime account status?”BestTime for AI tools
Connect BestTime to your AI tool in a few minutes. Use forecasts, live busyness, Venue Filter, and Collections from Codex, Claude Code, Cursor, or any compatible MCP client.
Available tools
The agent receives guidance about relative busyness, freshness, live availability, billing, and safe collection changes.
Important: BestTime reports normalized relative busyness from 0–100, not occupancy or visitor counts.
Check your plan and limits before a workflow.
“What is my BestTime account status?”Get typical hourly foot-traffic patterns for one venue, reusing stored data when possible.
“When is Central Park usually quiet?”Check current relative activity when live data is available. BestTime never invents missing live data.
“How busy is this venue now?”Find venues by location, time, predicted busyness, category, rating, price, and more.
“Find lively bars Friday at 9 PM.”List account-wide collections and inspect their venues without consuming data credits.
“Show my saved collections.”Create, rename, add or remove venues, and delete collections with explicit mutation inputs.
“Add this venue to Weekend ideas.”Client setup
Choose your AI tool. You will add one endpoint, authenticate in the client, then approve access in BestTime.
Run these commands in a terminal. The first adds the remote MCP server; the second starts OAuth.
codex mcp add besttime --url https://mcp.besttime.app/mcp
codex mcp login besttimeYour browser opens BestTime. Sign in, review the requested access, and choose Approve connection.
Run codex mcp get besttime, then ask Codex to check your BestTime account status.
Add it at user scope so the connection is available across projects.
claude mcp add --transport http --scope user besttime https://mcp.besttime.app/mcpStart Claude Code, enter /mcp, choose BestTime, and select Authenticate. Complete the browser approval.
Open /mcp again and check that BestTime is connected, then ask Claude to show your collections.
The button opens Cursor and pre-fills the production MCP endpoint.
Add BestTime to CursorIn Cursor’s MCP settings, find BestTime and choose Authenticate. Cursor opens the BestTime approval page in your browser.
Review the permissions, choose Approve connection, then return to Cursor and confirm BestTime is enabled.
Use this configuration in an MCP client that supports OAuth discovery.
{
"mcpServers": {
"besttime": {
"url": "https://mcp.besttime.app/mcp"
}
}
}Your client must support MCP OAuth discovery, authorization code flow, PKCE S256, and Streamable HTTP.
Approve access in BestTime, then call get_account_status before requesting paid data.
BestTime revokes the client’s OAuth grant and deactivates its hidden MCP usage identity. The AI tool can no longer call BestTime. Reconnect by repeating the setup from that client.
Account and collection reads do not consume data credits. Forecast, live, and Venue Filter calls follow the same plan, credit, and metered-billing rules as equivalent BestTime API usage.
Only when you approve collection write access. The approval page calls this out because it permits creating, renaming, adding or removing venues, and deleting collections.
Phase one includes account status, forecast, live busyness, Venue Filter, and collection read/write tools. Planner and Location Intelligence are not included yet.
Secure by design
Your AI tool receives a scoped OAuth connection. BestTime keeps a dedicated MCP usage identity server-side so calls remain tied to your account, plan, and usage logs.
You start authentication from Codex, Claude Code, Cursor, or another compatible client.
OAuth 2.1 + PKCEReview the requested data and collection permissions before anything is connected.
Scoped to your accountForecast, live, and Venue Filter calls use the same credits or metered billing as equivalent API usage.
Visible as MCP usage