Connect Curoxi Through MCP

What Curoxi MCP provides

Curoxi MCP gives compatible AI clients read-only access to the data the signed-in user is already allowed to see. The production server URL is https://mcp.curoxi.com/mcp.

Every token is fixed to one user and one active project. Tools cannot switch the token to another project, customer, or company. Curoxi checks the live user, role, project access, subscription, and feature configuration again on every request.

• Read-only tools only; agents cannot create, update, approve, sign, pay, delete, or deploy
• One user and one project workspace per token
• Immediate revocation and expiry enforcement through Redis
• No database credentials, application secrets, local file paths, or binary documents are returned

Create and connect a personal token

• Company admins can select any active company project; other company users see assigned projects only
• Customer users see projects belonging to their customer account
• Only a Super Admin can create or revoke a platform personal token
• Use one token per client and revoke it when that client is no longer trusted

1. Sign in to the company, customer, or Super Admin workspace that should own the connection.
2. Open Settings and select MCP Access.
3. Enter a token name that identifies the client or device.
4. Select the project workspace. This project cannot be changed after creation.
5. Choose an expiry of 1, 7, or 30 days.
6. Create the token and copy it immediately. Curoxi cannot display it again.
7. Configure the MCP client with https://mcp.curoxi.com/mcp and the generated token.

Tools available to company logins

• Profile and accessible projects: getProfile, listAccessibleProjects
• Projects and delivery: getProjectSummary, listProjectMembers, listReleases, listSprints, getActiveRelease, getActiveSprint
• Tasks: listTasks, listMyTasks, listMyPendingTasks, listMyInProgressTasks, listCompletedTasks, getTask, getTaskHistory
• Customer support: listSupportTickets and getSupportTicket when Support is included
• Documents: getMSA, getSOW, and getNDA when Documents is included
• Rates: listTaskRates and getRateHistory for company admins, billing managers, and project managers when Billing and Rates are included
• Invoices: listInvoices, invoice status shortcuts, and getInvoice for company admins and billing managers when Billing and Invoice Tracking are included
• Billing analytics: getBillingAnalytics for company admins and billing managers when Billing and Analytics are included
• Subscription payments: listCompanyPayments for the company admin

Tools available to customer logins

• Customer users receive the same project, task, release, sprint, support, document, rate, invoice, and billing analytics tools only when their subscription includes those modules
• Support tickets and MSA, SOW, and NDA documents are scoped to the customer workspace derived from the selected project
• Company subscription payment history and platform administration tools are not available
• Project member data still requires project-admin authority; customer-admin status does not automatically bypass project membership rules

Tools available to Super Admin logins

• getPlatformAnalytics returns the existing platform analytics view; identities with only support roles are denied
• getPlatformAuditTrail accepts q, page, and page_size filters
• listPlatformSupportTickets accepts an optional status filter
• getPlatformSupportTicket requires ticket_id and includes comments, attachment metadata, and followers
• listPlatformSupportFollowers returns eligible follower options
• listCompanyPayments returns payment history for the company derived from the token-bound project when the superuser role permits payment visibility
• Platform support requires Super Admin, Support Manager, or Support Engineer authority
• Payment history requires Super Admin, Finance Officer, Revenue Officer, Sales Manager, or Sales Representative authority

Task tool parameters

listTasks has no required parameter. It supports view, status, priority, task_type, created_month, invoice_state, release_id, sprint_id, search, and limit. created_month uses YYYY-MM, list values can be comma separated, and limit defaults to 100 with a maximum of 200.

• view: all, archived, my_tasks, pending, my_pending, in_progress, my_in_progress, completed, my_completed, urgent, or due_this_week
• invoice_state: all, invoiced, or uninvoiced
• getTask requires task_id
• getTaskHistory requires task_id and accepts optional limit
• Task shortcut tools accept only optional limit

Invoice, support, and platform parameters

• listInvoices accepts view, billing_type, created_month, due_month, search, and limit
• Invoice view can be all, pending, unpaid, paid, partial_paid, overdue, sent, or generated
• getInvoice requires invoice_id; invoice shortcuts accept optional limit
• listSupportTickets accepts optional status and limit; getSupportTicket requires ticket_id
• listSprints requires release_id
• getPlatformAuditTrail accepts optional q, page, and page_size; page_size is limited to 100
• listPlatformSupportTickets accepts optional status; getPlatformSupportTicket requires ticket_id
• All other get/list tools have no parameters unless their description above says otherwise

Why a tool may be denied

• The token expired, was revoked, or is no longer available in Redis
• The user was disabled or their role changed
• The project was deactivated or access was removed
• The active subscription no longer includes the required module
• The supplied task, invoice, release, or ticket does not belong to the authorized scope
• The requested company or platform data requires a higher role
• A mandatory security dependency is unavailable; MCP fails closed rather than returning unchecked data

Explore Curoxi

Browse the core pages that explain how Curoxi works, how pricing is structured, and how to start a workspace.