Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ARCA_API_KEYYesYour Arca API key

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_workspacesA

List all workspaces the API key owner belongs to, ordered alphabetically by name. IMPORTANT: Use this tool first when users provide workspace names instead of IDs - find the workspace ID from the results, then use it in subsequent calls to other tools (e.g., list_tasks, create_task).

get_workspaceA

Get details of a specific workspace by ID

list_membersA

List all members of a workspace. Returns member IDs, names, roles, and avatars. Use this to resolve member names to IDs before assigning users to tasks.

list_tasksA

List all tasks in a workspace, optionally filtered by list. Returns task titles with IDs - useful for finding task_id when users provide task names. Each task includes a custom_fields array with all custom field values for that task. Can be used to search for tasks by filtering results in-memory by title/description.

get_taskA

Get full details of a specific task by ID, including its custom_fields array with all custom field values.

create_taskA

Create a new task in a list. The list_id is required and determines the workspace automatically. If user provides list name instead of ID, first call list_lists to resolve it. For better context, consider calling list_statuses to get available status options before creating. To assign users, call list_members first to get user IDs, then pass them in assignee_ids. To set custom field values, call list_custom_fields first to get field IDs, then pass them in custom_fields.

update_taskA

Update an existing task. Supports updating custom field values via the custom_fields parameter — use list_custom_fields to get field IDs first.

delete_taskB

Delete a task by ID

list_listsA

List all lists in a workspace, optionally filtered by folder

create_listB

Create a new list in a workspace

update_listC

Update an existing list

delete_listC

Delete a list by ID

list_foldersB

List all folders in a workspace

create_folderA

Create a new folder in a workspace

update_folderC

Update an existing folder

delete_folderA

Delete a folder by ID

list_commentsB

List all comments on a task

create_commentA

Create a comment on a task

list_statusesA

List all statuses in a workspace, ordered by position

create_statusA

Create a new status in a workspace (requires owner or admin role)

update_statusA

Update an existing status (requires owner or admin role)

delete_statusA

Delete a status by ID (requires owner or admin role). If tasks use this status, provide reassign_to.

list_labelsB

List all labels in a workspace, ordered alphabetically

create_labelB

Create a new label in a workspace

update_labelA

Update an existing label (requires owner or admin role)

delete_labelA

Delete a label by ID (requires owner or admin role)

list_custom_fieldsA

List all custom fields defined in a workspace. Returns each field's ID, name, type, config, position, and list/folder scope (is_scope_restricted, granted_folder_ids, list_overrides). Task responses only include fields that apply to the task's list. Use field IDs when setting custom_fields values in create_task or update_task.

Prompts

Interactive templates invoked by user choice

NameDescription
server_instructionsInstructions for using the Arca MCP server effectively

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 27 tools

Disambiguation5/5

Every tool clearly maps to a single resource and action (e.g., list_tasks vs. get_task, create_status vs. update_status), so there is little chance of selecting the wrong tool. Descriptions also clarify workspace-vs-list-vs-task scope when needed.

Naming Consistency5/5

All 27 tools use a consistent snake_case verb_noun pattern: list/create/update/delete plus resource name. The verbs and noun order are uniform, making the tool set predictable and easy to navigate.

Tool Count2/5

At 27 tools, the server exceeds the 25+ threshold for a large tool set. While the domain spans many related entities, the count feels heavy for an MCP surface and could benefit from consolidation or pruning.

Completeness4/5

The server provides strong CRUD coverage for folders, lists, tasks, statuses, and labels, plus read access for workspaces, members, and custom fields. Minor gaps exist: comments lack update/delete operations and custom fields cannot be created or modified through the server.

Maintenance

ActivityInactive
ResponsivenessNo issues