Finely Connect · MCP

Your time, wherever you think.

Finely Connect lets you plug your own Finely account into Claude — or any client that speaks the Model Context Protocol. One OAuth approval and your assistant can read your unified agenda, goals, tasks, and priorities, and (if you allow it) schedule tasks and log progress on your behalf.

MCP endpoint · Streamable HTTP
https://mcp.finely.day/mcp

OAuth 2.1 with PKCE and dynamic client registration. Discovery metadata is served automatically at /.well-known/oauth-authorization-server — compliant clients configure themselves.

Setup

Connected in under a minute.

Add the connector

In Claude, open Settings → Connectors → Add custom connector and paste the Finely Connect URL:

https://mcp.finely.day/mcp

Sign in & approve

Claude discovers Finely's OAuth server and opens the Finely login page. Sign in with your Finely account, review exactly what access you're granting — read, write, or both — and approve.

Ask about your day

The finely tools now appear in every chat. Try: "What's on my plate today, and which goals need attention?"

Add the server

One command — the OAuth flow opens in your browser:

claude mcp add --transport http finely https://mcp.finely.day/mcp

Approve in the browser

Sign in to Finely, review the requested scopes, and approve. Tokens are stored by your client — Finely never sees or stores your Claude credentials.

Build with your schedule

Generate a morning-agenda artifact, wire your day into scripts, or let an agent triage your task backlog against real free slots.

Point your client at the endpoint

Finely Connect implements the MCP Streamable HTTP transport with OAuth 2.1 authorization (PKCE S256, dynamic client registration at /register). Any spec-compliant client can connect:

https://mcp.finely.day/mcp

Let discovery do the work

Unauthenticated requests receive a spec-correct 401 with WWW-Authenticate and resource metadata, so clients auto-discover the authorization server at /.well-known/oauth-authorization-server and run the flow without manual configuration.

Request only what you need

Scopes are finely:read and finely:write — request the minimum for your use case. Each is shown to the user in plain English on the consent page.

Tool reference

Ten tools. Your whole day.

Every tool resolves the acting user from the verified OAuth token — cross-user access is structurally impossible.

ToolScopeWhat it does
get_daily_agendareadThe one-call day view: events, goals with today's status, priorities, and open or overdue tasks together.
list_eventsreadCalendar events across every connected provider, filterable by date range.
list_goalsreadYour goals with streaks and completion status.
list_tasksreadTask backlog and scheduled tasks, filterable by status and date.
list_prioritiesreadToday's ranked priorities.
list_triagereadItems waiting in your triage inbox — captured but not yet committed.
create_taskwriteAdd a task to your backlog with title, due date, priority, and estimate.
schedule_taskwritePlace a task on your calendar at a specific date and time.
set_prioritieswriteSet today's priorities (maximum five per day — by design).
log_goalwriteLog progress on a goal you own — done or skipped, streak-aware.

finely:read

"See your events, goals, tasks, and priorities." Enough for agendas, dashboards, and briefings. Grant this alone if you only want reporting.

finely:write

"Create and schedule tasks, set priorities, and log goal progress." For assistants that act, not just observe. Never granted implicitly.

Security

Built like it holds your life. Because it does.

Questions

The fine print, finely.

Do I need a Finely account?

Yes — Finely Connect exposes your data, so it needs to know who you are. The beta is free: grab the app for iOS or Android, create an account, and connect a calendar first.

Can other people's clients see my data?

No. Every tool call resolves the acting user from the verified OAuth token on that request. There is no parameter, header, or trick that reaches another account's data — the isolation is structural, not policy.

How do I disconnect a client?

Revoke the grant from Finely's connected-apps settings (or via the API). Revocation is immediate: refresh tokens die and any live access tokens are invalidated on the spot. You can also remove the connector on the client side, but revoking at Finely is the authoritative kill switch.

Which clients work with Finely Connect?

Anything that implements MCP over Streamable HTTP with OAuth: Claude on web and desktop (as a custom connector), Claude Code, and other spec-compliant MCP clients and SDKs.

What can I build with it?

Morning-briefing artifacts that re-fetch your agenda every time they open. A weekly review that compares scheduled versus actual time. An agent that triages your task backlog into real free slots. If it can call an MCP tool, it can reason over your day.