MCP
MCP lets an AI client use Alma’s tools directly — ask Claude Desktop about an account and it can read your Memory; ask it to file something and it can, if allowed.
Connect
Your workspace’s server URL:
https://mcp.alma.team/mcp?organization_id={your-org-id}Copy it from the Console — it includes your real organization ID.
Auth
No API key required. On first connect, your client opens a browser to sign in to Alma, and tokens refresh automatically after that.
Because it’s OAuth, an MCP client acts as you and inherits your access. Two people connecting the same workspace get different tools, correctly.
Client setup
Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"alma": {
"url": "https://mcp.alma.team/mcp",
"type": "http",
"headers": { "X-Organization-Id": "your-org-id" }
}
}
}Multiple workspaces
The organization ID picks the workspace. To connect a different one, switch workspaces in the Console and copy the URL again.
The organization ID isn’t a credential — it’s a selector, honored only after confirming you’re actually a member of that workspace. If you belong to exactly one workspace, Alma resolves it without the header.
Permissions
This isn’t an MCP-specific permission screen — it’s the same workspace-wide tool-access ruleset shown on a connection’s Access tab, grouped by toolkit. Editing it here changes what workflows and chat can do too. Admins and implementors only.
Usage
Every tool call made by an external MCP client — who called what, when, and how it resolved. Filter by tool or by person.
Usage here is filtered to MCP clients. For everything Alma does through a connection across all channels, use a connection’s Log.
Admins and implementors only.