MCP Getting Started

Before you start

You need an Almena account, an active MCP-enabled subscription, membership of a workspace and a compatible MCP client. Workspace administrators control subscription and token access.

1. Create your account

1. Select Sign up on the Almena website.
2. Enter your business email, name, organisation and password, then accept the applicable terms and privacy notice.
3. Verify your email using the one-time link. If invited to an existing workspace, accept the invitation after verification.
4. Create a workspace only if your organisation does not already have one.

2. Choose and activate a subscription

1. Open Workspace settings, then Subscription.
2. Select a plan that includes Almena Analytics MCP access. The plan page shows included analytics, usage limits, billing period and commercial terms.
3. Enter the billing and legal-entity details requested at checkout and confirm the subscription.
4. Wait until the workspace shows Active. Enterprise plans may require contract approval before activation.

3. Generate your first token

1. Open Workspace settings, then Developer access, then MCP.
2. Select Create token.
3. Give it a recognisable name such as "Luna, Claude desktop".
4. Select the minimum available scope needed for the client and confirm creation.
5. Copy the token immediately and store it in a password manager or approved secrets store. The full token is shown only once.

4. Copy the customer MCP URL

On the same MCP settings page, copy the Almena Analytics MCP URL. Use only the URL displayed for your workspace and environment.

5. Configure your MCP client

Use the client's secure secret or environment-variable facility where available. The exact labels differ by client, but the connection has two inputs: the MCP URL and an Authorization bearer header carrying the workspace token.

{
  "mcpServers": {
    "almena": {
      "url": "<PUBLIC_ANALYTICS_MCP_URL>",
      "headers": {
        "Authorization": "Bearer <WORKSPACE_TOKEN>"
      }
    }
  }
}

6. Verify the first connection

1. Restart or reconnect the MCP client.
2. Confirm that Almena appears as connected and that the client displays the tools available to your plan.
3. Run a small metadata or catalogue request before requesting a large date range.
4. Check that the response identifies the tool and methodology versions, status, coverage and limitations.
5. If no tools appear, confirm that the subscription is active, the token belongs to the correct workspace and the client is using the customer MCP URL.

Token lifecycle

• Rotate: create a replacement, update the client, verify it, then revoke the old token.
• Revoke: use the token list in workspace settings when a user leaves, a device is retired or exposure is suspected.
• Review: workspace administrators should periodically review active tokens and remove unused credentials.
• Support: email contact@launch4.io with the token name and error time, never the token value.