Scopable MCP: Connect Claude to Your Workspace

Scopable's public MCP connector lets Claude read data from a workspace you approve. Use it to prepare client meetings, review your pipeline, or summarize service and compliance records without exporting them first.

MCP stands for Model Context Protocol. It gives an assistant tools for requesting data from a connected service. The Scopable public connector is read-only. It cannot create, update, or delete workspace records, send messages, or make payments.

Server URL

Use this URL when adding the connector:

https://api.scopable.io/mcp/public

The server URL is the connection endpoint. This page is the setup and usage documentation. All users connect to the same server URL, then authorize their own workspace.

The separate /mcp endpoint has a broader tool catalog. Use /mcp/public for the read-only connector described here.

Connect in Claude

1. Open Customize > Connectors in Claude.
2. Select Add > Custom > Web.
3. Name the connector Scopable and enter the server URL above. Select Continue.
4. Keep the detected OAuth authentication settings and continue. Choose Sign in now and set OAuth client to Register automatically.
5. Leave Request headers empty. Select Add to start the connection.
6. Sign in to Scopable in the authorization window. Select the workspace you want Claude to access, review the connection request, and approve it.
7. Return to Claude and confirm that Scopable is connected.

Scopable uses OAuth with automatic client registration. You do not need to generate an API key, paste a token into a chat, or supply a client secret. Enter your Scopable password only on the Scopable sign-in page.

Claude's controls can differ by product and organization policy. See Claude's connector setup instructions if your menu differs or your organization restricts connectors.

Check the connection

Start a new conversation with Scopable available as a connector. Ask:

Use Scopable to list up to five clients in my connected workspace. Show their names and IDs.

Review Claude's tool activity to confirm that it used Scopable. Compare a returned client with its record in the app. An empty result means no matching records were returned. It does not confirm that your workspace has been fully searched.

What you can read

The public catalog includes 50 read-only tools. Your connection may expose fewer tools because Scopable filters them by your current permissions.

Integration-dependent tools require the relevant integration to be connected in Scopable and the client to be mapped where applicable. Connecting Claude does not connect Microsoft 365, Azure, a PSA, or a distributor on your behalf.

The public connector does not expose every Scopable feature. For example, it can read an existing quote but cannot create one or change its status.

Example prompts

Replace the example client name and dates with your own. Ask Claude to use Scopable explicitly and to report missing data.

Prepare a client meeting

Use Scopable to find Acme and prepare a client meeting brief. Include contacts, agreements, open service issues, assessment findings, and available QBR history. Identify missing data and include record IDs so I can check the sources.

Review sales pipeline

Use Scopable to review opportunities expected to close this month. Show value, stage, client, and any linked quote. Separate records you retrieved from your recommendations, and tell me if the results are incomplete.

Review a quote

Use Scopable to retrieve quote [quote ID]. Summarize its line items and payment terms, and identify questions I should check in the app before sending it.

Review security and licensing

Use Scopable to summarize Acme's Microsoft 365 MFA coverage, license usage, Secure Score, and Defender alerts. Include available sync timestamps and say which data could not be retrieved.

Review compliance and Azure costs

Use Scopable to summarize Acme's compliance gaps and Azure costs. Show the period and source for each result, and separate recorded recommendations from your own suggestions.

Claude's answer is a summary of the retrieved records. Check the underlying records before making a client commitment or acting on a recommendation.

Permissions and workspace access

You approve one workspace per connection. Scopable checks your active membership, workspace eligibility, and current permissions when you use the connector. A connection does not give Claude administrator access or permission to read other workspaces.

If a tool is missing, your account may not have permission to use that part of Scopable. Ask your workspace administrator to review your access rather than sharing someone else's credentials.

To work in a different workspace, reconnect and approve that workspace. Changing the workspace you are viewing in the Scopable app does not change an existing connection's authorization.

Data freshness and completeness

Some reads use Scopable records, while integration-dependent reads can use synced or provider data. A successful result does not mean every source was refreshed at the moment you asked. Check any source, reporting period, sync status, or timestamp returned by the tool.

Searches and lists can return only a page of results. For a complete review, ask Claude to continue through available pages and filters, state the period covered, and identify any limits. Do not treat a limited search as a workspace-wide total.

An unavailable integration or failed tool call is not evidence of zero alerts, zero costs, or no compliance gaps. Ask Claude to keep unavailable data separate from empty results.

Disconnect or revoke access

To revoke the connection in Scopable:

1. Sign in to the workspace you approved.
2. Open Settings > MCP and find Connected apps.
3. Check the app name and redirect host to identify your Claude connection.
4. Select Disconnect, then confirm Disconnect app.

Scopable refuses that connection's next request. Reconnecting requires a new approval. If the MCP settings page is unavailable in your workspace, use the support contact at the bottom of this page.

You can also remove the connector from Customize > Connectors in Claude. Revoking Scopable access prevents further reads. It does not remove data already returned in a Claude conversation. Manage that conversation under Claude's data controls.

Troubleshooting

If a tool returns an error with a request ID, include that ID, the tool name, and the time of the failure when contacting support. Use the support contact at the bottom of this page. Do not send passwords, access tokens, or client secrets.

Privacy and data handling

When Claude calls a Scopable tool, the returned workspace data becomes available to Claude for that conversation. It can include client information and other records you are permitted to read. Review your organization's rules before using client data in an assistant.

Scopable's handling of data is described in its Privacy Policy. Data received by Claude is also subject to your Claude account's terms, settings, and Anthropic's Privacy Policy.

Other MCP clients

Use the same public server URL in a remote MCP client that supports Streamable HTTP, OAuth discovery, automatic client registration, and PKCE with S256. The client must complete Scopable sign-in and workspace approval.

Scopable publishes protected-resource metadata at:

https://api.scopable.io/.well-known/oauth-protected-resource/mcp/public

An unauthenticated protocol request receives HTTP 401 with OAuth discovery information. That is the expected sign-in challenge. It is not a documentation page or a connection failure by itself.