io.github.contextium-io/mcp-server
NPM · @CONTEXTIUM/MCP-SERVER · SCANNED SEP 20
Your team's knowledge, always in context. SOPs, coding standards, and workflows for Claude.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 58 of 143 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 40 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 10643 tokens (~154/item across 69 items; 69 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 69 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.contextium-io/mcp-server server?
io.github.contextium-io/mcp-server runs locally as an npm package, launched with npx -y @contextium/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @contextium/mcp-server
claude mcp add contextium-io-mcp-server -- npx -y @contextium/mcp-server
{
"mcpServers": {
"contextium-io-mcp-server": {
"command": "npx",
"args": [
"-y",
"@contextium/mcp-server"
]
}
}
} {
"servers": {
"contextium-io-mcp-server": {
"command": "npx",
"args": [
"-y",
"@contextium/mcp-server"
]
}
}
} codex mcp add contextium-io-mcp-server -- npx -y @contextium/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"contextium-io-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@contextium/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add contextium-io-mcp-server --command npx --arg -y --arg @contextium/mcp-server
mcp_servers:
contextium-io-mcp-server:
command: "npx"
args: ["-y", "@contextium/mcp-server"] {
"McpServers": {
"contextium-io-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@contextium/mcp-server"
]
}
}
} assistant mcp add contextium-io-mcp-server -t stdio -c npx -a -y @contextium/mcp-server
{
"mcpServers": {
"contextium-io-mcp-server": {
"command": "npx",
"args": [
"-y",
"@contextium/mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −3
- Stability: pass → 0.80 functional
- 10 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 26 −1
- Stability: pass → 0.97 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@contextium/mcp-server@1.10.12
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 143 packages
| Packages resolved | 143 |
|---|---|
| Stale | 58 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
access_request ~242
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | request = ask for access; list = see requests (yours, or a resource's if you own it); approve/deny = resolve a request you own. |
| mine | boolean | – | For action=list: list your own requests instead of a resource's pending requests. |
| reason | string | – | Optional note to the owner (action=request). |
| rejectionReason | string | – | Optional reason shown to the requester (action=deny). |
| requestId | string | – | The access-request ID. Required for action=approve/deny. |
| resourceId | string | – | The library/workflow ID. Required for action=request. |
| resourceType | string | – | Required for action=request (and action=list for a specific resource). |
| workspaceId | string | – | Workspace ID. Defaults to your default workspace. |
No output schema declared.
No examples provided.
add_comment ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Comment text (plain text, max 10000 chars) |
| fileId | string | yes | UUID of the file |
| lineNumber | number | – | Optional 1-based line to anchor the comment to |
| parentCommentId | string | – | Optional comment id to reply to (from list_comments) |
No output schema declared.
No examples provided.
add_phase ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| assignedAgentId | string | – | Optional agent ID to assign this phase to. |
| description | string | – | Optional longer description or acceptance criteria. |
| title | string | yes | Phase title — short, actionable description of the work. |
| workflowId | string | yes | Workflow ID |
| workspaceId | string | – | Workspace ID. Defaults to your configured workspace. |
No output schema declared.
No examples provided.
add_task ~644
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 workspace-level task. The caller does NOT need to choose a workflow or assignee. Provide an explicit workflowId/workflowName and/or assigneeIds ONLY to override that decision (the user has already decided) — explicit values are used verbatim and skip auto-routing/auto-assignment for whatever was specified. Set autoRoute:false to skip AI routing and place the task directly in the "General" workflow. Tasks are stored as DB tasks under the chosen workflow by default; only legacy workflows that still have a file-backed project library store the task as a phase file tagged "task".
| Name | Type | Req | Description |
|---|---|---|---|
| assignedTo | string | – | User ID to assign the task to. Overrides the workflow default assignee when provided. |
| assigneeIds | array | – | User IDs to assign this task to as a SHARED task that any one of them can complete (max 5). Only assign multiple people when the task genuinely needs more than one owner — do not blanket-assign. Pref… |
| autoAssign | boolean | – | When true (the default) and no explicit assignee is given, the task is auto-assigned to the team member(s) whose job role best fits it. Set false to leave it unassigned. |
| autoRoute | boolean | – | When true (the default) and no workflow is given, the task is auto-routed to the best-fit workflow, falling back to the workspace's "General" workflow if none relates. Set false to skip AI routing an… |
| description | string | – | Optional longer description or context for the task. |
| dueDate | string | – | Optional due date — a calendar date "YYYY-MM-DD" or a full ISO 8601 datetime. Once set, the task surfaces in due-soon / overdue nudges. |
| phaseFileId | string | – | Legacy: phase file ID to link this task to, for workflows still using a file-backed project library. New workflows use DB-backed phases (add_phase) and do not need this. |
| priority | string | – | Task priority — high, medium, or low. AI agents should set this based on urgency and importance. |
| title | string | yes | Task title — short, actionable description. |
| workflowId | string | – | Exact workflow ID. Use this when you already know the ID. |
| workflowName | string | – | Workflow name or partial name. Used to look up the workflow when you don't know the ID. If multiple workflows match, candidates are returned so the user can pick. |
| workspaceId | string | – | Workspace ID. Defaults to your configured workspace. |
No output schema declared.
No examples provided.
auto_project_setup ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | What the project is about — used to tailor agent system prompts |
| name | string | yes | Project name |
| workspaceId | string | – | Workspace ID (uses default if omitted) |
No output schema declared.
No examples provided.
auto_research_setup ~131
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.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | string | – | quick: one research agent + summary doc. deep: Research Lead + Fact Checker + structured brief. Defaults to quick. |
| description | string | – | What to research — used to tailor agent system prompts and scope the brief |
| name | string | yes | Research topic name |
| workspaceId | string | – | Workspace ID (uses default if omitted) |
No output schema declared.
No examples provided.
break_down_task ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| taskId | string | yes | ID of the parent task to break down. |
| workflowId | string | yes | Workflow ID that owns the task. |
| workspaceId | string | – | Workspace ID. Defaults to your configured workspace. |
No output schema declared.
No examples provided.
capture_idea ~202
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…", "I want to build…") — those are not quick notes; route them to idea_kickoff, which runs a full business analysis. When unsure between capturing and kicking off a venture idea, prefer idea_kickoff.
| Name | Type | Req | Description |
|---|---|---|---|
| projectName | string | – | Project to attach the idea to — inferred from existing projects if omitted |
| text | string | yes | The idea or note to capture |
| workspaceId | string | – | Workspace ID (uses default if omitted) |
No output schema declared.
No examples provided.
contextium_help ~68
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".
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
contextium_status ~89
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".
| Name | Type | Req | Description |
|---|---|---|---|
| workspaceId | string | – | Workspace ID (uses default if omitted) |
No output schema declared.
No examples provided.
create ~460
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 the SAME workspace, put //<fileId> inline in the content — use the target file's UUID (from search/list/get results), not its title. The link renders as the target's title and is indexed automatically on save; the target gains a backlink with no extra step. Add a link only where the text genuinely references an existing file; never invent //<id> for a file that does not exist (it becomes a dangling link). Use get({ type: "file_links", id }) to inspect a file's links and backlinks.
| Name | Type | Req | Description |
|---|---|---|---|
| agentIds | array | – | Agent IDs (type=workflow) |
| content | string | – | Full file content — must be complete (type=file) |
| description | string | – | Description (type=library, agent, skill, workflow) |
| folderId | string | – | Folder ID (type=file) |
| isPrivate | boolean | – | Workflow visibility (type=workflow). Defaults to true — visible only to you until shared. Set false to share with the whole team. |
| libraryId | string | – | Library ID (type=file) |
| name | string | – | Name (type=library, agent, skill, workflow) |
| path | string | – | File path (type=file) |
| projectIds | array | – | Workflow library IDs (type=workflow) |
| skillIds | array | – | Skill IDs (type=workflow) |
| tagIds | array | – | Workflow tag IDs (type=workflow) |
| title | string | – | Title (type=file) |
| type | string | yes | Resource type to create. (Tags are not created here — a tag exists by adding a #<value> token to a file's content; use manage_relationship type=tag to tag a file.) |
| workspaceId | string | – | – |
No output schema declared.
No examples provided.
create_agent ~475
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 content: - "You are a senior customer support agent for Acme Corp. You handle billing and account queries..." - "You are a code reviewer specialising in Python. You check for security vulnerabilities..." DO NOT use create_agent to store reference material, policies, or documentation — use create_skill for that. IMPORTANT: You MUST always provide both a clear name AND a meaningful description — never leave description blank. The description should explain the agent's role, specialisation, and how it behaves. WORKFLOW ATTACHMENT: Always provide workflowId when creating an agent for a specific project or feature — this ensures the agent is immediately attached to the right workflow and won't be orphaned.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | REQUIRED — A meaningful description of the agent's purpose, role, and behaviour. Explain what this agent specialises in, what tasks it handles, and how it should approach its work. Do NOT leave this… |
| name | string | yes | A clear, descriptive name for the agent (e.g., "Customer Support Agent", "Code Reviewer", "Marketing Copywriter") |
| personaId | string | – | Optional persona ID to base this agent on a built-in persona. Use list_agents or get the persona list to find valid IDs. If provided, systemPrompt is derived from the persona. |
| systemPrompt | string | – | The system prompt defining this agent's behaviour and instructions. Required for custom agents (when no personaId is given). Example: "You are a senior customer support agent. You handle billing quer… |
| workflowId | string | – | Optional workflow ID to attach this agent to immediately after creation. Recommended — avoids orphaned agents. |
| workspaceId | string | – | Workspace ID. If not provided, uses your default workspace. |
No output schema declared.
No examples provided.
create_identity ~244
Creates a new identity in the workspace. Identities capture voice, tone, role, and audience context so AI produces work from the right perspective.
| Name | Type | Req | Description |
|---|---|---|---|
| alwaysDo | string | – | Things to always do. |
| audience | string | – | Intended audience. |
| background | string | – | Background information. |
| brandColors | string | – | Brand colours. |
| brandVisuals | string | – | Visual style description. |
| linkedLibraryIds | array | – | Context library IDs to link. |
| name | string | yes | Identity name (required). |
| neverDo | string | – | Things to never do. |
| recurringTopics | string | – | Recurring topics. |
| roleContext | string | – | Role and context description. |
| scope | string | – | user: personal; workspace: shared. Defaults to user. |
| type | string | – | Identity type. Defaults to person. |
| valuesPriorities | string | – | Values and priorities. |
| voiceDescriptors | string | – | Voice and tone descriptors (e.g. "concise, direct, warm"). |
| workspaceId | string | – | Workspace ID. If not provided, uses your default workspace. |
| writingSamples | string | – | Writing samples. |
No output schema declared.
No examples provided.
create_plan ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional short description of the project. |
| name | string | – | Project plan name (defaults to the workflow name if omitted). |
| spec | string | – | Optional full project spec stored on the plan record. |
| workflowId | string | yes | Workflow ID to attach the plan to. |
| workspaceId | string | – | Workspace ID. Defaults to your configured workspace. |
No output schema declared.
No examples provided.
create_project ~141
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional short description of the project. |
| name | string | – | Project plan name (defaults to the workflow name if omitted). |
| spec | string | – | Optional full project spec stored on the plan record. |
| workflowId | string | yes | Workflow ID to attach the plan to. |
| workspaceId | string | – | Workspace ID. Defaults to your configured workspace. |
No output schema declared.
No examples provided.
create_resource ~81
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".
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
delete ~73
Delete a resource (moves to trash, restorable). type: file | skill | workflow
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Resource ID |
| type | string | yes | Resource type: file | skill | workflow |
| workspaceId | string | – | Workspace ID (required for workflow). If not provided, uses your default workspace. |
No output schema declared.
No examples provided.
delete_agent ~66
Permanently delete an agent from the workspace. This cannot be undone. System agents (harness agents) cannot be deleted.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | ID of the agent to delete |
| workspaceId | string | – | Workspace ID. If not provided, uses your default workspace. |
No output schema declared.
No examples provided.
delete_done_phases ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| workflowId | string | yes | Workflow ID |
| workspaceId | string | – | Workspace ID. Defaults to your configured workspace. |
No output schema declared.
No examples provided.
delete_identity ~87
Permanently deletes an identity by ID. Use dryRun=true first to preview which workflows will have their identity_id set to null.
| Name | Type | Req | Description |
|---|---|---|---|
| dryRun | boolean | – | If true, returns affected workflows without deleting. Default false. |
| identityId | string | yes | The ID of the identity to delete. |
| workspaceId | string | – | Workspace ID. If not provided, uses your default workspace. |
No output schema declared.
No examples provided.
delete_library ~63
Delete a context library (moves to trash, recoverable within 30 days). Requires owner or admin role.
| Name | Type | Req | Description |
|---|---|---|---|
| libraryId | string | yes | The UUID of the library to delete |
| workspaceId | string | – | Workspace ID (optional — uses default workspace if omitted) |
No output schema declared.
No examples provided.
delete_phase ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| phaseId | string | yes | Phase ID (from list_phases or get_project) |
| workspaceId | string | – | Workspace ID. Defaults to your configured workspace. |
No output schema declared.
No examples provided.
dismiss_broadcast ~52
Dismiss a broadcast notification so it no longer appears in the inbox.
| Name | Type | Req | Description |
|---|---|---|---|
| broadcastId | string | yes | ID of the broadcast to dismiss. |
| workspaceId | string | – | Workspace ID. Defaults to configured workspace. |
No output schema declared.
No examples provided.
dispatch_agent_job ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| intent | string | yes | What you want the agent runner to do. Plain English — e.g. "Summarise the last 5 files in the Research library and write findings to a new file called Summary." |
| workspaceId | string | – | Workspace ID. Defaults to your active workspace. |
No output schema declared.
No examples provided.
edit_phase ~103
Update the title or description of an existing phase without changing its status or position. Use this to reword or clarify a phase.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | New description for the phase (optional, omit to keep current). |
| phaseId | string | yes | Phase ID (from list_phases) |
| title | string | – | New title for the phase (optional, omit to keep current). |
| workspaceId | string | – | Workspace ID. Defaults to your configured workspace. |
No output schema declared.
No examples provided.
figma_sync ~112
Manage Figma connector integrations — list connected files or trigger a sync to pull design tokens, components, and page structure into your Contextium libraries.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | list: show all connected Figma files and their sync status; sync: trigger a full sync for a specific connection |
| integrationId | string | – | Integration ID of the Figma connection to sync (required for action=sync). Get this from action=list. |
| workspaceId | string | – | Workspace ID (uses default if omitted) |
No output schema declared.
No examples provided.
get ~637
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Filter by action — created, updated, deleted, completed, etc. (type=workspace_activity) |
| direction | string | – | Which links to return (type=file_links, default both) |
| entityType | string | – | Filter by entity type — file, workflow, task, agent, member, etc. (type=workspace_activity, entity_activity) |
| id | string | – | Resource ID |
| includeArchived | boolean | – | Include archived items (type=library_structure) |
| includeLinks | boolean | – | Also return the file's outgoing // links resolved to titles (type=file). Set true BY DEFAULT whenever a user asks to open/show/read a file: then add a one-line footer with how many files it links to,… |
| includeMetadata | boolean | – | Include metadata (type=file) |
| limit | number | – | Max results. For workspace_activity: 1–200 (default 50). For file_versions and entity_activity: 1–20 (default 10). |
| month | number | – | Filter to calendar month 1–12 (type=workspace_activity) |
| offset | number | – | Pagination offset (type=file_versions, workspace_activity) |
| page | number | – | Page number for activity_archive (default 1, 100 rows per page) |
| query | string | – | Title or path to search for (type=file_by_path); search term (type=link_suggestions) |
| scope | string | – | Search scope (type=link_suggestions, default workspace) |
| type | string | yes | Resource type. file_links: the files a file links TO (forward) plus files that link to it (backward/backlinks) — id=fileId, optional direction. linked_mentions: backlinks with content excerpts (id=fi… |
| userId | string | – | Filter by user ID (type=workspace_activity) |
| workspaceId | string | – | – |
| year | number | – | Filter to year e.g. 2026 (type=workspace_activity) |
No output schema declared.
No examples provided.
get_agent_job ~62
Get the status and result of a specific agent runner job. Poll this after dispatch_agent_job to check completion.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | Job ID returned by dispatch_agent_job. |
| workspaceId | string | – | Workspace ID. Defaults to your active workspace. |
No output schema declared.
No examples provided.
get_identity ~65
Gets the full profile of a single identity by ID, including voice descriptors, writing samples, and all contextual fields.
| Name | Type | Req | Description |
|---|---|---|---|
| identityId | string | yes | The ID of the identity to retrieve. |
| workspaceId | string | – | Workspace ID. If not provided, uses your default workspace. |
No output schema declared.
No examples provided.
get_notifications ~78
Get the notification inbox for the current user — both activity notifications and broadcasts.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max notifications to return (default 20). |
| offset | number | – | Pagination offset (default 0). |
| unreadOnly | boolean | – | Only return unread notifications. |
| workspaceId | string | – | Workspace ID. Defaults to configured workspace. |
No output schema declared.
No examples provided.
get_project ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| workflowId | string | yes | Workflow ID |
| workspaceId | string | – | Workspace ID. Defaults to your configured workspace. |
No output schema declared.
No examples provided.
get_unread_count ~42
Get the total number of unread notifications (activity + broadcasts) for the current user.
| Name | Type | Req | Description |
|---|---|---|---|
| workspaceId | string | – | Workspace ID. Defaults to configured workspace. |
No output schema declared.
No examples provided.
idea_kickoff ~286
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 analysis autonomously — SWOT, market size (live TAM/SAM/SOM), competitor analysis with funding/revenue/valuation, build plan, RICE scorecard, timeline, roles, two-tier startup financials, and a synthesised go/no-go verdict — written as files into a dedicated project library. Do NOT present a "what do you want to do with this idea" menu and do NOT run the step-by-step new_project wizard: the idea IS the go-ahead, so just do the research. Use new_project instead for a feature inside an EXISTING product; use capture_idea only for a lightweight "remember this" note.
| Name | Type | Req | Description |
|---|---|---|---|
| idea | string | – | The business/product idea, in the user's own words — used to name the project and scope the analysis |
| workspaceId | string | – | Workspace ID (uses default if omitted) |
No output schema declared.
No examples provided.
list ~227
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, tags, file_tags (pass fileId), workspace_status, or members (with roles + activity). Uses your active workspace when workspaceId is omitted.
| Name | Type | Req | Description |
|---|---|---|---|
| fileId | string | – | File ID to list tags for (type=file_tags) |
| folderId | string | – | Filter by folder (type=files) |
| libraryId | string | – | Required when type=files |
| status | string | – | Filter by status (type=files) |
| type | string | yes | Resource type to list. members: list all workspace members with their roles and activity status. |
| workspaceId | string | – | Workspace ID (uses default if omitted) |
No output schema declared.
No examples provided.
list_agent_jobs ~51
List recent agent runner jobs for the workspace — shows status (pending, running, done, failed), intent, and result summary.
| Name | Type | Req | Description |
|---|---|---|---|
| workspaceId | string | – | Workspace ID. Defaults to your active workspace. |
No output schema declared.
No examples provided.
list_agents ~46
Lists all agents (AI assistant configurations) in a workspace. Agents define assistant roles and capabilities.
| Name | Type | Req | Description |
|---|---|---|---|
| workspaceId | string | – | Workspace ID. If not provided, uses your default workspace. |
No output schema declared.
No examples provided.
list_comments ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| fileId | string | yes | UUID of the file |
| includeResolved | boolean | – | Also include resolved threads (default false) |
No output schema declared.
No examples provided.
list_identities ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| scope | string | – | Filter by scope: "user" for personal identities only, "workspace" for shared identities only. Omit to return all visible identities. |
| workspaceId | string | – | Workspace ID. If not provided, uses your default workspace. |
No output schema declared.
No examples provided.
list_lessons ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | – | Only return lessons recorded against this project. Omit to get every lesson in the workspace (the cross-project view). |
| workspaceId | string | – | Workspace ID. Defaults to your active workspace. |
No output schema declared.
No examples provided.
list_phases ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| workflowId | string | yes | Workflow ID |
| workspaceId | string | – | Workspace ID. Defaults to your configured workspace. |
No output schema declared.
No examples provided.
list_tasks ~218
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.
| Name | Type | Req | Description |
|---|---|---|---|
| includeDismissed | boolean | – | Include dismissed tasks. Default: false. |
| mine | boolean | – | Cross-workflow listing only: return just tasks assigned to you plus unassigned ones. Ignored when workflowId is set. Default: false (all tasks across the workspace). |
| priority | string | – | Filter tasks by priority. Omit to return all priorities. |
| status | string | – | Optional comma-separated status filter: not_started,in_progress,done,dismissed |
| workflowId | string | – | Workflow ID. Omit to list all tasks across every workflow in the workspace. |
| workspaceId | string | – | Workspace ID. Defaults to your configured workspace. |
No output schema declared.
No examples provided.
list_trash ~50
List all context libraries currently in the workspace trash (deleted within the last 30 days, not yet permanently removed).
| Name | Type | Req | Description |
|---|---|---|---|
| workspaceId | string | – | Workspace ID (optional — uses default workspace if omitted) |
No output schema declared.
No examples provided.
load_workflow ~66
Load complete workflow context — agents, skills, files, and libraries. Use this to initialise a full workflow session.
| Name | Type | Req | Description |
|---|---|---|---|
| includeFileContent | boolean | – | Include full file content in response (default true) |
| workflowId | string | yes | – |
| workspaceId | string | – | – |
No output schema declared.
No examples provided.
manage_relationship ~423
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-created if new. (Equivalent to updating the file content yourself.) For type=workflow_member, add is an upsert (re-adding an existing member updates their role).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action. apply_bulk/remove_bulk: tag multiple files at once (type=tag, max 100), or add/remove multiple skills on one agent (type=agent_skill, max 100). |
| agentId | string | – | Agent ID (type=agent_skill) |
| fileId | string | – | Single file ID (type=tag, action=add or remove) |
| fileIds | array | – | Multiple file IDs (type=tag, action=apply_bulk or remove_bulk, max 100) |
| role | string | – | Access level for the shared member (type=workflow_member, action=add). Defaults to viewer. |
| skillId | string | – | Single skill ID (type=agent_skill, action=add or remove) |
| skillIds | array | – | Multiple skill IDs to add/remove on one agent (type=agent_skill, action=apply_bulk or remove_bulk, max 100) |
| type | string | yes | Relationship type. |
| userId | string | – | Target workspace member's user ID to share the workflow with (type=workflow_member) |
| value | string | – | Tag value to add/remove (type=tag), e.g. "urgent". Lowercase letters, digits and hyphens; written into the file content as #<value>. |
| workflowId | string | – | Workflow ID (type=workflow_member) |
| workspaceId | string | – | – |
No output schema declared.
No examples provided.
manual_project_setup ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| workspaceId | string | – | Workspace ID (uses default if omitted) |
No output schema declared.
No examples provided.
manual_research_setup ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| workspaceId | string | – | Workspace ID (uses default if omitted) |
No output schema declared.
No examples provided.
mark_notification_read ~63
Mark one notification as read, or mark all notifications as read when no ID is provided.
| Name | Type | Req | Description |
|---|---|---|---|
| notificationId | string | – | Notification ID to mark read. Omit to mark all as read. |
| workspaceId | string | – | Workspace ID. Defaults to configured workspace. |
No output schema declared.
No examples provided.
marketplace ~189
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | search: browse listings; get: full details by slug; install: add to workspace |
| category | string | – | Category filter (action=search) |
| itemType | string | – | Filter by type (action=search) |
| query | string | – | Search query (action=search) |
| slug | string | – | Listing slug (action=get or install) |
| workspaceId | string | – | Target workspace (action=install) |
No output schema declared.
No examples provided.
new_project ~70
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
notify_team_members ~274
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.
| Name | Type | Req | Description |
|---|---|---|---|
| memberEmails | array | – | Optional list of member email addresses to notify. |
| memberIds | array | – | Optional list of member UUIDs to notify. Use memberNames or memberEmails instead when possible. |
| memberNames | array | – | Optional list of member display names to notify (case-insensitive). Prefer this when the user says things like "notify Sarah" or "notify Tom and Alice". |
| message | string | – | Optional additional context to include in the notification |
| notificationType | string | – | Notification preference type. Defaults to "newFileCreated". Use "mention" when notifying a specific person. |
| resourceId | string | yes | The UUID of the resource |
| resourceName | string | yes | Human-readable name of the resource, used in the notification text |
| resourceType | string | yes | The type of resource being shared |
| workspaceId | string | – | Workspace ID (uses default if omitted) |
No output schema declared.
No examples provided.
What is the io.github.contextium-io/mcp-server server?
io.github.contextium-io/mcp-server is listed in the public MCP registry as io.github.contextium-io/mcp-server. Your team's knowledge, always in context. SOPs, coding standards, and workflows for Claude. This page covers its npm package (@contextium/mcp-server).
Is the io.github.contextium-io/mcp-server server safe to use?
io.github.contextium-io/mcp-server scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.contextium-io/mcp-server server expose?
io.github.contextium-io/mcp-server exposes 69 tools: list, get, create, update, delete, and 64 more. Their descriptions and schemas cost roughly 10,643 tokens of context every time the server is loaded.
Is the io.github.contextium-io/mcp-server server still maintained?
io.github.contextium-io/mcp-server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.contextium-io/mcp-server server under?
io.github.contextium-io/mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.