Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ALLOWED_WORKSPACESNoComma-separated list of workspace IDs to restrict write operations to (optional)
ANTHROPIC_ADMIN_KEYYesYour Anthropic Admin API key (required, get from console.anthropic.com → Settings → Admin Keys)

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_org_infoA

Get information about the current Anthropic organization.

Returns the organization's ID, name, and type. Useful as a smoke test that the Admin API key is configured correctly.

list_membersA

List organization members.

Returns up to limit members per call. For pagination, pass the last user_id from a previous response as after_id. Member objects include id, email, name, role (user / developer / billing / admin / claude_code_user), and timestamps.

list_invitesB

List pending and historical organization invites.

Invites expire after 21 days. Each invite includes the invited email, the role offered, status (pending / accepted / expired / deleted), and timestamps.

list_workspacesA

List workspaces in the organization.

Workspaces partition API keys, members, and billing. Every org has a Default Workspace that doesn't appear in this list. Max 100 active workspaces per org; archived workspaces don't count against the limit.

get_workspaceA

Get a single workspace by ID.

Returns name, display_color, created_at, archived_at (if archived), and type. Useful for resolving a workspace ID into its display name before referring to it in subsequent operations.

list_workspace_membersA

List members of a specific workspace.

Each entry includes the user_id and their workspace_role (workspace_admin / workspace_developer / workspace_user / workspace_billing). Org admins automatically have workspace_admin on every workspace and may not appear here explicitly.

list_api_keysB

List API keys in the organization.

Returns metadata only — the actual key values are never returned by the Admin API and cannot be retrieved after creation. Each entry includes id, name, status, workspace_id, partial_key_hint (last 4 chars), and created_by_user_id.

get_usage_reportA

Get detailed token usage from the Messages API.

Returns input/output/cache token counts and request counts, bucketed by the requested time window and grouped by the requested dimensions. Use this for questions like 'how many Opus tokens did workspace X burn yesterday' or 'show daily request volume for the last week grouped by model'. Data appears within ~5 minutes of API calls.

get_cost_reportA

Get dollar-amount cost data for the organization.

Returns costs in US dollars (already converted from the API's native cents representation by the client wrapper) broken down by operation description (input tokens, output tokens, cache writes /reads, code execution, web search, etc.) and optionally by workspace. Use for questions like 'what did we spend last week' or 'which workspace cost the most this month'. Priority Tier costs are NOT included here — track those via usage.

get_claude_code_usageA

Get usage data specific to Claude Code workspaces.

Returns daily aggregated user activity, tool usage statistics, and token consumption for Claude Code sessions. This is separate from the general usage report and only covers Claude Code workspace activity. Bedrock-routed Claude Code is not included.

invite_memberA

Invite a new member to the organization.

Sends an invitation email. The invitation expires in 21 days and cannot be modified once created — only cancelled and re-issued. Cannot grant the 'admin' role; admins must be promoted via Console.

delete_inviteA

Cancel a pending invite.

Once deleted, the invite link will no longer work. The invitee will not be notified. Re-inviting requires a new invite call.

update_member_roleA

Change an existing member's organization role.

Cannot promote to or demote from 'admin' — those changes happen only in the Console. Changing roles takes effect immediately and may impact what API keys and workspaces the user can access.

remove_memberA

Remove a member from the organization.

The user loses access to all workspaces immediately. API keys created by them remain active (keys are org-scoped, not user-scoped). Cannot remove members with the 'admin' role — that must be done through the Console.

create_workspaceA

Create a new workspace.

Workspaces partition API keys, members, and limits. Max 100 active workspaces per organization. Creating a workspace does not add any members or keys to it automatically.

update_workspaceA

Rename or recolor a workspace.

Cosmetic only — does not affect billing, access, or API keys. At least one of name or display_color must be provided.

archive_workspaceA

Archive a workspace.

Archived workspaces are hidden from default listings but their data (usage history, costs) is preserved. API keys in the workspace become inactive. Per Anthropic docs this state is reversible through the Console.

add_workspace_memberA

Grant a user access to a workspace.

Org admins and org billing members get automatic workspace roles and don't need to be added explicitly. workspace_billing is inherited from org-level billing role and cannot be assigned here.

update_workspace_member_roleA

Change a member's role within a workspace.

Effective immediately. Does not affect their org-level role or access to other workspaces.

remove_workspace_memberA

Remove a member from a workspace.

They lose access to API keys scoped to this workspace. Their org-level role and access to other workspaces are unaffected. Org admins cannot be removed from workspaces — their role is automatic and inherited.

update_api_keyA

Rename or deactivate an API key.

Renaming is cosmetic and does not require confirmation in itself, but the tool still respects the global confirm flag. Setting status='inactive' immediately stops the key from authenticating new requests — any running workloads using it will start failing. This server cannot reactivate keys; that must be done in the Console.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Trushtonfactory/anthropic-admin-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server