BestTime

BestTime for AI tools

Ask when and where venues get busy.

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.

  • OAuth protected
  • Revoke anytime
One secure connection BestTime MCP connection diagram Codex, Claude Code, and Cursor connect through OAuth to BestTime, which returns forecast and live venue data. Codex Claude Code Cursor BestTimeOAuth + MCP VENUE RESULTSUnion SquareFulton MarketSouth Congress API KEYS STAY SERVER-SIDE

Available tools

Ask better location questions.

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.

Account status

No data credits

Check your plan and limits before a workflow.

“What is my BestTime account status?”

Venue forecast

Forecast

Get typical hourly foot-traffic patterns for one venue, reusing stored data when possible.

“When is Central Park usually quiet?”

Live busyness

Live

Check current relative activity when live data is available. BestTime never invents missing live data.

“How busy is this venue now?”

Venue Filter

Query

Find venues by location, time, predicted busyness, category, rating, price, and more.

“Find lively bars Friday at 9 PM.”

Read collections

Read only

List account-wide collections and inspect their venues without consuming data credits.

“Show my saved collections.”

Manage collections

Writes

Create, rename, add or remove venues, and delete collections with explicit mutation inputs.

“Add this venue to Weekend ideas.”

Client setup

Set up BestTime MCP

Choose your AI tool. You will add one endpoint, authenticate in the client, then approve access in BestTime.

1
Add the endpointTell your AI tool where BestTime lives.
2
Authenticate in the clientStart the secure browser login from your AI tool.
3
Approve in BestTimeReview permissions, then return to the client.
1

Add BestTime to Codex

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 besttime
2

Authenticate in Codex

Your browser opens BestTime. Sign in, review the requested access, and choose Approve connection.

3

Confirm the connection

Run codex mcp get besttime, then ask Codex to check your BestTime account status.

If you revoked BestTime before, repeat these steps.A new connection is created. Your old connection stays visible in connection history.
Manage AI tool connections
What happens when I revoke a connection?

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.

Does MCP use my BestTime credits?

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.

Can an AI tool change my collections?

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.

Which BestTime features are included?

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

No API key to copy.

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.

1

Your AI tool requests access

You start authentication from Codex, Claude Code, Cursor, or another compatible client.

OAuth 2.1 + PKCE
2

You approve in BestTime

Review the requested data and collection permissions before anything is connected.

Scoped to your account
3

Usage follows your plan

Forecast, live, and Venue Filter calls use the same credits or metered billing as equivalent API usage.

Visible as MCP usage
API keys stay server-sideNo customer API key is sent to or stored by the AI client.
Dedicated usage logsUsage identifies the client, tool, and request.
Revoke anytimeThe client loses access immediately after revocation.