# ConnectWise PSA MCP server with security roles

> A ConnectWise PSA MCP server with security roles: why a 2,858-tool connector needs an allow rule on the Elaichi role, and how an API member's role caps calls.

**TL;DR** Elaichi's ConnectWise PSA connector carries 2,858 tools, 313 of them with delete in the name. ConnectWise limits an API member by the security role you give it, and Elaichi limits each person by a restriction on their Elaichi role. Use both. At this size a block list cannot keep up, so write an allow rule that names the few tools a service desk needs.

## Does a ConnectWise PSA MCP server with security roles work in Claude and ChatGPT?

Yes. Connect ConnectWise PSA in Elaichi with an API member's keys, add https://api.elaichi.ai/mcp in Claude, ChatGPT, Cursor or Microsoft Copilot, and hold the service desk to a short allow rule of named ticket, note and time tools on its Elaichi role.

The scale is the reason. Elaichi's [ConnectWise PSA connector](/connectors/connectwisepsa/) has 2,858 tools covering tickets, time entries, agreements, invoicing, company setup and member records. ConnectWise describes PSA as a tool for MSPs to coordinate tickets, projects, time tracking and billing (checked November 2026, [ConnectWise's PSA page](https://www.connectwise.com/platform/psa)).

## What does a ConnectWise security role control?

A security role sets what a ConnectWise member may do in each module. You create one under System, then Security Roles. Cisco's setup guide sets levels per module, such as Add, Edit and Inquire at All for Companies, Configurations (checked November 2026, [Cisco's ConnectWise guide](https://www.cisco.com/c/en/us/support/docs/security/umbrella/225008-configure-api-keys-in-connectwise-for.html)).

Acronis's guide shows three shapes of role: the full set of Add, Edit, Delete and Inquire for Service Tickets, Edit and Inquire for Company Maintenance, and Inquire alone for Contacts (checked November 2026, [Acronis's role guide](https://www.acronis.com/en/support/documentation/ConnectWisePSA/create-api-role.html)). ConnectWise's own developer and documentation sites ask for a sign-in, so these guides stand in for them. The role is the first limit. Elaichi's restriction is the second, and it holds even if the role is set too wide.

## How does a ConnectWise API member work?

An API member is the identity a connected app uses. You create it under System, Members, API Members, give it a role, and make a key pair on its API Keys tab. It does not use a Manage user license, and the private key is shown only once (checked November 2026, [Acronis's API member guide](https://www.acronis.com/en/support/documentation/ConnectWisePSA/creating-api-member-in-connectwise-manage.html)).

N-able's guide adds that the member must carry the role you created for it (checked November 2026, [N-able's API key guide](https://documentation.n-able.com/N-central/userguide/Content/Administration/PSA_Integration/ConnectWise/PSA_ConnectWise_API_Keys.htm)). In Elaichi, every call through a connection uses the account that connection was made with. Give the service desk one API member on a narrow role and billing a second on a wider one. Do not reuse an administrator's keys.

## Should the service desk role use an allow rule or block rules?

An allow rule, because ConnectWise PSA has 2,858 tools. Holding a role to an app's reads takes either an allow rule naming those reads, plus allow rules for every other app the role uses (once a role carries any allow rule, every connector and tool none of its allow rules names is blocked for that role), or block rules naming every tool on the app that is not a read (a layer with only block rules has no allowlist, so everything it does not block passes it).

The test is which list you could write down. A service desk needs about a dozen ConnectWise tools. Block rules would have to name the thousands that remain, and every tool ConnectWise adds would be reachable by default. The allow rule names the dozen and leaves the rest out of reach, at the cost of adding whole-connector allow rules for the role's other apps. Our guide to [allow lists against block lists](/blog/allowlist-vs-blocklist-mcp-tools/) covers the general case.

## Which ConnectWise tools belong on a service desk role?

Start with reads: list_all_connectwisepsa_tickets, get_single_connectwisepsa_ticket_by_id, list_all_connectwisepsa_ticket_notes, list_all_connectwisepsa_members and list_all_connectwisepsa_company_contacts. Add the configuration lookups your people use.

Two writes cover most of a day. create_a_connectwisepsa_ticket_note adds an update. update_a_connectwisepsa_ticket_by_id changes status or assignment. create_a_connectwisepsa_time_entry needs its own decision, because time entries feed billing.

Leave these unnamed: delete_a_connectwisepsa_ticket_by_id, delete_a_connectwisepsa_time_entry_by_id, delete_a_connectwisepsa_finance_agreement_by_id, delete_a_connectwisepsa_member_by_id and update_a_connectwisepsa_member_by_id. Add connectwisepsa_company_configurations_bulk_delete too, because one call there can remove many records.

## What should stay with billing and the administrator in ConnectWise?

Agreements, invoices and member records. list_all_connectwisepsa_finance_agreements and create_a_connectwisepsa_agreement_invoice sit in the money path. Member and security tools sit in the access path.

The connector also carries project security role tools, such as create_a_connectwisepsa_project_security_role. An AI that can edit who has access to what is not a service desk assistant. Give those to a named administrator on a role of their own, and read their audit rows. A fair test is whether a technician can undo a mistake in two minutes. A wrong status can be undone. A deleted agreement cannot.

## How does a chat client cope with 2,858 ConnectWise tools?

It does not see them as a list. In Elaichi, connected tools are never listed one by one, however few there are. The model finds a tool with search_tools and runs it with execute_tool, so a technician who asks for open tickets on one customer triggers a search, then a call to list_all_connectwisepsa_tickets.

A restricted tool is left out of the tools Elaichi offers a client and cannot be called. Search still names it, flagged restricted, with no schema. The search also counts what the role cannot run, so a coordinator asking for an agreement learns it exists and can file an access request. Only a person in the console, under Governance, then Access requests, can approve it. Elaichi writes one entry for each connected-tool call that reaches execution (a call refused earlier writes none). A refusal writes none, so the log shows what ran. It names the person, the tool, the connection and the MCP client, and keeps 90 days. For longer, export to your own Datadog comes with the Black plan.

## Is a dedicated API member enough without Elaichi?

For one trusted administrator on a test board, yes. A narrow role on a dedicated API member caps what ConnectWise lets any call do, and the keys stay out of chat. That setup needs no second tool.

It stops short when several people share that member. ConnectWise then sees one identity, and the role cannot tell a technician from a billing clerk. Elaichi adds the per-person split on top of the member's role. Over MCP, it does not pause a write to ask first, so if a coordinator wants a confirm step before each ticket update, turn it on in Claude or ChatGPT. See the [ConnectWise PSA connector](/connectors/connectwisepsa/), the [full catalog](/connectors/), or how [blocking one tool differs from blocking an app](/blog/per-tool-vs-per-app-restrictions/).

## FAQ

### How many tools does the ConnectWise PSA connector have in Elaichi?

Elaichi's ConnectWise PSA connector carries 2,858 tools, and it connects with API keys. Of those, 313 have delete in the name, covering tickets, ticket notes, members, agreements, expenses, configurations and many setup tables. An AI client never sees them as one long list, because Elaichi serves connected tools through search.

### Does a ConnectWise API member use a paid user license?

Not according to one vendor guide, which says an API member does not use a Manage user license and that the private key is only shown once (checked November 2026, https://www.acronis.com/en/support/documentation/ConnectWisePSA/creating-api-member-in-connectwise-manage.html). N-able's guide agrees the private key cannot be viewed after creation (checked November 2026, https://documentation.n-able.com/N-central/userguide/Content/Administration/PSA_Integration/ConnectWise/PSA_ConnectWise_API_Keys.htm). The member still needs a security role, and that role is the real boundary on what any call can read or change.

### Should the AI use the Admin role in ConnectWise?

No, unless you want every call to carry administrator reach. One vendor guide says the Admin role can serve as an API member's role (checked November 2026, https://www.acronis.com/en/support/documentation/ConnectWisePSA/creating-api-member-in-connectwise-manage.html). Cisco's guide builds a dedicated role with module levels set one by one (checked November 2026, https://www.cisco.com/c/en/us/support/docs/security/umbrella/225008-configure-api-keys-in-connectwise-for.html). The dedicated role is the better starting point for AI work.

### If I restrict a ConnectWise tool in Elaichi, can the AI still find it?

It can find the name, but it cannot run it. Elaichi leaves a restricted tool out of what it offers a client, and a search names it as restricted with no schema. The model can then tell the person what to ask an admin for. A call made by name anyway is refused.

## Read next

- [MCP tool allowlist vs blocklist: which fits?](/blog/allowlist-vs-blocklist-mcp-tools/) — MCP tool allowlist vs blocklist: an allowlist blocks all it does not name, a blocklist stops only what it names, and an empty allow rule locks a role out.
- [Restrict one AI tool or the whole app? Six cases](/blog/per-tool-vs-per-app-restrictions/) — Restrict one AI tool when a role needs part of an app, and block the whole app when it needs none of it. Six cases, and what new tools do to each rule.
- [MCP restriction resolver precedence, as a decision tree](/blog/restriction-resolver-decision-tree/) — How the mcp restriction resolver precedence works across Elaichi's enforcement points, traced through one real tool call from browse to outbound request.
