Maglis MCP

Connect an AI assistant

Give Claude, Cursor or any MCP client read access to your meetings, so you can ask about decisions, prices and action items in plain English or Arabic.

Last updated: November 21, 2026

Maglis runs a remote Model Context Protocol (MCP) server. Connect your assistant once, then ask things like “What did we agree on pricing in last week's discovery call?” or “List every open action item from this month's meetings.” The assistant searches your workspace and quotes the real transcript.

The server lives at https://www.maglis.ai/mcp and authenticates with a Maglis API key passed as a Bearer token. Access is read-only: an assistant can never change or delete anything.

Before you start

  • Your workspace is on the Enterprise plan. On other plans the API keys section is hidden and the server answers 403 enterprise_required.
  • You are an active member of the workspace. Any member can create keys for themselves.
  • An MCP client that supports remote servers over HTTP: Claude Code, Cursor, VS Code, or any client that speaks Streamable HTTP.

Create an API key

  1. 1
    Open Settings in Maglis
    Sign in at maglis.ai and open Settings.
  2. 2
    Go to Developer → API keys
    The section is called API keys & MCP and also shows your MCP address.
  3. 3
    Name the key
    Use a name that says where it will live, for example Claude Code on my laptop.
  4. 4
    Click Create key
  5. 5
    Copy the key now
    Keys start with mgl_ and are shown only once. Maglis stores only a hash, so a lost key can't be recovered: revoke it and create a new one.
Treat a key like a password. It reads meetings as you, so keep it out of shared repositories and screenshots. Each person can hold up to 10 active keys.

Connect your client

Claude Code

Run this once in your terminal, with your key in place of the placeholder:

Terminal
claude mcp add --transport http maglis https://www.maglis.ai/mcp \
  --header "Authorization: Bearer mgl_YOUR_API_KEY"

Then type /mcp inside Claude Code to confirm maglis shows as connected.

Cursor

Add Maglis to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

mcp.json
{
  "mcpServers": {
    "maglis": {
      "url": "https://www.maglis.ai/mcp",
      "headers": {
        "Authorization": "Bearer mgl_YOUR_API_KEY"
      }
    }
  }
}

VS Code

Add Maglis to .vscode/mcp.json in your workspace, then start the server from the MCP view:

.vscode/mcp.json
{
  "servers": {
    "maglis": {
      "type": "http",
      "url": "https://www.maglis.ai/mcp",
      "headers": {
        "Authorization": "Bearer mgl_YOUR_API_KEY"
      }
    }
  }
}

Other clients

Any client that supports remote MCP servers over Streamable HTTP works. Point it at https://www.maglis.ai/mcp and send the header Authorization: Bearer mgl_…. To check a key from the command line:

Terminal
curl -X POST https://www.maglis.ai/mcp \
  -H "Authorization: Bearer mgl_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Long-lived streams close after about four minutes and clients reconnect on their own. You don't need to do anything.

Try it

Once connected, ask your assistant in English or Arabic:

  • “List my last 10 meetings.”
  • “Find every meeting where we discussed the onboarding timeline.”
  • “Show me the action items from yesterday's call, in Arabic.”
  • “ما الذي اتفقنا عليه بخصوص الأسعار في اجتماع الأسبوع الماضي؟”

See the tools reference for exactly what the assistant can call.

Security and privacy

  • Read-only. No tool can create, change, send or delete anything.
  • Your workspace only. A key reaches the meetings of the workspace it was created in, as the member who created it.
  • Audited. Every time an assistant opens a meeting, document or transcript, it is written to your workspace's audit log.
  • Prompt-injection aware. Meeting content is labelled as data, so instructions spoken in a meeting are not treated as commands to the assistant.
  • Stops when access stops. If a member is removed from the workspace, their keys stop working immediately.

Limits

LimitValue
Requests120 per minute, per key
Active keys10 per person
Transcript pageUp to 100,000 characters per call, with an offset to continue

Errors

StatusMeaning
401 invalid_api_keyThe key is missing, mistyped or revoked, or its owner left the workspace.
403 enterprise_requiredThe workspace is not on the Enterprise plan.
429 rate_limitedMore than 120 requests in a minute. Wait for the number of seconds in the Retry-After header.

Revoke a key

In Settings → Developer → API keys, click Revoke next to the key and confirm. Anything using it stops working straight away, and this can't be undone. Members can revoke their own keys; owners and admins can revoke any key in the workspace.

See also Tools reference.

Questions? © 2026 Maglis