Resell secure MCP access to your customers.

What does reselling MCP mean for an MSP?

Reselling MCP means packaging secure access to a customer's SaaS applications as a managed service. The MSP administers a separate customer workspace, connects approved apps, grants specific MCP tools, and helps the customer's staff use those tools from compatible AI clients.

This is different from using MCP only inside the MSP. The service is designed for the people at the customer: finance, operations, sales, support, IT, or other teams that want an AI client to work with the business apps they already use. For the MSP's own PSA, RMM, security, and documentation workflows, see MCP for MSPs.

How does a managed MCP service work?

How are customer SaaS apps and users isolated?

Every managed customer can have its own workspace. Users, SaaS connections, tool grants, MCP sessions, and audit records resolve inside that workspace, so one customer does not inherit another customer's access.

Stackyapper checks the signed-in identity, selected workspace, service connection, tool grant, action risk, and confirmation policy again when a tool runs. The official MCP authorization guidance likewise recommends authorization when servers access user-specific data, administrative actions, audit history, or enterprise systems. See the Model Context Protocol authorization guide and Stackyapper's MCP access control model.

What can customer staff do with MCP?

The exact actions depend on the App and its current state, the customer's provider authorization, and the tools the MSP grants. The App directory separates Available Apps from Beta Apps that are still being worked on. A managed customer MCP service can support patterns such as:

• Ask an approved AI client to find records across permitted business systems.
• Build customer-specific summaries, reports, or client-supported artifacts from approved results.
• Use read tools first, then keep write or destructive actions separately permissioned.
• Give different departments access to different apps and tools without sharing provider credentials.
• Remove a user or tool grant without rebuilding every customer integration.

How to onboard a customer to managed MCP access

1. Create the customer workspace. Add one managed customer workspace so its users, SaaS connections, permissions, sessions, and audit records stay separate.
2. Connect the customer’s SaaS apps. Authorize supported business applications inside that customer workspace. Provider credentials stay with Stackyapper and are not sent to the AI client.
3. Grant only the approved MCP tools. Choose which tools the workspace, groups, and individual users can access. Apply confirmation policy to higher-impact actions.
4. Onboard customer staff. Invite authorized staff and connect a compatible MCP client such as Claude, ChatGPT, Codex, or Microsoft Copilot Studio using the maintained setup instructions.
5. Operate and review the service. Review activity by customer workspace and update users, connections, and tool grants as the customer’s requirements change.

Use the maintained MCP client setup guide for current client requirements. Microsoft partners can also follow the Microsoft Copilot Studio MCP setup guide.

How can an MSP package and price MCP?

Stackyapper bills each managed customer workspace to the account that manages it. The managing business decides whether to include it in a managed-service bundle, pass it through as a line item, or absorb it, subject to its Stackyapper agreement and its own customer contract.

Your number of active customer workspaces determines one per-workspace rate, applied to all of them for that billing period.

Example: Five active customer workspaces cost $699 per month, plus the managing account's Standard ($99) or Business ($199) plan. There is no customer-workspace minimum or maximum.

Every managed customer workspace includes unlimited customer users; separate apps, connections, permissions, sessions, and audit scope; managed SAML and SCIM; automated identity lifecycle; and a custom access domain.

Prices are USD and billed month to month. See current Stackyapper pricing and the machine-readable pricing file. Provider subscriptions and provider API charges are not included.

What is the MSP responsible for?

• Confirming the applicable agreement permits its planned resale or managed-service model.
• Choosing the correct customer workspace before connecting an app or granting a tool.
• Obtaining customer authorization for provider connections and workplace monitoring.
• Designing least-privilege access for each customer role and reviewing higher-impact actions.
• Supporting the AI client and workflow the MSP chooses to include in its service.

Stackyapper is the access and policy layer, not the AI assistant and not a substitute for the MSP's customer agreement. Review the trust center, terms, and MCP security checklist for MSPs before launch.

Managed customer MCP questions