Connect TASKn to an AI assistant

Talk to your tasks. Once connected, an MCP-compatible AI app can read and manage your TASKn account directly inside a conversation, no app-switching.

View TASKn in the Claude Directory

📱 Opened this from the TASKn app on your phone? The actual connection is set up inside Claude’s desktop or web app (claude.ai), not here. Tap the copy buttons below to grab the server details now, then paste them in when you’re at a computer.

What this does

TASKn exposes an MCP (Model Context Protocol) connector — an open standard that lets AI assistants securely use an app’s real data and actions, with your explicit sign-in and approval. It’s not a Claude-only thing: any app that speaks MCP can connect the same way, including Cursor, OpenAI’s Codex, and more (see below). Once connected, you can ask something like “what’s on my plate today?” or “add a task to call the dentist tomorrow” and it will actually read from and write to your TASKn account.

Set it up (2 minutes)

On a computer, open Claude at claude.ai (or the desktop app), go to Settings → Connectors, and choose Add custom connector.
Fill in these two fields — tap Copy now if you’re on your phone and want to send these to yourself for later:
Name
TASKn
Remote MCP server URL
https://mcp.taskn.app/functions/v1/mcp
Click Add, then Connect — you’ll be taken to a TASKn sign-in screen. Use the same Google, Apple, or email login you already use in the app.
Review what Claude is asking for and click Approve. That’s it — Claude now has access.

What Claude can do once connected

View your task feed

Create a task

Update a task

Complete a task

Search your tasks

List your projects

List tasks shared with you

See your daily stats

Other MCP apps Official connectors coming soon

TASKn works with remote MCP clients that support HTTPS Streamable HTTP and browser-based OAuth 2.1 sign-in. Claude’s setup above is the simplest — a couple of fields in a settings screen. Some other compatible apps are developer tools that connect via a config file on a computer instead of a menu — open this section when you’re at a keyboard, not on your phone.

Developer setup: Cursor and Codex

Name

TASKn

MCP server URL

https://mcp.taskn.app/functions/v1/mcp

Cursor — add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "taskn": { "url": "https://mcp.taskn.app/functions/v1/mcp" }
  }
}

OpenAI Codex CLI — run:

codex mcp add taskn --url https://mcp.taskn.app/functions/v1/mcp

Grok — on grok.com go to Connectors → New Connector → Custom, and enter:

MCP server URL

https://mcp.taskn.app/functions/v1/mcp

Grok discovers TASKn’s sign-in automatically — complete the TASKn login (Google, Apple, or email), approve access, and Grok can read and manage your tasks right in the conversation.

A client must support remote HTTP MCP plus OAuth browser authorization. Local-only or stdio-only MCP clients cannot use this hosted connector directly. Exact setup varies by app, so check that app’s own MCP docs.

OAuth and Dynamic Client Registration for connector developers

TASKn uses OAuth 2.1 authorization-code flow with PKCE. A user signs in and explicitly approves access in their browser; TASKn does not issue a personal API key for this connector.

Protected resource metadata

https://mcp.taskn.app/.well-known/oauth-protected-resource/functions/v1/mcp

OAuth issuer

https://qxxjwdzxmflvzungriuq.supabase.co/auth/v1

Authorization endpoint

https://qxxjwdzxmflvzungriuq.supabase.co/auth/v1/oauth/authorize

Token endpoint

https://qxxjwdzxmflvzungriuq.supabase.co/auth/v1/oauth/token

Dynamic client registration endpoint

https://qxxjwdzxmflvzungriuq.supabase.co/auth/v1/oauth/clients/register

Prefer discovery: make an unauthenticated request to the MCP endpoint, read its WWW-Authenticate resource_metadata URL, then fetch the issuer metadata from /.well-known/oauth-authorization-server. This avoids hard-coding endpoints as TASKn evolves.

Dynamic Client Registration is enabled. Connector builders should register a public client with an exact HTTPS redirect URI, PKCE S256, and token_endpoint_auth_method: none; there is no client secret for a public client. If a host asks for a client ID instead of performing DCR itself, its integration owner can register that client and provide the returned client ID to the host.

TASKn currently relies on the signed-in user’s existing row-level access controls. Supabase OAuth supports standard identity scopes, not custom task-level scopes, so connector builders should use TASKn’s tool descriptions and obtain user confirmation before actions that change data.

Muse Connector Platform Official connectors coming soon

TASKn has a hosted HTTPS MCP endpoint and OAuth sign-in flow ready for Muse’s Existing MCP submission path. Muse Connector Platform is different from installing an MCP server in a developer tool: a connector must be submitted at muse.ai/platform and approved after Meta’s functional, security, legal, and end-to-end review. Muse has not published a separate MCP transport or tool-schema requirement, so this page is the current technical reference for the submission.

Whichever app you connect, it only ever sees and changes your own TASKn account — the same permissions you already have signed in. TASKn is never given your password directly. To disconnect, use the connected-app controls offered by your MCP client; TASKn-side connected-app management is not available yet.

Troubleshooting

If the sign-in page appears blank, an ad-blocker or privacy extension in your browser may be hiding it — try disabling it for taskn.app, or use a different browser, then reload the page.

Still stuck? Email support@taskn.app.