Contextium Io MCP server

Read from the package source without running it. The installed server may list more.

• access_request

  Request access to a private library or workflow you cannot see, or — as the resource owner — list, approve, or deny pending requests. Use action="request" when a loaded workflow reports a locked library (see its requestAccess affordance). This works from the terminal — the user does not need to open the web app.

• add_comment

  Add a comment to a file, or reply to an existing comment (pass parentCommentId). Authored as the connected user. Optionally anchor to a line with lineNumber. Replying to an external (guest) commenter also emails them.

• add_phase

  Add a phase (work item) to a workflow's project plan. Phases are appended at the end of the existing list. If the workflow has no project plan yet, one is created automatically.

• add_skill_to_agent

  Add a skill to an agent, giving the agent access to that skill's knowledge and capabilities.

• add_task

  Add a task — autonomous by default. Just pass a title and the server will (a) auto-ROUTE the task to the workflow it best fits (matched from the task text against workflow names/descriptions), falling back to the workspace's "General" workflow when no workflow clearly relates, and (b) auto-ASSIGN it to the right team member(s) by role/default. Every task belongs to a workflow — there is no workspa

• auto_project_setup

  Autonomous one-shot project setup — creates a full Contextium workspace (library, agents, workflow, project-state.md) without asking any questions. Use when the user says "just set it up", "create a project for X", or is on mobile/voice.

• auto_research_setup

  Autonomous one-shot research workspace setup — creates a research library, agents, and workflow without asking any questions. Use when the user says "deep dive into X", "research X for me", or is on mobile/voice.

• break_down_task

  Use AI to break a broad task into 3-6 concrete, actionable subtasks. Claude analyses the task title and workflow context, then creates the subtasks automatically. Use when a task is too broad to complete in one step.

• capture_idea

  Capture a quick note or seed to remember later — saves into an existing project's seeds or a general Quick Notes library. Use ONLY for lightweight "remember this" notes: when the user says "remember this", "note that", "jot this down", or "add this to [project]". Do NOT use this for a brand-new business, product, app, SaaS, or venture idea ("I have an idea for…", "I want to start a business that…"

• contextium_help

  Show all available Contextium capabilities and how to use them. Call this when the user asks: "what can Contextium do", "help with Contextium", "how do I use Contextium", "what Contextium tools are available", "show me what I can do with Contextium".

• contextium_status

  Show a Contextium workspace health dashboard — available workspaces, libraries, agents, skills, and workflows. Call this when the user asks: "check Contextium status", "what workspace am I in", "what resources do I have in Contextium", "show my Contextium setup", "what libraries do I have".

• createwrite action

  Create a new resource in a workspace. Set `type` to what you're creating: "file" (needs libraryId + title + complete content), "library" (a context library — needs name), or "agent" / "skill" / "workflow" (need name; a workflow can bundle projectIds, agentIds, skillIds, and tagIds). Always provide full, real content for files — never empty or placeholder. File linking: to link to another file in t

• create_agentwrite action

  Create a new agent in the workspace. WHAT IS AN AGENT: An agent is a specialised AI assistant with a defined role, persona, and behavioural instructions. Agents are where you put "You are a..." system prompts, persona definitions, tone of voice rules, and task-specific instructions. Agents can have skills attached to them to give them access to reference knowledge. EXAMPLES of correct agent conten

• create_context_librarywrite action

  Create a new Context Library in the workspace. Use this to organize documentation into separate libraries.

