Connect Prioza

Connect your AI assistant to your Prioza backlog to find, create and prioritise tasks from a conversation. The Prioza app works on its own; this connection is optional.

Before you start

You need a Prioza account and a client that supports remote MCP over Streamable HTTP with OAuth. Signing into the web app alone does not connect your assistant. Use your Prioza account on the server’s sign-in page when your client opens it.

Server URL — copy the whole address, including /mcp:

https://prioritask-api.onrender.com/mcp

The service still uses the Prioritask name in its hosting address and some sign-in screens. This is the endpoint advertised by Prioza’s server. It is different from the web app’s URL.

Connect with Codex

In Codex’s MCP settings, add a remote HTTP server named prioza with the URL above, then start its OAuth sign-in. If your version does not expose that option, use the Codex CLI on the same machine:

codex mcp add prioza --url https://prioritask-api.onrender.com/mcp

Complete the sign-in opened by Codex. If you need to retry authorization, run:

codex mcp login prioza

Sign in yourself and review the access requested. You do not need to paste a password, API key or OAuth client secret into a conversation or configuration file.

Run codex mcp list to check that the server is configured, then check its tools in Codex. A saved server entry alone does not prove authentication succeeded. If tools are missing after login, reopen your session or restart the app and check again.

For current client options, see the official Codex MCP guide.

Connect with Claude or another MCP client

Add a remote server
Open your client’s connector or MCP settings. In Claude, look for Connectors and Add custom connector where available. Menu names and availability depend on the client version and account.
Enter the URL and choose OAuth
Use https://prioritask-api.onrender.com/mcp. Let the client discover the OAuth settings; do not invent a client ID or secret. A URL-only connector without OAuth support cannot complete this setup.
Sign in and review access
Your client opens the Prioza authorization page on prioritask-api.onrender.com. Sign in with the intended Prioza account and review the requested access. OAuth associates the connection with that account.

Check the connection before changing data

Check that your assistant exposes Prioza tools such as list_tasks, list_tags and create_task. Start with a read-only request:

"Use Prioza to list my tags and show up to five tasks. Do not create or change anything."

Confirm that the returned tasks belong to the expected account. An empty backlog can be valid; an authentication error is not a successful connection. Only then ask your assistant to create or update work.

If the connection fails

Not in the plugin directory: add the remote MCP URL manually if your client supports custom servers. A directory listing is not required.
A browser visit returns 405: this endpoint accepts MCP requests through POST. Opening it as a normal web page is not a connection test.
401 or unauthorized: an initial authentication challenge is expected before OAuth. If it persists after sign-in, reconnect and complete authorization.
Registration fails with invalid_redirect_uri: Confirm that the server is up to date. Native clients use HTTP callbacks on the local loopback IP (127.0.0.1 or [::1]); older Prioza deployments accepted only HTTPS callbacks. For other registration errors, confirm the full URL and your client’s support for OAuth discovery and dynamic client registration. Do not enter made-up credentials.
503 or a timeout: retry later. If it persists, report it to support; the server may be unavailable or its authentication configuration may need attention.
403 / origin not allowed: the operator must review the allowed origins for your client. Do not disable browser security to work around it.
Configured but no tools: finish OAuth, enable the connection in your client, and reload the session. Saving a URL is only the first step.

Access and disconnection

The connection includes tools that change or delete data; it is not a read-only integration. Review tool actions in your assistant. Never share access tokens in prompts, screenshots or source control.

To disconnect Codex, run codex mcp logout prioza; to remove its configuration, run codex mcp remove prioza. In other clients, use their disconnect or remove control. Removing a client configuration does not delete your Prioza tasks.

Operator-managed integrations can also use a static Bearer token. This is not the recommended account sign-in flow. The operator must configure the intended user scope with MCP_DEFAULT_USER_ID before sharing access; never reuse an unscoped server token for a personal connection.

Try these first

"Add three tasks to Prioza: send the Q3 invoice by Friday, review Ana's pull request, and book the flights to Lima."

"What should I work on right now? Skip anything work related."

"Show me my backlog by priority and tell me how much of it is overdue."

What Prioza can do from here

Tools work with the same backlog as the app. The exact tool list depends on the deployed server version; inspect the tools exposed by your connected client.

Every tool is either read-only or clearly marked as one that changes your data.

Reads your data

Answer "what should I do now" with a short, ranked list
Show today's tasks and today's habits
List or search tasks, goals, habits, tags and tag groups
Open a single task or goal in full detail
Summarise the backlog by priority, and review the week goal by goal

Changes your data

Create tasks, goals and habits
Update a task, set its priority, start it or complete it
Rank tasks or goals from a list you order
Mark a habit for the day and set the value of a key result
Delete a task, a goal or a habit, which cannot be undone

Accounts and plans

You need a Prioza account to connect — the same one you sign into the app with. Prioza is free while in beta.

Support

Write to support@prioza.net. We answer within two business days.