Manage Plutio clients, projects, tasks, time entries and invoices. For freelancers and teams that manage client work in Plutio. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"plutio": {
"url": "https://plutio.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"plutio": {
"type": "http",
"url": "https://plutio.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The AI reads projects and their tasks, checks project status and due dates, and identifies overdue work for a client or project.
plutio_list_projects plutio_list_tasks
The AI reads invoice status, amounts paid and due dates, then checks associated transactions to help you review outstanding client balances.
plutio_list_invoices plutio_list_transactions
The AI adds a client record and creates a project for that client after you confirm the details.
Changes data · plutio_create_person plutio_create_project
The AI reads a task to check its project, then records the duration you provide against that task after confirmation.
Changes data · plutio_list_tasks plutio_log_time
The AI creates a draft invoice for a person or company and adds its initial line items after you confirm the details. The invoice is not emailed and cannot yet be paid.
Changes data · plutio_create_invoice plutio_add_invoice_items
The AI finds a proposal or contract and retrieves its content blocks so you can review the written terms alongside its status.
plutio_list_proposals plutio_list_contracts plutio_get_document_blocks
The login page asks for your Workspace subdomain, Client ID and Client Secret.
In Plutio open Settings → API and create an API client; copy its Client ID and Client Secret. The workspace is the first part of your Plutio address (acme for acme.plutio.com). The client acts with the access of the person who created it, and your secret is used only to call the Plutio API on your behalf.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Workspace subdomain, Client ID and Client Secret. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Plutio connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
plutio_get_workspace | read | Get workspace The Plutio workspace this API client is connected to: name, domain, currency, locale, timezone and settings. GET /businesses. |
plutio_list_people | read | List people People: clients and your own team members (name, role, contactEmails, contactPhones, companies). Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /people. |
plutio_list_companies | read | List companies Companies (clients that group people): title, industry, people, contact details. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /companies. |
plutio_list_projects | read | List projects Projects: name, client, status, dates, budget, billing rate. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /projects. |
plutio_list_task_boards | read | List task boards Task boards of projects. A project has one or more boards that hold tasks. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /task-boards. |
plutio_list_task_groups | read | List task groups Task groups (columns/lists on a task board). Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /task-groups. |
plutio_list_tasks | read | List tasks Tasks: title, status (incomplete, completed, overdue), dueDate, assignedTo, projectId, taskBoardId. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /tasks. |
plutio_list_statuses | read | List statuses Custom statuses (for projects and similar records): title, type, entityType. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /statuses. |
plutio_list_time_entries | read | List time entries Time entries: personId, projectId, taskId, startedAt, stoppedAt, time in seconds, billing amount and rate. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /time-tracks. |
plutio_list_categories | read | List categories Categories used to organize records such as time entries and transactions. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /categories. |
plutio_list_events | read | List events Calendar events: title, startDate, endDate, location, participants. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /events. |
plutio_list_schedulers | read | List schedulers Scheduling pages (booking links) and their settings. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /scheduler. |
plutio_list_invoices | read | List invoices Invoices: name, client, status (draft, pending, paid and so on), amount, amountPaid, currency, dueDate, issueDate. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /invoices. |
plutio_list_invoice_subscriptions | read | List recurring invoices Recurring invoice subscriptions: client, schedule, amount. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /invoice-subscriptions. |
plutio_list_transactions | read | List transactions Payments and expenses: amount, currency, client, invoiceId, status, type, issueDate. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /transactions. |
plutio_list_proposals | read | List proposals Proposals: name, client, status, amount. The text is in blocks: see plutio_get_document_blocks. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /proposals. |
plutio_list_contracts | read | List contracts Contracts: name, client, status, signatures. The text is in blocks: see plutio_get_document_blocks. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /contracts. |
plutio_list_forms | read | List forms Forms (intake forms, questionnaires): name and status. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /forms. |
plutio_list_form_responses | read | List form responses Submitted responses to forms. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /form-responses. |
plutio_list_notes | read | List notes Notes: title, descriptionHTML, entityType and entityId of the record they belong to. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /notes. |
plutio_list_comments | read | List comments Comments on tasks, files and conversations: bodyHTML, createdBy, entityType, entityId. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /comments. |
plutio_list_conversations | read | List conversations Inbox conversations: subject, participants, last message. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /conversations. |
plutio_list_wiki_pages | read | List wiki pages Pages of the Plutio wiki / knowledge base. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /wiki-entities. |
plutio_list_files | read | List files File records (name, size, folder, sharing). File contents are not downloaded. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /files. |
plutio_list_folders | read | List folders File folders. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /file-folders. |
plutio_list_custom_fields | read | List custom fields Custom field definitions (label, type, which records they apply to). Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /custom-fields. |
plutio_get_document_blocks | read | Get document blocks The content blocks of a contract, proposal or invoice: the written text (textHTML) and, for invoices, the line items. A document record only holds block ids. GET /blocks (entityType and entityId are both required). |
plutio_create_person | write | Create person WRITE: add a person (a client by default) to the workspace. Returns the new record with its _id. POST /people. |
plutio_create_company | write | Create company WRITE: add a company, optionally linking existing people to it. Returns the new record. POST /companies. |
plutio_create_project | write | Create project WRITE: create a project. Plutio gives it a default status and a first task board (find it with plutio_list_task_boards). Returns the new record. POST /projects. |
plutio_create_task | write | Create task WRITE: add a task to a project's task board. Get taskBoardId from plutio_list_task_boards (projectId filter). New tasks start as incomplete. Returns the new record. POST /tasks. |
plutio_update_task | write | Update task WRITE: change a task's title, status (incomplete, completed, overdue), due date or description. Only the fields you pass change. Returns the updated record. PUT /tasks. |
plutio_log_time | write | Log time WRITE: record a time entry against a task. projectId must be the task's own project (read the task first). time is the length in seconds (5400 = 1.5 hours). POST /time-tracks. |
plutio_create_comment | write | Comment on a task WRITE: post a comment on a task, file or conversation. Visible to everyone who can see that record. Returns the new record. POST /comments. |
plutio_create_event | write | Create event WRITE: add a calendar event. No invitations are sent. Returns the new record. POST /events. |
plutio_create_invoice | write | Create draft invoice WRITE: create a DRAFT invoice for a person or company. The client cannot pay it and nothing is emailed. Add line items with plutio_add_invoice_items. Returns the new record. POST /invoices. |
plutio_add_invoice_items | write | Add invoice line items WRITE: put line items on an invoice that has none yet (an invoice made with plutio_create_invoice). Refuses an invoice that already has an items block. Plutio works out line totals, subtotal and total. POST /blocks. |
plutio_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
plutio_request_feature | Request a missing feature Tell usefulapi that the user needs something the Plutio tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
plutio_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Plutio (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
plutio_cancel_subscription | Cancel the Pro subscription Cancel the caller's Plutio Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run plutio_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper workspace | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this Plutio server only. Subscribe with plutio_upgrade (it returns a Stripe Checkout link). Cancel any time with plutio_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running plutio_upgrade before then undoes the cancel. Or write to [email protected].
Review project progress and overdue tasks. Review outstanding invoices. Create a client and a project. Record time against a task. Prepare a draft invoice with line items. Read a proposal or contract. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Plutio. The server calls the Plutio API with your own Plutio access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Workspace subdomain, Client ID and Client Secret. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Workspace subdomain, Client ID and Client Secret. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Plutio API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Plutio.
Yes, if you approve it. 10 of the 37 Plutio tools can create or change data. The other 27 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this Plutio server only. Cancel any time: Pro then runs to the end of the paid period. Run plutio_usage_status to see how many calls you used.
Ask the AI to run plutio_upgrade: it returns a Stripe Checkout link. To cancel, run plutio_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with plutio_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.