Getting Started

Connect supported AI assistants and automation tools to Cumulus through the Model Context Protocol (MCP).

This guide covers prerequisites, API credentials, host configuration, authentication, example requests, and troubleshooting.

Quick links: Get started · Troubleshoot

What is the Cumulus MCP Server?

The Sherweb Cumulus MCP Server lets supported AI assistants and automation tools access Cumulus data through MCP. Depending on your account permissions, you can ask about organizations, subscriptions, the product catalog, billing, audit logs, and renewal details.

Your MCP host discovers the tools available to your account. The host and selected AI model influence how requests are interpreted and how answers are presented. Verify important decisions and results in Cumulus.

Before you begin

Protect your credentials: Treat your Client Secret and access tokens like passwords. Do not include them in support tickets, screenshots, recordings, or chat messages.

Create an API credential

  1. Sign in to Cumulus and open Security > APIs.
  2. Create an API credential or select an existing one.
  3. Record the Client ID and store the Client Secret securely.
  4. For interactive sign-in, register the redirect URI required by your MCP host. The host usually provides this URI during setup.

For screenshots and the Cumulus-specific walkthrough, see the Sherweb setup article.

Configure your MCP host

The server is available at https://mcp.sherweb.com. Host setup varies, so follow the instructions for your chosen application and confirm its required redirect URI and authentication options.

Host application Best for
Microsoft Copilot Studio Low-code or no-code agent building
VS Code with GitHub Copilot Developers and technical users
Cursor Developers and AI-first IDE users
Claude Desktop or Claude Code General assistant and developer scenarios

Other MCP-compatible hosts may work. Refer to the host’s documentation for its current remote MCP and OAuth setup.

VS Code and Cursor

Add the remote HTTP server to your MCP configuration, for example in .vscode/mcp.json:

{
  "servers": {
    "sherweb-cumulus": {
      "type": "http",
      "url": "https://mcp.sherweb.com"
    }
  }
}

When prompted, complete authentication with your Cumulus API credentials. Register the redirect URI requested by the host in Cumulus > Security > APIs before starting interactive sign-in. See the VS Code MCP documentation for host-specific configuration details.

Microsoft Copilot Studio

  1. Open your agent and go to Tools > Add a tool > Add a new MCP.
  2. Enter a server name and description of your choice.
  3. Set the server URL to https://mcp.sherweb.com.
  4. Choose OAuth 2.0 with manual configuration.
  5. Enter the Client ID and Client Secret from your Cumulus API credential.
  6. Configure the OAuth endpoints and scopes below.
  7. After creating the connection, register the redirect URI generated by Copilot Studio for that credential in Cumulus.
  8. Authenticate and confirm the agent can discover its available tools.
Setting Value
Authorization URL https://cumulus.sherweb.com/oidc/connect/authorize
Token URL https://cumulus.sherweb.com/oidc/connect/token
Refresh URL https://cumulus.sherweb.com/oidc/connect/token
Scopes openid offline_access mcp:tools service-provider
Redirect URI The URI generated by Copilot Studio for this connection

Keep the redirect URI registered in Cumulus identical to the one generated by Copilot Studio. For screenshots, see the Sherweb setup article.

Claude Desktop and Claude Code

Configure a remote MCP server at https://mcp.sherweb.com using the host’s current MCP configuration instructions. Complete the OAuth sign-in when prompted and register the redirect URI required by the host in Cumulus. The exact configuration differs between Claude Desktop and Claude Code versions; consult the Claude Code MCP documentation or the Claude Desktop documentation for the application you use.

Authenticate

Choose the flow that matches your scenario. Your MCP host guides you through sign-in or credential entry.

Authentication flow Use it for What to expect
Authorization Code with OIDC Interactive user sessions A browser opens so you can sign in through Cumulus. The host’s redirect URI must be registered.
Client Credentials Automation or machine-to-machine workflows The application authenticates with its Client ID and Client Secret. A redirect URI is not needed.

After authentication, refresh or reconnect the host if needed. Confirm that it discovers the Cumulus tools available to your account.

Try your first requests

Start with a focused, read-only question. Include an organization, date range, product, or other relevant filter.

If an answer is too broad or incomplete, narrow the request with an organization, subscription, product, status, or date range. For long lists, ask for a smaller result or the next page. Verify important information in Cumulus.

Available Cumulus areas

Area Examples
Organizations Organization details and portfolio information
Subscriptions Details, quantities, status, and renewal dates
Catalog Products, offers, pricing, and billing schedules
Billing Charges, invoice information, and cost analysis
Audit logs Subscription changes and related history
Schema Available data model and fields

Use actions safely

Some tools may perform actions in Cumulus. An action is available only when supported by the tool and permitted by your assigned permissions and authorization controls.

Troubleshooting

Issue What to try
Sign-in or authentication fails Confirm the authentication flow, Client ID, host configuration, and registered redirect URI for interactive sign-in. Never share your Client Secret or token.
Tools are not available Confirm the server URL is https://mcp.sherweb.com, authentication completed, and your account has the required permissions. Refresh or reconnect the host.
The answer is incomplete Add filters, narrow the date range, or request a smaller result. Verify important information in Cumulus.
The answer appears inaccurate Compare it with Cumulus. Try a clearer request, and contact Sherweb if the underlying data differs.
An action fails or has an uncertain result Do not immediately retry. Verify the final state in Cumulus and contact Sherweb with the action details and time.
Your host is not listed Refer to the host’s MCP documentation. If you need help, provide the host name, version, configuration, and error details.

Get help

Use your normal Sherweb support channel. Include details that help the team investigate:

Before sharing diagnostics, remove Client Secrets, passwords, access tokens, authorization headers, and other sensitive values from screenshots, logs, configuration files, and recordings.