• create_filewrite action

  Create a new file in a Contextium Context Library. IMPORTANT: You MUST generate and provide the full file content before calling this tool. Never call this with empty or placeholder content — write the complete content first, then call this tool with it. Empty content will be rejected. OKF (Open Knowledge Format): All files MUST include YAML frontmatter at the top with at minimum `type` and `title

• create_identitywrite action

  Creates a new identity in the workspace. Identities capture voice, tone, role, and audience context so AI produces work from the right perspective.

• create_planwrite action

  Create a phase plan for a workflow. A workflow can have at most one plan. Returns the new plan ID to use with add_phase. This is an alias of create_project.

• create_projectwrite action

  Create a phase plan for a workflow (despite the name, this does NOT create a context library — it creates the project plan that holds phases). A workflow can have at most one plan. Returns the new plan ID to use with add_phase. Alias: create_plan.

• create_resourcewrite action

  Interactively create an agent, skill, or workflow in the current Contextium workspace. Call this when the user says things like: "create an agent", "make a new agent", "create a skill", "build a workflow", "I need a skill for X", "set up an agent that does X", "make an agent that can do X".

• create_skillwrite action

  Create a new skill in the workspace. WHAT IS A SKILL: A skill is a reusable block of KNOWLEDGE, REFERENCE MATERIAL, or DOMAIN EXPERTISE that agents can draw on — things like company policies, style guides, technical documentation, process steps, or domain facts. Skills are NOT agents. Skills do NOT contain persona definitions, "You are a..." instructions, or behavioural rules. If you are defining

• create_workflowwrite action

  Create a new workflow in the workspace. Workflows bundle agents, skills, tags, and context libraries together for a specific task.

• deletewrite action

  Delete a resource (moves to trash, restorable). type: file | skill | workflow

• delete_agentwrite action

  Permanently delete an agent from the workspace. This cannot be undone. System agents (harness agents) cannot be deleted.

• delete_done_phaseswrite action

  Bulk delete all phases marked as done from a workflow's project plan. Use this to clean up completed work. Returns the number of phases deleted.

• delete_filewrite action

  Delete a file from Contextium (moves to trash, not permanent). The file can be restored later if needed. Requires write access to the file.

• delete_identitywrite action

  Permanently deletes an identity by ID. Use dryRun=true first to preview which workflows will have their identity_id set to null.

• delete_librarywrite action

  Delete a context library (moves to trash, recoverable within 30 days). Requires owner or admin role.

• delete_phasewrite action

  Delete a single phase from a project plan by its phase ID. Use this to remove a specific work item. To bulk-remove completed work, use delete_done_phases instead.

• dismiss_broadcast

  Dismiss a broadcast notification so it no longer appears in the inbox.

• dispatch_agent_job

  Dispatch an AI agent runner job with a natural-language intent. The runner autonomously selects the right agent, plans actions, and executes them. Returns a job ID you can poll with get_agent_job.

• edit_phasewrite action

  Update the title or description of an existing phase without changing its status or position. Use this to reword or clarify a phase.

• figma_sync

  Manage Figma connector integrations — list connected files or trigger a sync to pull design tokens, components, and page structure into your Contextium libraries.

• get

  Get full details of a resource by ID. Use workspace_activity for recent activity logs. Use activity_archive to read a specific month's archived logs by YYYY-MM (e.g. 2025-02). Use list_activity_archives to see which months have archives. Use workflow_activity for the activity digest since a workflow's last session. Use entity_activity for recent activity on a specific file or entity.

• get_agent

  Get detailed information about a specific agent including system prompt, persona, configuration, and associated files. Returns complete agent context for use in LLM workflows.

• get_agent_job

  Get the status and result of a specific agent runner job. Poll this after dispatch_agent_job to check completion.

• get_context_library

  Get detailed information about a specific context library (project) including metadata, file structure, and statistics. Context libraries are collections of documentation and knowledge files.

• get_file

  Get the complete content and metadata of a specific documentation file by its ID. Requires read access to the file's workspace. Whenever a user asks to open, show, view, or read a file, set includeLinks=true BY DEFAULT — it returns the file's outgoing // links resolved to titles. Then present the file and, if it has any links, add a one-line footer telling the user how many files it links to and l

• get_identity

  Gets the full profile of a single identity by ID, including voice descriptors, writing samples, and all contextual fields.

• get_marketplace_listing

  Get full details about a specific marketplace listing by its slug, including description, configuration options, version history, and ratings.

• get_notifications

  Get the notification inbox for the current user — both activity notifications and broadcasts.

• get_project

  Get the project plan attached to a workflow, including all its phases (open and completed). Returns phase titles, statuses, assigned agents, and sort order. Use this to understand what work is planned or in progress for a workflow.

• get_skill

  Get a skill by its file ID, including full markdown content. Use list_skills to find skill IDs.

• get_unread_count

  Get the total number of unread notifications (activity + broadcasts) for the current user.

• get_workflow

  Get detailed information about a specific workflow including name, description, associated agents, tags, and metadata. Use load_workflow to get the complete workflow context with all resources (agents, skills, files).

• idea_kickoff

  Autonomous business-idea kickoff. Call this FIRST and IMMEDIATELY whenever a user voices a brand-new business, product, app, SaaS, startup, or venture idea — e.g. "I have an idea for…", "I have a business idea", "I want to start a business that…", "I want to build a product that…", "what if there was an app that…", "here's a business idea", "idea: …". Returns instructions to run a FULL business an

• install_marketplace_listing

  Install (import) a marketplace skill or agent into a workspace. This copies the listing content into the user's workspace so they can use it immediately.

• list

  List all resources of a given type in a workspace — the fast way to see what already exists before you act. Returns lightweight summaries (IDs, names, key fields), not full content: use `get` for one resource's full detail, or `search` to find resources by text or tag. Set `type` to choose what to list — workspaces, libraries (context libraries), agents, skills, files (pass libraryId), workflows,

• list_agent_jobs

  List recent agent runner jobs for the workspace — shows status (pending, running, done, failed), intent, and result summary.

• list_agents

  Lists all agents (AI assistant configurations) in a workspace. Agents define assistant roles and capabilities.

• list_comments

  List the comments on a file — open (unresolved) threads by default. Comments are feedback to act on: each shows the author (members and external share-link guests), the anchored line number if any, and the comment id needed by resolve_comment / add_comment replies.

• list_context_libraries

  Lists all Context Libraries in a workspace with file counts. Use this to see what context libraries you have before listing files.

• list_files

  Lists files in a Context Library or folder (names and metadata only, no content). Use get_file to retrieve specific file content.

• list_identities

  Lists identities visible to the current user in a workspace. Identities capture voice, tone, role, and audience context so AI produces work from the right perspective.

• list_lessons

  Read lessons learned previously recorded in this workspace — including ones captured while working on OTHER projects. Call this before starting new work, when debugging something that smells familiar, or when the user asks what has been learned before. Optionally filter by project.

• list_phases

  List all phases for a workflow's project plan, ordered by sort_order. Returns each phase with its ID, title, status (pending/in_progress/done/blocked), assigned agent name, and creation date. Use the phase IDs with update_phase_status to progress work.

• list_skills

  Lists all skills (shared knowledge and best practices) in a workspace. Skills contain reusable documentation for AI agents.

• list_tags

  List all tags in a workspace. Returns a flat list of tags with their IDs and usage counts. Use this to discover available tags before searching or applying them.

• list_tasks

  List tasks. Omit workflowId to list ALL tasks across every workflow in the workspace. Provide workflowId to list a single workflow's tasks instead; these are DB tasks by default, or phase files tagged "task" for legacy file-backed workflows. Returns status, creator, priority, and due dates. Use sparingly — load_workflow already includes active workflow tasks.

• list_trash

  List all context libraries currently in the workspace trash (deleted within the last 30 days, not yet permanently removed).

• list_workflows

  List all workflows in a workspace. Workflows bundle agents, skills, tags, and context libraries together for a specific task. Each workflow includes phaseCount and completedCount showing project progress.

• list_workspaces

  Lists all workspaces you have access to with your role. Each workspace contains projects, agents, skills, tags, and workflows.

• load_workflow

  Load complete workflow context — agents, skills, files, and libraries. Use this to initialise a full workflow session.

• manage_relationship

  Manage relationships: add/remove skills on agents (one at a time, or many in one call with apply_bulk/remove_bulk + skillIds), add/remove inline tags on files, and share/unshare a private workflow with an individual workspace member. For type=tag this EDITS THE FILE CONTENT — it writes (or deletes) a #<value> token in the file body, which is the source of truth for a file's tags; the tag is auto-c

• manual_project_setup

  Guided, interactive project setup — walks the user through creating a Contextium workspace step by step, asking for confirmation at each stage. Use when the user is present and wants to work through the setup together.

• manual_research_setup

  Guided, interactive research workspace setup — walks the user through creating a research workspace step by step. Use when the user is present and wants to steer the research direction.

• mark_notification_read

  Mark one notification as read, or mark all notifications as read when no ID is provided.

• marketplace

  Browse, inspect, and install shared skills, agents, and MCP servers from the Contextium Marketplace. Set `action`: "search" to browse listings (optionally filter by itemType skill/agent/mcp_server, category, or query); "get" for a listing's full details by slug; "install" to add a listing to a workspace by slug. Typically search first to find a slug, then get or install with it.

• new_project

  Start a guided new Contextium project setup. Call this tool FIRST whenever a user wants to set up a new project in Contextium, create libraries/agents/skills for a project, get started with Contextium, or organise their AI context. Returns complete step-by-step setup instructions that you must follow exactly.

• notify_team_members

  Notify all eligible workspace team members about a resource you just created or updated — file, workflow, agent, or library. Use this when the user says things like "notify the team of this new file", "let everyone know about this workflow", or "notify @sarah about this". Respects each member's notification preferences and Do Not Disturb settings. Returns how many members were notified.

• project

  DEPRECATED — phases are now DB-backed. Use list_phases (replaces get_next_phase), update_phase_status(phaseId, "done") (replaces mark_phase_complete), and load_workflow (replaces load_session/close_session).

• record_lesson

  Record a lesson learned — something that went wrong and how it was fixed — into the workspace Lessons Learned library, so the same mistake can be avoided on THIS and any OTHER project. Call this when you hit and resolve a non-obvious bug, a broken assumption, a footgun, or a fix that took real effort to find. Do NOT use it for routine notes or ideas (use capture_idea) or for reusable reference kno

• remove_skill_from_agentwrite action

  Remove a skill from an agent.

• reorder_phases

  Reorder the phases in a workflow's project plan. Provide the full list of phase IDs in the desired order; the plan's sort order is updated to match.

• resolve_comment

  Resolve (acknowledge) a comment thread once it has been addressed — it disappears from default views everywhere (web, desktop, public share page, list_comments). Pass the ROOT comment id; the whole thread resolves. Set resolved=false to reopen.

• restore_library

  Restore a context library from trash. Must be within the 30-day restore window.

• resume_project

  Resume a Contextium project from a session handoff — loads the project plan, finds the last handoff note, and briefs you so you can continue without losing context. Call this when the user says things like: "resume my project", "continue where I left off", "pick up from last session", "what was I working on", "I'm back let's continue", "carry on from yesterday", "what's next in my project".

• search

  Find files in a workspace when you don't know their exact ID. Pick a `mode`: "text" runs a full-text search over file contents and titles; "tags" returns files carrying ALL of the given tagIds (AND logic); "files" matches by partial file name/title. Reach for search before `get` when you only know roughly what you want; use `list` with type=files instead when you just need everything in a library.

• search_by_tags

  Search for files by tag IDs. Returns files that have ALL specified tags (AND logic). Use this to find files organized by specific tags like category:api, status:active, or team:engineering.

• search_marketplace

  Browse and search the Contextium marketplace for published skills and agents. Use this to find community-built skills or agents that match what the user needs, then use install_marketplace_listing to add them to the workspace.

• share_createwrite action

  Create a public share link for a file so someone outside the workspace can view it. Returns the full link ONCE. accessMode "link" = anyone with the link; "restricted" = only allowlisted emails/domains (verified by emailed code). permission "view" or "download".

• share_list

  List the active public share links for a file, with access mode, permission, and view count.

• share_revoke

  Revoke a public share link. The link stops working immediately.

• suggest_libraries

  Suggest existing context libraries that look relevant to a workflow you are about to create, ranked by keyword overlap between the workflow name/description and each library's name/description. Call this BEFORE create_workflow (or create type=workflow) so you can present the matches to the user and let them choose which to attach via projectIds. Nothing is auto-attached — these are suggestions onl

• summarize_done_phases

  Generate an AI summary of all done phases in a workflow's project plan, save it as a context file in the specified library, then delete the source phases. Updates the plan's last_summarized_at timestamp.

• updatewrite action

  Update an existing resource in place by ID — edit a file's title, path, content, or status, or rename/reconfigure an agent, skill, workflow, or project. Only the fields you pass are changed; for files, a new version is created automatically so history is preserved. Set `type` to the resource kind and `id` to its UUID (from list/search/get). File linking (type=file): to link to another file in the

• update_agentwrite action

  Update an existing agent's name, description, custom context, or system prompt.

• update_identitywrite action

  Updates an existing identity by ID. Only the fields you provide are changed.

• update_notification_preferenceswrite action

  Update notification preferences for the current user — per-type toggles, email frequency, or Do Not Disturb.

• update_phase_statuswrite action

  Update the status of a project phase. Valid statuses: pending, in_progress, done, blocked. Use this to progress phases as work is completed. Setting a phase to "done" automatically records the completion time.

• update_skillwrite action

  Update an existing skill — change its title, content, or both. Skills are reusable knowledge modules stored in the Skills Library.

• update_taskwrite action

  Update a task title, description, or status. Works for all task types (DB tasks, phase tasks, file-backed tasks). Omit workflowId to update a task by id regardless of its workflow (the server resolves it). Use this instead of update_task_status when you also need to set a title or description.

• update_task_statuswrite action

  Update the status of a task. Omit workflowId to update a task by id regardless of its workflow (the server resolves it). Updates the DB task record; for legacy file-backed workflows it instead swaps the status tag on the underlying phase file. Use in_progress when starting work, done when complete, dismissed when no longer relevant.

• update_workflowwrite action

  Update an existing workflow. Modify its name, description, or the agents, skills, tags, and libraries it includes. Pass projectConfig to set phaseCount, completedCount, contextLibraryId, and tagIds — required at the end of Planner runs.

• workspace_summary

  Start-of-day overview / morning brief for the current user in a workspace: outstanding tasks assigned to them (overdue, due-soon and a suggested focus), plus unread notifications and @mentions — returned as compact counts, a few highlights, and a ready-to-read `brief` sentence. Call this whenever the user asks, in ANY phrasing, what they need to do or what has happened — e.g. "what needs doing tod

• Code scan163 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancerepository not readable: repo not found3/15
• Maintainer identityno repository or website to verify2/10

Safety score

65/100

higher than 20% of 48,243 servers

Tools

94

the typical server has 7

Tools that change things

31%

typical: 0%. Fewer write tools means less an agent can break

Downloads a week

396

more than 85% of 12,306 servers with a package

Contextium Io: common questions

Is Contextium Io MCP server safe?

With care: it is graded C, so read the findings first (65/100). Read the Contextium Io safety report

How do I install Contextium Io?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Contextium Io need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Contextium Io maintained?

The latest release is v1.10.12.

How does Contextium Io compare with other MCP servers?

safety score 65/100 (higher than 20% of 48,243 servers); tools 94 (the typical server has 7); tools that change things 31% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.