Get Started with Alasco MCP Server BETA

Welcome to the Alasco MCP server! You can use it to integrate your AI agents and workflows with Alasco and supercharge your business processes.

This feature is currently in beta and is subject to change. Please contact us with feedback and questions!

Setup

Before you can use the Alasco MCP server, follow the steps below.

Note: during the beta period, certain limitations apply. These will be expanded in the future.

Prerequisites

  • You need an MCP client. Supported clients are listed here.
  • Your Alasco account needs to be activated for MCP access. Contact our support team to request access.
  • You need to have the role Admin for the Alasco accounts you want to use.

Connect your client

To connect your MCP client, you will receive a client ID and redirect URI.

Then you can authenticate with your Alasco account. The MCP client will then act on your behalf with your access rights and permissions.

Supported Clients

Note: we currently do not support Dynamic Client Registration (DCR). To receive the necessary credentials or register another client, please contact us.

The following clients are known to work with the Alasco MCP server:

  • Claude Code
  • Cursor

Technical Overview

The Alasco MCP server is a thin transport layer in front of the Alasco Public API. It exposes product APIs as Model Context Protocol tools for compatible clients.

  • Starlette + FastMCP ASGI application
  • Auth0 OAuth 2.0 — bearer token validated on each request
  • One tool namespace per product, derived from that product’s Public API OpenAPI specification
  • Permissions from your Alasco roles at session start; tools are filtered per account and user