Scopable
io.scopablePublished by scopable.ioOfficial publisherv1.0.0Updated Oct 24, 2026
Scopable MSP API: clients, quotes, assessments, compliance, QBRs. OAuth 2.1, read-only or read-write
Overview
Scopable connects an AI assistant to the Scopable MSP API for clients, quotes, assessments, compliance and QBRs, with OAuth sign-in and read-only or read-write.
- What you can do
- Work with client records in the Scopable MSP API, including looking up and managing clients and their details, subject to the access level granted at sign-in. Handle quotes, creating and reviewing them through the API. Work with assessments and compliance information. Access QBR material. Access is either read-only or read-write depending on the OAuth scope chosen when connecting.
- When to use it
- Useful for managed service providers already on Scopable who want an assistant to look up or update client, quote, assessment, compliance and QBR records without leaving the conversation. Choose read-only access if the assistant only needs to retrieve information.
- Requirements
- A remote MCP endpoint at mcp.scopable.io reached over streamable HTTP. OAuth authentication is required, and the connection must be granted either read-only or read-write access. No environment variables or headers are declared.
Installation
In SourceWeft
- Open Scopable in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.scopable%2Fscopable/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"scopable": {
"type": "http",
"url": "https://mcp.scopable.io/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestOct 24, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.