MSPCFO API Patterns
Overview
MSPCFO runs a first-party hosted MCP server at https://app.mspcfo.com/mcp.
There is no WYRE sidecar. Conduit proxies the server through its unified
endpoint, https://conduit.wyre.ai/v1/mcp, and handles sign-in. This skill
covers what is not guessable from the tools themselves: how auth works,
why tool names must be discovered live, and who can see the tools.
Anti-triggers
- Which client or agreement is losing money — use
mspcfo-client-profitability or mspcfo-agreement-pricing-review.
- Technician hours and utilization — use
mspcfo-technician-utilization.
Connection and authentication
- Auth is OAuth 2.0 authorization code with PKCE (S256), scope "mcp",
against MSPCFO's own authorization server. Conduit registers a public
client, so there is no client secret.
- The user connects once in Conduit (Connections → MSPCFO), signs in
with their MSPCFO account in the browser, and Conduit keeps the access
and refresh tokens server-side. Conduit sends the access token to MSPCFO
as a bearer token itself; the client sends no vendor header.
- The plugin therefore ships no
.mcp.json; Claude Code reaches the tools
through wyre-gateway. Never add an Authorization header or an API key
variable for MSPCFO: there is none, and Conduit drops client headers.
- The token carries the signed-in MSPCFO user's permissions. If a report
is missing or partial, the MSPCFO account may not have access to it.
The admin-only gate in Conduit
MSPCFO's tools are on Conduit's unclassified backlog: no tool has a tier
yet, so Conduit fails closed.
- Admin-tier callers see every tool MSPCFO lists.
- Every other caller sees no MSPCFO tools.
When no MSPCFO tools appear, check the connection first: in Conduit,
Connections → MSPCFO should show the connection as connected and
signed in. An expired or revoked sign-in, or an MSPCFO outage, also
leaves the session with no MSPCFO tools, even for an admin; signing in
again fixes the first. Only when the connection is connected and signed
in and the tools are still missing is the cause the caller's Conduit
tier being below admin. Then say so plainly and point the user to a
Conduit admin.
Every MSPCFO tool is admin-gated in Conduit, whatever it does. That will
change only after WYRE classifies the tools from a verified live
connection.
Discovering tools
MSPCFO does not publish its MCP tool names, and this plugin does not
invent them.
- Read the MSPCFO tools from the live tool list in the session (they
appear on the Conduit server under the
mspcfo connector).
- Match each job to a tool by its description and input schema. MSPCFO's
public MCP page says the server draws on these reports: Client P&L,
Client Segments, Market Segments, Member Work Report, Members Billing
by Month, Utilization Hours and FFA Components.
- If no listed tool covers the report you need, tell the user which
report is missing. Do not fall back to a guessed tool name or to
arithmetic on unrelated data presented as if MSPCFO computed it.
- If a tool's description says it creates, updates, deletes, sends or
schedules something, treat it as a write. Describe the exact call and
get the user's approval first.
Parameters and result size
MSPCFO has not published parameter schemas or pagination rules. Read them
from each tool's input schema. In practice:
- Reports are period-based. Pass an explicit date range or period and
state it in your answer. Prefer whole months and like-for-like
comparisons (this quarter vs. the same quarter last year).
- Scope to one client or agreement when the question is about one client.
Portfolio-wide pulls are large.
- If a result looks cut off (round-number row counts, a continuation
token, a "more results" hint), follow the tool's own paging field if it
has one. Otherwise narrow the period or scope, and say the first answer
was partial.
Errors
| Situation |
Likely cause |
Action |
| No MSPCFO tools listed |
Caller's Conduit tier is below admin |
Ask a Conduit admin; sign-in is fine |
| Connect refused or never completes |
Sign-in cancelled, or MSPCFO rejected the OAuth request |
Retry the sign-in once; if it still fails, contact WYRE |
| Auth error after a working period |
Refresh failed (MSPCFO user disabled, password reset, access revoked) |
Reconnect in Conduit and sign in again |
| Empty report, no error |
Period has no data, filter too narrow, or the MSPCFO user cannot see it |
Widen the period, then check the user's MSPCFO permissions |
| Throttling or upstream 5xx |
MSPCFO or Conduit is rate limiting or degraded |
Wait, then retry once with a smaller scope; do not loop |
MSPCFO does not publish rate limits. Sequence portfolio sweeps client by
client rather than firing many large report calls at once.
Data freshness and trust
- MSPCFO's numbers come from synced PSA data plus MSPCFO's cost and
agreement setup. They are only as good as time entry, labor cost rates
and agreement mapping in the PSA.
- MSPCFO describes its MCP as early and asks customers to check important
numbers against the report in the MSPCFO app. Do that before anything
reaches a client or a pricing decision.
- Calculated metrics (efficiency, employee revenue productivity, margins)
are MSPCFO's definitions. Quote them as MSPCFO's figures rather than
re-deriving them with a different formula.
Related Skills
1---2name: mspcfo-api-patterns3description: >4 MSPCFO MCP fundamentals for this plugin: OAuth 2.0 + PKCE browser sign-in5 brokered by Conduit (no API key, no headers), the admin-only tool gate6 while MSPCFO's tools are unclassified in Conduit, discovering tool names7 at runtime because MSPCFO does not publish them, report parameters and8 result size, error handling, and data-freshness caveats.9when_to_use: >-10 When connecting MSPCFO, working out which MSPCFO tool to call, or11 debugging missing tools, auth failures or odd numbers from the MSPCFO MCP12 server. Use when: mspcfo api, mspcfo auth, mspcfo oauth, mspcfo sign in,13 mspcfo connect, mspcfo tools missing, mspcfo error, or mspcfo mcp.14metadata:15 source: https://skillmd.com/skills/wyre-ai/mspcfo-api-patterns16---1718# MSPCFO API Patterns1920## Overview2122MSPCFO runs a first-party hosted MCP server at `https://app.mspcfo.com/mcp`.23There is no WYRE sidecar. Conduit proxies the server through its unified24endpoint, `https://conduit.wyre.ai/v1/mcp`, and handles sign-in. This skill25covers what is not guessable from the tools themselves: how auth works,26why tool names must be discovered live, and who can see the tools.2728## Anti-triggers2930- **Which client or agreement is losing money** — use31 `mspcfo-client-profitability` or `mspcfo-agreement-pricing-review`.32- **Technician hours and utilization** — use33 `mspcfo-technician-utilization`.3435## Connection and authentication3637- Auth is OAuth 2.0 authorization code with PKCE (S256), scope "mcp",38 against MSPCFO's own authorization server. Conduit registers a public39 client, so there is no client secret.40- The user connects once in Conduit (**Connections → MSPCFO**), signs in41 with their MSPCFO account in the browser, and Conduit keeps the access42 and refresh tokens server-side. Conduit sends the access token to MSPCFO43 as a bearer token itself; the client sends no vendor header.44- The plugin therefore ships no `.mcp.json`; Claude Code reaches the tools45 through `wyre-gateway`. Never add an Authorization header or an API key46 variable for MSPCFO: there is none, and Conduit drops client headers.47- The token carries the signed-in MSPCFO user's permissions. If a report48 is missing or partial, the MSPCFO account may not have access to it.4950## The admin-only gate in Conduit5152MSPCFO's tools are on Conduit's unclassified backlog: no tool has a tier53yet, so Conduit fails closed.5455- Admin-tier callers see every tool MSPCFO lists.56- Every other caller sees **no** MSPCFO tools.5758When no MSPCFO tools appear, check the connection first: in Conduit,59**Connections → MSPCFO** should show the connection as connected and60signed in. An expired or revoked sign-in, or an MSPCFO outage, also61leaves the session with no MSPCFO tools, even for an admin; signing in62again fixes the first. Only when the connection is connected and signed63in and the tools are still missing is the cause the caller's Conduit64tier being below admin. Then say so plainly and point the user to a65Conduit admin.6667Every MSPCFO tool is admin-gated in Conduit, whatever it does. That will68change only after WYRE classifies the tools from a verified live69connection.7071## Discovering tools7273MSPCFO does not publish its MCP tool names, and this plugin does not74invent them.75761. Read the MSPCFO tools from the live tool list in the session (they77 appear on the Conduit server under the `mspcfo` connector).782. Match each job to a tool by its description and input schema. MSPCFO's79 public MCP page says the server draws on these reports: Client P&L,80 Client Segments, Market Segments, Member Work Report, Members Billing81 by Month, Utilization Hours and FFA Components.823. If no listed tool covers the report you need, tell the user which83 report is missing. Do not fall back to a guessed tool name or to84 arithmetic on unrelated data presented as if MSPCFO computed it.854. If a tool's description says it creates, updates, deletes, sends or86 schedules something, treat it as a write. Describe the exact call and87 get the user's approval first.8889## Parameters and result size9091MSPCFO has not published parameter schemas or pagination rules. Read them92from each tool's input schema. In practice:9394- Reports are period-based. Pass an explicit date range or period and95 state it in your answer. Prefer whole months and like-for-like96 comparisons (this quarter vs. the same quarter last year).97- Scope to one client or agreement when the question is about one client.98 Portfolio-wide pulls are large.99- If a result looks cut off (round-number row counts, a continuation100 token, a "more results" hint), follow the tool's own paging field if it101 has one. Otherwise narrow the period or scope, and say the first answer102 was partial.103104## Errors105106| Situation | Likely cause | Action |107|---|---|---|108| No MSPCFO tools listed | Caller's Conduit tier is below admin | Ask a Conduit admin; sign-in is fine |109| Connect refused or never completes | Sign-in cancelled, or MSPCFO rejected the OAuth request | Retry the sign-in once; if it still fails, contact WYRE |110| Auth error after a working period | Refresh failed (MSPCFO user disabled, password reset, access revoked) | Reconnect in Conduit and sign in again |111| Empty report, no error | Period has no data, filter too narrow, or the MSPCFO user cannot see it | Widen the period, then check the user's MSPCFO permissions |112| Throttling or upstream 5xx | MSPCFO or Conduit is rate limiting or degraded | Wait, then retry once with a smaller scope; do not loop |113114MSPCFO does not publish rate limits. Sequence portfolio sweeps client by115client rather than firing many large report calls at once.116117## Data freshness and trust118119- MSPCFO's numbers come from synced PSA data plus MSPCFO's cost and120 agreement setup. They are only as good as time entry, labor cost rates121 and agreement mapping in the PSA.122- MSPCFO describes its MCP as early and asks customers to check important123 numbers against the report in the MSPCFO app. Do that before anything124 reaches a client or a pricing decision.125- Calculated metrics (efficiency, employee revenue productivity, margins)126 are MSPCFO's definitions. Quote them as MSPCFO's figures rather than127 re-deriving them with a different formula.128129## Related Skills130131- [Client profitability](../client-profitability/SKILL.md)132- [Agreement pricing review](../agreement-pricing-review/SKILL.md)133- [Technician utilization](../technician-utilization/SKILL.md)